Kembali ke Log Perubahan
Backend Panel
v1.0.598
An upload limit set in a site's own nginx file now survives, Nextcloud can be deployed again, and three app templates stop advertising a port they do not publish.
Peningkatan
2- A regeneration that lowers an upload limit which was raised by hand now records it in the log, naming the old value, the new one and where to set it so it persists. Until now the value simply reverted, and the cause could have been any of a dozen triggers — an SSL operation, a PHP change, an alias edit or an unrelated startup repair.
- When a linked service cannot be given a value it inherits from the main container, the deployment now stops with a message naming the template and the variable, instead of starting a container that cannot work. A value that could not be resolved used to be dropped without a word, which is how a database container could be started with no password at all.
Perbaikan Bug
3- A site's own nginx configuration can now set its upload limit. nginx refuses a second client_max_body_size in the same context, and the generated vhost always wrote one, so the single setting an administrator most often needs to raise was the one the custom-configuration editor could not carry: saving it failed validation and was rolled back. The only place left was the generated file itself, which the next regeneration overwrote. The generated vhost now leaves the directive out when the site's own file provides it, so a limit set in .system/conf/vhost_nginx.conf survives every regeneration. The same rule applies to subdomains.
- Nextcloud could not be deployed from the app templates. The template's linked database container is PostgreSQL, but the template handed it MySQL variables, so the database started without POSTGRES_PASSWORD, refused to initialise and restart-looped for ever while the panel reported the deployment as successful. Typing a password in the form did not help, because the value went to a variable the PostgreSQL image ignores. The PostgreSQL variables are restored. This affected installations created since 15 September 2026; older servers were unaffected.
- WordPress, Matomo and Uptime Kuma showed an address with a port the application does not publish on the screen shown after deployment, so the link answered nothing. The address now follows the port the deployment actually received, including when the port was remapped because the template's default was already in use.