• 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.

Resolved 502 BAD GATEWAY

Henry C. Lavau

New Pleskian
I post this in case it helps.

All the sites of the plesk server suddenly showed a 502 Bad Gateway.
The server VPS000000.ovh.net was hired with Plesk installed.

From time to time, all my sites show the 502 BAD GATEWAY message.

I suspect the automatic updates unable to restart, accordingly to the message I received.
| Unable to generate the web server configuration file on the host <stock.ovh> because of the following errors:
| Template_Exception: Can not restart web server: Apache is down, start it instead of graceful
| Apache is down, start it instead of graceful

A manual repair / restart did not solve the problem either

What solved it? Setting the Full Server Name from stock.ovh, which is the default name of the server to its name VPS000000.ovh.net (replace VPS000000 by the actual name)
The sites reborned instantly.

HTH
 
Back
Top