• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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