• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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