We’ve repeatedly encountered an issue where Panelica updates or configuration regeneration appear to reset a domain’s custom Nginx upload limit.
Our configured limits were:
Nginx client_max_body_size: 1100M<br>PHP upload_max_filesize: 1024M<br>PHP post_max_size: 1100M<br>ModSecurity SecRequestBodyLimit: 1153433600
Uploads worked with those settings. However, the generated Nginx configuration later reverted to:
client_max_body_size 64M;
The reset affected both HTTP and HTTPS server blocks. PHP and ModSecurity retained their configured limits, but Nginx’s lower limit prevented a 75 MB file from uploading.
Restoring client_max_body_size to 1100M, validating the configuration, and reloading the customer Nginx service resolved the issue. An 80 MB multipart HTTPS request then passed successfully.
This regression has happened repeatedly. We suspect an update or configuration rebuild, but have not confirmed the exact trigger.
Could the Panelica team investigate and clarify:
To clarify, this concerns server configuration settings being overwritten, not uploaded user files being changed or deleted.
Thank you.
Our configured limits were:
Nginx client_max_body_size: 1100M<br>PHP upload_max_filesize: 1024M<br>PHP post_max_size: 1100M<br>ModSecurity SecRequestBodyLimit: 1153433600
Uploads worked with those settings. However, the generated Nginx configuration later reverted to:
client_max_body_size 64M;
The reset affected both HTTP and HTTPS server blocks. PHP and ModSecurity retained their configured limits, but Nginx’s lower limit prevented a 75 MB file from uploading.
Restoring client_max_body_size to 1100M, validating the configuration, and reloading the customer Nginx service resolved the issue. An 80 MB multipart HTTPS request then passed successfully.
This regression has happened repeatedly. We suspect an update or configuration rebuild, but have not confirmed the exact trigger.
Could the Panelica team investigate and clarify:
- What process could reset a custom upload limit to 64M?
- Where should administrators configure domain limits so they survive updates, PHP version changes, and configuration rebuilds?
- Can the update process preserve existing administrator-defined settings and back up configurations before replacing them?
- Can this behavior be covered by a regression test?
To clarify, this concerns server configuration settings being overwritten, not uploaded user files being changed or deleted.
Thank you.