• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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
3
Views
4K
Conny Dittmann
Conny Dittmann
J
Issue sw-engine won't start
Replies
15
Views
3K
alvarezcruz
alvarezcruz
P
Question Plesk login 8443 cannot be called up
Replies
8
Views
3K
Kaspar@Plesk
Kaspar@Plesk
C
Issue 502 Bad Gateway - after applying updates
Replies
2
Views
3K
CChris
C
Y
Issue I can't access the plesk panel and all sites returning Nginx 502 Bad Gateaway error after updated some components
Replies
1
Views
1K
IgorG
IgorG
Back
Top