• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Error 502 after manual update

S

Steve1980

New Pleskian
Hi all,

After a failed automatic upgrade I manually updated plesk via the upgrades and components page.

I am now unable to log into the Plesk control panel however all the websites are still working (thank God).

Does anyone know what the issue can be? I am running Centos 6 and Plesk 12.

I've really don't want to reinstall Plesk as I will lose everything.
 
You must log in or register to reply here.

Similar threads

AlbertoPizzarelli
Resolved Plesk update fails on CentOS 7 + TuxCare ELS: missing trousers dependency (gnutls requires trousers >= 0.3.11.2)
Replies
4
Views
3K
D4NY
D4NY
weareimpulse
Question Plesk pre-upgrade check - Checking Components Before Updating
Replies
4
Views
1K
weareimpulse
weareimpulse
T
Question Plesk Update Notification Without Local Email Service
Replies
4
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
H.W.B
Issue Watchdog down after Plesk update
Replies
7
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
C
Issue Plesk-mail-pc-driver update 18.0.76.5 causes Dovecot authentication database desync on every automatic update
Replies
6
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top