• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue 502 Gateway to Plesk Login after update

Joe90k

New Pleskian
Ran an update to plesk this afternoon on a cloud server I have, it seemed to complete successfully however it gave and error that another instance of the installer was running and said the server may be non-responsive.

All sites are fine, however the Plesk panel is inaccessible now. 502 Bad Gateway when accessing xxx.xxx.xxx.xxx:8443

Running /etc/init.d/sw-engine restart is OK - starting and stopping sw-engine is fine but has no effect on the login screen still 502, the last line of /var/log/sw-cp-server/error_log shows:-
Code:
2018/08/20 16:28:55 [error] 33289#0: *9001 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "xxx.xxx.xxx.xxx:8443", referrer: "https://panel-url.xxx"

I think possibly the update failed, my Linux and Plesk Knowledge is limited so any help is appreciated! I also notice that /run is 100% used. I'm not sure if this is an issue or not!

Code:
ps aux | grep sw-
psaadm    7031  0.0  0.0 325716   540 ?        S    Jan04   0:08 sw-engine-kv
root     22906  0.0  3.3 511496 33400 ?        Ss   16:18   0:00 sw-engine-fpm: master process (/etc/sw-engine/sw-engine-fpm.conf)
root     23891  0.0  0.0 112704   972 pts/0    R+   16:33   0:00 grep --color=auto sw-
root     33287  0.0  0.0  52432     4 ?        Ss   Jul24   0:00 sw-cp-server: master process /usr/sbin/sw-cp-serverd -c /etc/sw-cp-server/config
sw-cp-s+ 33289  0.0  0.3  54484  3456 ?        S    Jul24   0:11 sw-cp-server: worker process
 
which OS do you have ?

did you try the usual comands? Try to run:
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation

Another way would be -> contact Plesk Support Team if it not help, they will fix your Plesk directly on your server.
 
which OS do you have ?

did you try the usual comands? Try to run:
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation

Another way would be -> contact Plesk Support Team if it not help, they will fix your Plesk directly on your server.

The first command looked hopeful the second returned signal: bus error - I will contact Plesk! Thanks :)
 
I tried to work out how to contact Plesk directly without too much luck! What's the best method please?
 
Back
Top