• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Prevent 502's for all sites when changing configs

KarelB

New Pleskian
I have a Plesk 12 server running that works great. But the problem is that whenever one of my shared hosting customers changes something out a domain or subdomain, all the other sites on the server give a 502 error.
The reason why is clear to me: apache is reloading its config while nginx is still active, but sees apache as being down and therefor throws a 502 error.

Is there any way to prevent this from happening? Because it's happening a lot and people are sending in 'site down' reports while there's actually nothign wrong with the server or their site.

I tried searching for "502" on the forum, but it seems that keywords is too short to be used for a search...
 
Back
Top