Applicable to:
- Plesk for Linux
Symptoms
- In Tools & Settings > Apache Web Server, Apache restart interval value is set to 0.
- After settings update via Plesk sites show periodically show
502 Bad Gatewayerror.
-
The records below can be found in
/var/www/vhosts/system/example.com/logs/proxy_error_log:2020-04-29 13:35:29 Error 203.0.113.2 28571#0: *6219628 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-04-29 13:38:24 Error 203.0.113.2 31784#0: *6220942 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream nginx error -
Also the following notification can be received by Watchdog:
The Web Server (Apache) service on host example.com is down. The problem was discovered on Jan 14, 2021 08:57 AM.
Cause
When the interval is set to 0, Apache web server restarts immediately to apply new domain settings. Apache restart causes websites unavailability.
Resolution
-
Open Tools & Settings > Apache Web Server.
-
Set up a non-zero Apache restart interval, for example 600 (interval is set in seconds).
Comments
4 comments
Does this mean that changes for Apache will be applied only every 600 seconds?
Hello @tomaz,
Yes, changes take effect only after the restart of Apache.
Please, note that 600 seconds is an example value.
After your recent maintenance my website has stopped working, how do I proceed?
Hello Paul Hume
Please, could you clarify, what do you mean by maintenance? Was it Plesk update?
What error is displayed?
The quickest way to have the issue resolved is to submit a support request to Plesk Technical Support or to our partner depending on where Plesk license was purchased.
Please sign in to leave a comment.