February 23, 20251 yr Dear Glorious Authists, I seek your infinite wisdom! I have installed and configured the @SpaceInvaderOne Nextcloud AIO, which has worked flawlessly for two weeks! However, I created a shared folder and whenever someone tries to upload bigger they get Server replied "413 Request Entity Too Large" regardless of whether it is uploaded from the Windows app or Browser. I am trying to solve it with this config: upload_max_filesize = 16G post_max_size = 16G max_execution_time = 3600 memory_limit = 1024M I am running in circles trying to figure out where the bloody config is, as it seems that SpaceInvaderOne setup is somewhat custom and whatever I try I don't find the necessary configs... I am dying...I`ve been fighting with this for a week now...🫠 I attached the running dockers. The PHP config is the default one: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 4bc8d47705d1 nextcloud/aio-apache:latest "/start.sh /usr/bin/…" 5 hours ago Up 38 minutes (healthy) 80/tcp, 0.0.0.0:11000->11000/tcp, :::11000->11000/tcp nextcloud-aio-apache 647011b077e0 nextcloud/aio-notify-push:latest "/start.sh" 5 hours ago Up 38 minutes (healthy) nextcloud-aio-notify-push 49f60372c3f8 nextcloud/aio-nextcloud:latest "/start.sh /usr/bin/…" 5 hours ago Up 38 minutes (healthy) 9000/tcp nextcloud-aio-nextcloud e35988d29790 nextcloud/aio-redis:latest "/start.sh" 5 hours ago Up 38 minutes (healthy) 6379/tcp nextcloud-aio-redis 58b6e89f6516 nextcloud/aio-postgresql:latest "/start.sh" 5 hours ago Up 38 minutes (healthy) 5432/tcp nextcloud-aio-database 928760df2821 nextcloud/aio-collabora:latest "/start-collabora-on…" 5 hours ago Up 38 minutes (healthy) 9980/tcp nextcloud-aio-collabora 025a673766e2 nextcloud/all-in-one:latest "/start.sh" 2 weeks ago Up 37 minutes (healthy) 80/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:7282->8080/tcp, :::7282->8080/tcp Version: 8.3.16 Memory limit: 512 MB Max execution time: 3600 Upload max size: 16 GB OPcache Revalidate Frequency: 60 Extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, hash, iconv, json, mbstring, SPL, session, PDO, pdo_sqlite, bz2, posix, random, readline, Reflection, standard, SimpleXML, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, cgi-fcgi, apcu, bcmath, Phar, exif, ftp, gd, gmp, igbinary, imagick, imap, intl, ldap, memcached, pcntl, pdo_pgsql, pgsql, redis, smbclient, sodium, sys Please someone have mercy and guide the cursed noob of me on how to fix this! Edited February 23, 20251 yr by Hordemar
February 23, 20251 yr Author Solution JEEEEEEEUS! What a find! Check This Reddit Post So here is what I did to "fix" it via the desktop client: Quote Cloudflare only supports uploading files up to 100 MB in the free plan, if you try to upload bigger files you will get an error (413 - Payload Too Large) if no chunking is used (e.g. for public uploads in the web, or if chunks are configured to be bigger than 100 MB in the clients or the web). Based on https://github.com/nextcloud/desktop/issues/4271#issuecomment-1159578065 Quote Windows Fix Press Win+R on your keyboard to open the Run application. Past the following in the dialog box: %APPDATA%\Nextcloud\nextcloud.cfg This will either ask you to pick an application to open nextcloud.cfg or will open in your default text editor (unless you have something else set to open .cfg files). If it asks you to pick an application, feel free to use Notepad or any other editor. Add the following line under the [General] section: maxChunkSize=50000000 Save the file, quit Nextcloud desktop, and start it again. I tested it and it works! This way the app is forcing 50MB chunks so it will pass the 100MB Cloudflare limit...!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.