• 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.

Resolved Control Panel unreachable on port 8443

aless

New Pleskian
Hi,

all of a sudden I am not able to reach the cp both on https://serverurl:8443 and http://serverurl:8880. Website and other services seem to work as usual though. Now, since I know that this can be related to a variety of issues, I would appreciate very much if someone could help me in creating a comprehensive list of possible related issues, in order for me to debug, and maybe for other people in the community dealing with the same problem to find them all in one place.

So far here is what I have investigated:

1. Firewall

Check if port 8443 is open. The actual iptables rule for ports 8443 and 8880 is
# iptables -I INPUT 1 -p tcp -m multiport --dports 8880,8443 -j ACCEPT

2. Fail2Ban
either start and stop doesn't solve the issue

3. Restart cp
# /etc/init.d/sw-cp-server restart
correctly restarts the cp, but with no effects

The error:log file in my /var/log/sw-cp-server folder says
# 25774#0: *1 connect() to unix:/var/run/sw-engine.sock failed (11: Resource temporarily unavailable)

What else should be checked in order to investigate further this issue?
 
Hi aless,

pls. consider to use as well:
Code:
/etc/init.d/sw-engine restart
or/and
Code:
service psa restart
... and report back, if this already solved your issue.

If the issue is still existent, pls. consider to have a new look at your error.log and pls. post as well the output of the example commands ( logged in as user "root" over SSH ):
Code:
ps aux | grep sw-
and
Code:
lsof -i | grep 8443
netstat -ltnp | grep 8443
Code:
lsof -i | grep 8880
netstat -ltnp | grep 8880
 
Hi aless,

pls. consider to use as well:
Code:
/etc/init.d/sw-engine restart

Absolutely great. Many thanks! That solved the issue.

If I may ask, just for the record, what is the difference between the two services sw-cp-server and sw-engine?

Thanks again.
 
Back
Top