Back to Changelog
v1.0.310
WordPress installs and security-reconfig now use the canonical mode-aware config generator, fixing self-signed certificate stuck state after WordPress installation
Improvements
2- nginx vhost regeneration now validates with nginx -t and rolls back safely on any error before applying changes
- nginx stays a pure reverse proxy in all code paths; ModSecurity processing remains exclusively in Apache, consistent with the panel architecture
Bug Fixes
2- WordPress install and domain security-reconfig now regenerate nginx and Apache configs through the same canonical, mode-aware generator used by domain create and the SSL editor
- Fixed a case where WordPress installation left the domain stuck on a self-signed certificate: config regeneration was rolling back silently due to an incorrect vhost template (nginx was receiving ModSecurity directives that belong only to Apache), so HTTPS and auto-SSL were never applied