• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Unable to access to my Plesk interface (502 Bad Gateway)

T

Tomulus06

New Pleskian
Server operating system version
CentOS 7.9
Plesk version and microupdate number
Plesk Obsidian 18.0.60.0
Hi,

I can no longer access my Plesk interface since I restarted my server. I have the following error: 502 Bad Gateway.

The repair kit tells me that the sw-engine.service is stopped. I tried to restart my server but the error persists. When I restart sw-engine.service, the process stops immediately.

I couldn't find a solution that works in my case on the forum. Here are my different logs:

- systemctl status sw-engine.service :
sw-engine.service - Startup script for Panel sw-engine
Loaded: loaded (/usr/lib/systemd/system/sw-engine.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/sw-engine.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Fri 2024-04-26 14:02:14 UTC; 4s ago
Process: 5814 ExecStopPost=/usr/bin/find /run/lock/lmlib/ -mindepth 1 -delete (code=exited, status=0/SUCCESS)
Process: 5813 ExecStart=/usr/sbin/sw-engine-fpm --fpm-config /etc/sw-engine/sw-engine-fpm.conf -c /usr/local/psa/admin/conf/php.ini --nodaemonize --pid /run/sw-engine.pid (code=exited, status=1/FAILURE)
Main PID: 5813 (code=exited, status=1/FAILURE)
CGroup: /system.slice/sw-engine.service

Failed to start Startup script for Panel sw-engine.
Unit sw-engine.service entered failed state.
sw-engine.service failed.
Click to expand...

- journalctl -xe :
-- Subject: Unit plesk-web-socket.service has finished shutting down
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit plesk-web-socket.service has finished shutting down.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Started Plesk Web Socket Service.
-- Subject: Unit plesk-web-socket.service has finished start-up
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit plesk-web-socket.service has finished starting up.
--
-- The start-up result is done.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/libaps.so.1)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_filesystem-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_regex-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_thread-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_serialization-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/sw/librdbmspp.so.2)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: sw-engine.service: main process exited, code=exited, status=1/FAILURE
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/libaps.so.1)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_filesystem-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_regex-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_thread-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_serialization-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/sw/librdbmspp.so.2)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Failed to start Startup script for Panel sw-engine.
-- Subject: Unit sw-engine.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit sw-engine.service has failed.
--
-- The result is failed.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Unit sw-engine.service entered failed state.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: sw-engine.service failed.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: plesk-web-socket.service: main process exited, code=exited, status=1/FAILURE
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Unit plesk-web-socket.service entered failed state.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: plesk-web-socket.service failed.
Click to expand...

thanks ! :)
 
You must log in or register to reply here.

Similar threads

M
Issue After update to 18.0.60 sw-engine no start
Replies
6
Views
2K
User 343735
U
A
Issue Server Error 502 Bad Gateway /
Replies
11
Views
4K
dlabsnl
D
Jan Bludau
Resolved Debian 11 to Debian 12
Replies
2
Views
5K
Jan Bludau
Jan Bludau
Q
Resolved problem with ram server
Replies
8
Views
2K
Qusay
Q
R
Issue Update to plesk 18.0.40 failed
Replies
2
Views
2K
IgorG
IgorG
Back
Top