चेंजलॉग पर वापस जाएँ
पैनल बैकएंड
v1.0.599
Apache's status page works again, the panel stops overwriting a vhost file you have edited, and the upload-limit and app-template fixes from the previous beta.
सुधार
3- The panel no longer overwrites the Apache default vhost file once you have edited it. It is replaced only while it is still exactly what the panel wrote - today's shape, or one an earlier version produced, which is how a server affected by the problem above repairs itself. Any other content is yours: the panel leaves the file alone and records why in the log.
- A regeneration that lowers an upload limit raised by hand now says so in the log and names where to set the value so it persists.
- A linked service that cannot be given a value it inherits from the main container now stops the deployment with a message naming the template and the variable, instead of starting a container that cannot work.
बग फ़िक्स
4- Apache's server status page is reachable again. The default vhost added in 1.0.591 answered 404 for every path on 127.0.0.1:7080, /server-status included, so no monitoring agent on the machine could read Apache any more - mod_status stayed loaded and configured, but nothing could reach it. The page is excluded from the catch-all and stays restricted to localhost; an unmatched Host still gets 404 instead of another customer's site.
- A site's own nginx configuration can now set client_max_body_size. nginx refuses a second copy of that directive in one context and the generated vhost always wrote one, so the setting administrators most often need to raise was the one the custom-configuration editor could not carry. A limit set in .system/conf/vhost_nginx.conf now survives every regeneration, and the same applies to subdomains.
- Nextcloud could not be deployed from the app templates. The linked database container is PostgreSQL but the template handed it MySQL variables, so it started with no POSTGRES_PASSWORD and restart-looped while the panel reported success. The PostgreSQL variables are restored.
- WordPress, Matomo and Uptime Kuma showed an address with a port the application does not publish on the screen shown after deployment. The address now follows the port the deployment actually received, including when it was remapped because of a conflict.