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

Issue 502 Bad Gateway on all domains

M

MarkgWatson

New Pleskian
I rebooted Plesk and now all my hosted domains are resolving with 502 Bad Gateway. I am able to access to Plesk admin panel but all my domains are resolving with the 502 problem.

Can anyone suggest what I can do to rectify the problem.
 
You must log in or register to reply here.

Similar threads

Daveo
Issue Debian 13: Apache Issues
Replies
13
Views
6K
mow
M
X
Issue Cloudflare DNS Extension Fails with JsonException when Cloudflare returns non-JSON errors (502/524)
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
D
Issue Plesk stops responding
Replies
1
Views
1K
scsa20
scsa20
E
Resolved Made a mistake, changed server hostname, please advise
Replies
2
Views
2K
elliotpa04
E
Z
Resolved Plesk updates failing: 502 Bad Gateway after installer update + “Unable to receive update information” error
Replies
1
Views
2K
zihniates
Z
Back
Top