Roundcube is using PHP, right? The default php.ini on my box is set for a upload_max_filesize of 2M, so since Roundcube is reading that it’s max file size for upload is 16MB, I’m guessing somewhere there’s an .htaccess file that’s overriding it.
Edit, phpinfo in the roundcube directory shows the same:
The only other thing I’d consider is if you have too big an attachment, many mail services will reject the delivery. Most have a limit of sending attachments of 25MB - They’re unlikely to accept a 650MB file.
Alright, looks like you can upload pas 128MB if compressed into a zip, I guess, however much your cpu can crunch numbers, and depending on the acceptable formatting of the compressed archive.
Do you mean you can compress a file larger than 128MB such that the compressed file is under 128MB, so it can be uploaded? Because the limit in nginx should not allow any request body over 128MB, no matter the filetype.
I don’t see any errors in access.log or error.log of nginx
The POST command seems to be running for ever on client side without no way to follow if failed or still running.
On server side I can the POST in acces.log and no errors about it in error.log
No imapsync is not option since this shall be able to be done by any non-technical user without installing or using any third-party software.
I am gonna look about this keepalive timeout param…
What is the expected time for the upload to complete?
The client_max_body_size directive is available to be configured under every domain and subdomain in /etc/nginx/conf.d/local.conf. Did you check to make sure you configured in the correct server block?
I have no clue on the expected time for the upload to complete.
How would I know/calculate that ?
I guess it is highly depending on the user bandwidth capacity right.
yep I got the right domain because if don’t modify those parameters I get the error like in the screenshot of the very message of this conversation…