On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Plesk never loads or fails with 502 Bad Gateway/504 Gateway errors

Follow

Comments

3 comments

  • Avatar
    bruno vianna

    I am having this trouble regularly. Every day at around 6.30 the network and cpu usage spike and the domains stop being served with 504 errors. I restarted both nginx and apache and it didn't work. The only solution I found was to reboot the server, but the next morning it stops again. Tomorrow I'l ll try the solution above.

    It seems to have started after the upgrade to 18.0.27. I'm running plesk obsydian on linux.

    I began to suspected ddos attacks, but I checked the main ips and there was nothing suspicious. Could it be some maintainence script causing that?

    This is the error I got (8:13 was the time I checked the domains=.

    2020/06/08 08:13:15 [crit] 599#0: *1 connect() to unix:/run/plesk-web-socket/ws.sock failed (2: No such file or directory) while connecting to upstream, client:x.x.x.x, server: , request: "GET /ws HTTP/1.1", upstream: "http://unix:/run/plesk-web-socket/ws.sock:/", host: "canpujades.com:8443"
    2020/06/08 08:13:18 [crit] 599#0: *3 connect() to unix:/run/plesk-web-socket/ws.sock failed (2: No such file or directory) while connecting to upstream, client: x.x.x.x, server: , request: "GET /ws HTTP/1.1", upstream: "http://unix:/run/plesk-web-socket/ws.sock:/", host: "canpujades.com:8443"
    2020/06/08 08:13:25 [crit] 599#0: *6 connect() to unix:/run/plesk-web-socket/ws.sock failed (2: No such file or directory) while connecting to upstream, client: x.x.x.x, server: , request: "GET /ws HTTP/1.1", upstream: "http://unix:/run/plesk-web-socket/ws.sock:/", host: "canpujades.com:8443"

    2
    Comment actions Permalink
  • Avatar
    bruno vianna

    I tried the solution above and it didn't work. The only solution was to reboot the machine.

    0
    Comment actions Permalink
  • Avatar
    Anzhelika Khapaknysh

    @bruno vianna,

    The issue may be caused by various of reasons.

    I'd recommend contacting our Support Team for a thorough investigation.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request