Files not getting synced (413 Request Entity Too Large)

[kinghat]

@BlackJub

Replace “client_max_body_size 512M;” with “client_max_body_size 0;” in the following file: “[…]/nextcloud/nginx/site-confs/default.conf” in Nextcloud.
(Related parameters in php.ini didn’t affect WebDAV connections)

i had to set this as well in the nginx conf inside the linuxserver nextcloud image. my swag nginx and nextcloud proxy confs were both set to 0 already.

@Michael_Moreno

I know this is old but I found my solution.
I noticed in the Nextcloud GUI > Administation Settings > Settings
At the bottom in the PHP section it still said “Upload max size: 512 MB”

I found “/etc/php83/conf.d/nextcloud.ini” where it still said 512M. I changed it to 200G

i dug in and looked at this file as well, its the same as yours but i didnt need to change this in the linuxserver image. just the nginx config.

[Yorgos_Andreadakis]

@Michael_Moreno

Additionally I was using a cloudflare tunnel. As it turns out the free plan limits “Maximum Upload Size” to 100 MB. In photosync, I enabled “upload in chunks”, and I no longer get this error when transferring large files.

Well I am using Cloudflare’s Tunnel too and that " As it turns out the free plan limits “Maximum Upload Size” to 100 MB " gave me an idea:

I went to windows’ Nextcloud Desktop client configuration file
(found

• On Linux distributions:
  $HOME/.config/Nextcloud/nextcloud.cfg
• On Microsoft Windows systems:
  %APPDATA%\Nextcloud\nextcloud.cfg
• On macOS systems:
  $HOME/Library/Preferences/Nextcloud/nextcloud.cfg
  )

and added under [General] the following 2 lines:
timeout=1200
maxChunkSize=100000000

I limit the maximum chunk size to under 100MB that Cloudflare’s free plan imposes and that solved for me that terrible “413 Request Entity Too Large” error