• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Plesk 11.5 MU#11 - Bad Gateway 502 - PleskFatalException

N

netsetter

Basic Pleskian
It happens with every update since 11.5.x:

Internal error.
ERROR: PleskFatalException: Unable to connect to database: mysql_connect(): No such file or directory (auth.php:139)

So far I always could ignore this error, but this time, after installing MU#11, I am unable to login to plesk panel, it now says:

502 Bad Gateway
nginx

Any ideas?


Update: I'm able to login again, seems that I had to wait a few minutes, now the Bad Gateway error isn't showing up anymore.
 
Last edited:
You must log in or register to reply here.

Similar threads

Mlieder
Question Problems with Joomla and my domains on Plesk Obsidian on Ubuntu 22.04
Replies
2
Views
755
Conny Dittmann
Conny Dittmann
J
Issue sw-engine won't start
Replies
15
Views
2K
artalva
artalva
C
Issue 502 Bad Gateway - after applying updates
Replies
2
Views
2K
CChris
C
P
Question Plesk login 8443 cannot be called up
Replies
8
Views
245
Kaspar@Plesk
Kaspar@Plesk
finbarr69
Resolved nginx random bad gateway 502 errors segfault
Replies
1
Views
2K
finbarr69
finbarr69
Back
Top