- Plesk for Linux
When changes are applied in a website configuration (i.e. hosting settings) Apache immediately restarts and all websites show the error:
CONFIG_TEXT: 502 Bad Gateway
How to prevent Apache to restart every time when any changes are applied in Plesk?
When users perform operations with domains and subdomains (such as creating, removing, or changing their configurations), the changes take effect only after the restart of Apache.
To avoid too many Apache restarts, it's possible to set a fixed interval of time in which Plesk should restart Apache. Note that if the interval is 0 seconds, Apache restarts immediately after each change. It is recommended to always set this interval to more than 0 seconds, especially if users perform a lot of operations with domains and subdomains through Plesk.
If during the specified interval of time no changes were made with domains, Apache will not restart.
To prevent Apache restart immediately log in to Plesk web interface and specify Apache restart interval under Tools & Settings > Apache Web Server.
Once in a specified interval, Plesk checks for changes made to domains and subdomains. In case there are changes that require web server restarting, Plesk restarts Apache.
Note: Restart interval should be specified in seconds.