Wont sync files after 413 request entity too large error

[GekoCH]

Expected behaviour

I have a large folder with a lot of pictures that should be synced to the cloud

Actual behaviour

I synced a folder with 1200 images (one image around 20mb)
I got a some errors: 413 request entity too large error

So after rebooting the system it synced again and told me that all files were synced but after investigation those files that were marked by the 413 request entity too large errors won't get synced anymore. I can't force them to synchronize again

Client configuration

Client version: 2.5

Operating system: Win 10

[instantlinux]

Ditto. I was moving nextcloud to a new host, forgot to update the buffer-size params, and now have about 100 photos in limbo. This bug should be easy to reproduce: install nextcloud behind a nginx reverse-proxy, set its proxy-body-size / client-body-buffer-size values below the size of typical photos, try to do an upload, then readjust the proxy to allow large-file uploads. The iOS app won't give you any option to retry the failed Error code 413 uploads.

Nextcloud for iOS 2.22.7.4
Nextcloud server 15.0.0

[gacpac]

In my case, I updated from the 2.3.3 client and it started giving me that error. I also have a setup behind a reverse proxy with Unraid.

It doesn't happen in my android app, iPhone app or the web. Only happens at the Client using the latest 2.5.1

To be more specific. I cannot upload files bigger than 95Mb because of that error.

[gacpac]

log nextcloud.txt

This is my log

[ChadBailey]

Can confirm also experiencing this behavior.... activity log reports "(skipped due to earlier error, trying again 22 hour(s))". Would be nice to be able to force a retry once server config issue is resolved.

Edit: I attempted to workaround via reinstalling the client, but it did not delete the local config files (nor did it prompt to, probably should but staying focused on this bug).

Workaround: Open config file with Nextcloud client closed and delete all contents then save to reset config upon next launch (not clean, you can go manually hunting for the other files if you so desire). i.e. Win+R then enter notepad.exe "%APPDATA%\Nextcloud\nextcloud.cfg" when notepad opens, ctrl+a then delete and save.

[kylepaulsen]

I'm no expert, but this is what I figured out:

Look for a hidden .db file in the root nextcloud folder you chose to sync from. It might be named something like: ._sync_4c7450a8f62e.db

If you quit nextcloud and either move this file out (or delete it) and then restart nextcloud, it should resync all failed files. Keep in mind this .db file has some settings data you might have set up.

Alternatively you can use a sqlite database viewer/editor like https://sqliteonline.com/ and load up that database file. You can run DELETE FROM 'blacklist'; as a command to remove all error logs from that DB file (these are the records that prevent the client from trying to resync right away). Place the edited db file back and run nextcloud and it should try syncing the failed files again.

[tuomassalo]

I can confirm that @kylepaulsen's workaround also works on macos Catalina, which conveniently ships a sqlite client. Here's what I did:

1. quit the Nextcloud client
2. open a terminal window
3. run sqlite3 my-nextcloud-folder/._sync_123567890ab.db
4. type delete from blacklist;
5. type ctrl-d to exit the client
6. reopen Nextcloud client

[raleonardo]

Hi
Having the same issue with NC desktop for mac 3.1.3 with, docker nextcloud:21 behind nginx proxy.
trying again in 19 hours..

I already set this in nginx:

client_max_body_size        10G; 
client_body_buffer_size     400M;

Any idea how to force sync these files on the client side?

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[gacpac]

my problem was also regarding the reverse proxy from swag that had some old config, causing this to happen.

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!