Hello, we have a problem with ISPConfig and the configuration of our nginx web server. Last week, a customer entered a nginx config with incorrect syntax in the web interface. ISPConfig attempted to deploy this config on the web server, causing it to crash. ISPConfig then reverted the config and restarted the web server. However, ISPConfig keeps trying to deploy the faulty nginx config every minute, resulting in a downtime of 5-10 seconds each minute. Is there a way to adjust ISPConfig to, for example, run "nginx -t" to check if the config is valid before deploying it, or to ban a invalid config from deploying until it has been fixed? Thank you
That's what ISPConfig is doing already, but not every potential config issue can be found like this. If the config test is successful, then ISPConfig applies the config nd restarts the server, if this fails, the config gets reverted and the last working config is being used. So in your case, somehow the last working config is broken as well, which can normally not happen, unless someone manually altered config files on the system outside of ISPConfig. So you should check what got altered manually in the config and fix that to stop this loop. Also take care that you did not disable the config test under System > server config > web, as this would allow clients to pass an invalid config to the system.
