-
Is your feature request related to a problem? Please describe.Users with high upload speed and cloudflare tunnel/proxy users can benefit of this env variables. For example, if a user wants to upload a folder with +20 files and the whole folder size is +40GB, the default chunk size is 10MiB, so this can be an issue because it exceeds the value of Cloudflare Tunnel/proxy users on tier free can upload up 100MB per request, this can be solved by limiting chunk size to 95MiB in case of a large file upload, and combining with max_file_uploads, say 60. Describe the solution you'd likeAdd the folowing env variables to docker-compose.yml Describe alternatives you've consideredSet 95MiB as the default for Additional context |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
Hi, based on https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#adjust-chunk-size-on-nextcloud-side and https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-run-occ-commands, you can already set the max_chunk_size via
Edit: I think you are misunderstanding this setting. |
Beta Was this translation helpful? Give feedback.
-
No. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification.
PHP default value is 20 files per request. I will try to upload the same folder outside the cloudflare tunnel to see if this issue is about the 100MB limitation or |
Beta Was this translation helpful? Give feedback.
-
|
What did you find out? :) |
Beta Was this translation helpful? Give feedback.
-
|
I tested it again without CF proxy on a domain and a fresh install of the AIO. The fist attempt uploading these folder it throw me some 403 and 408 errors, I don't know if this was caused by a server overload or proxy issue, my reverse proxy is configured on an old 775 machine with 4GB of ram and a dual core Celeron E3300 running OpenMediaVault and Nginx Proxy Manager. The machine where I tested has a 5700x and 32gb of ram, I virtualized a Debian OS with 4GB of ram and 4 cores.... On the first test ran with default AIO php parameters, the default
The upload was completed but with some files missing. In the second test I tried to upload it again with a value of 1000 on
On the third test I tried it again but with the default value and restarted the nextcloud container and deleted all the cache on the web browsers. And the upload finished successfuly again using Chrome and Brave... However I tested this using Firefox. This time I noticed something was slowing down my entire PC and crashed the system, lol. Looking on the Task manager: Oh my gosh, 98% of ram usage... So at this point I think the default values are working well no need to increase the |
Beta Was this translation helpful? Give feedback.
-
|
This is my NPM config:
|
Beta Was this translation helpful? Give feedback.
-
|
This is the complete folder tree: |
Beta Was this translation helpful? Give feedback.
I tested it again without CF proxy on a domain and a fresh install of the AIO.
The fist attempt uploading these folder it throw me some 403 and 408 errors, I don't know if this was caused by a server overload or proxy issue, my reverse proxy is configured on an old 775 machine with 4GB of ram and a dual core Celeron E3300 running OpenMediaVault and Nginx Proxy Manager.
The machine where I tested has a 5700x and 32gb of ram, I virtualized a Debian OS with 4GB of ram and 4 cores....
On the first test ran with default AIO php parameters, the default
max_file_uploadsvalue in this case is 20.(To get this value execute
sudo docker exec -it nextcloud-aio-nextcloud php -r "phpinfo();" | grep ma…