Turkey (Turkish)
Germany (German)
Worldwide (English)
Panel servislerisw-cp-server and sw-engine
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
The Plesk control panel runs by default from HTTPS 8443 port. Failure to open the panel; failure to listen on the port, sw-cp-server or sw-engine failure, firewall/Fail2Ban block, hostname DNS or panel SSL certificate issue can occur.
This site can’t be reached
ERR_CONNECTION_TIMED_OUT
ERR_CONNECTION_REFUSED
curl: (7) Failed to connect to 127.0.0.1 port 8443
sw-cp-server.service: FailedTimeout, indicates that the connection packets could not be responded to; connection refused shows that the target server is not actively serving on the port or has refused the connection. The issue should be separated from the external network problem by testing with localhost first and the panel service.
If the local test on 127.0.0.1:8443 is successful but the external connection fails, the problem is likely due to the operating system firewall, data center security group, NAT, or IP block.
If local test fails, check sw-cp-server, sw-engine, panel configuration, and /var/log/plesk/panel.log.
If access is only possible to a single IP, Fail2Ban, Plesk Firewall or ISP block is investigated. If no one has access, the service and port listening status is the priority.
If the hostname is resolved to the wrong IP or the panel certificate is incompatible, the browser SSL warning will be triggered; this situation should not be confused with safe timeout.
It is more secure to only allow admin IPs and use VPN/zero-trust access if possible, instead of temporarily opening 8443 port to the entire internet without restrictions.
Search for the phrase you see in the email, browser, or SSH log. Each card includes meaning, probable cause, and safe initial action.
Meaning: Client did not receive connection response within the specified time.
Possible cause: Firewall drop, security group, incorrect IP, network route, or overload.
Meaning: Target reached but connection to port 8443 has been refused.
Possible cause: sw-cp-server is closed or service is listening on a different interface.
Meaning: The Plesk panel web server has failed to start.
Possible cause: Corrupted configuration, port conflict, certificate or disk issue.
Meaning: Plesk panel PHP engine is not working.
Possible cause: Packet corruption, memory, permission, or update issue.
Meaning: The panel service is running but has been denied by access authorization.
Possible cause: IP access restriction, reverse proxy, or security rule.
Meaning: The name in the panel certificate does not match the accessed hostname.
Possible cause: Access with IP, wrong hostname or old certificate.
Meaning: Another process is using the Plesk panel port.
Possible cause: Port conflict or incorrect proxy configuration.
Meaning: The panel service's connection or source capacity is full.
Possible cause: Bot scanning, DDoS, long tasks or low resources
No records matching this expression were found.
Commands are for root access. Collect only status and logs first; Do not change the permanent setting without seeing the reason.
systemctl status sw-cp-server sw-engine --no-pagerShows the status of the Plesk panel web server and PHP engine.
ss -lntp | grep -E ':8443|:8880'
lsof -nP -iTCP:8443 -sTCP:LISTEN 2>/dev/nullShows which process is listening on ports 8443 and 8880.
curl -vkI --connect-timeout 5 https://127.0.0.1:8443/Measures the response of the panel service via localhost outside the firewall.
journalctl -u sw-cp-server -n 100 --no-pager
tail -n 150 /var/log/plesk/panel.logService start and panel application errors are displayed.
nft list ruleset 2>/dev/null | grep -n '8443'
iptables -S 2>/dev/null | grep -E '8443|8880'Finds the panel port-related rules in the operating system firewall.
fail2ban-client status 2>/dev/null
fail2ban-client status plesk-panel 2>/dev/nullPlesk panel jail and blocked IP status
plesk repair allInteractively check Plesk components; it is preferred to do this off-peak on a busy server.
First, perform a local service test, then check port, firewall, IP block, and panel configuration in that order.
Access the server via SSH if the panel is not opening. If SSH is not available, the issue is likely related to network or server access layer before Plesk.
Locates the service issue by separating it from the external network.
curl -vkI https://127.0.0.1:8443/Record the first cause of the startup error before restarting the service if it is closed.
systemctl status sw-cp-server sw-engine --no-pagerIf the local test is successful, the OS firewall, provider security group, Fail2Ban, and administrator IP change are checked.
The hostname A/AAAA record must be resolved to the correct IP and the panel certificate must be valid for the same name.
If the panel is partially accessible, use the /repair/ path or Plesk repair via SSH; then repeat external and local testing.
curl -vkI https://hostname:8443/repair/Fail2Ban, Plesk Firewall, and provider-side IP restrictions are checked. Mobile internet provides a test separation.
The panel service is healthy; firewall, NAT, security group, or network routing takes priority.
sw-cp-server startup log, port conflict and disk fullness are checked.
This is not a timeout. The hostname, certificate assignment, and accessed URL must have the same name.
Long-running Plesk tasks, CPU/RAM, panel log, and external connection load are checked.
Plesk interface uses 8443 port by default for HTTPS, and 8880 for HTTP. 8443 is preferred for secure access.
Timeout usually indicates that packages were unable to receive a response; refused indicates that the target was reached, but no service was available on the port.
Not always. The panel service can also be broken independently and web sites can continue to work
Usually accessed via https://hostname:8443/repair/ with admin credentials. SSH is required if the panel service is completely closed.
No. It creates a security risk except for short diagnostic checks. Only necessary ports and trusted IPs should have rules set up.
The Plesk control panel server component serves the Plesk control panel. sw-engine is the PHP engine for the panel application.
Connect to the 8443 port with hostname using openssl or browser and examine the CN/SAN fields and expiration date of the certificate.
By analyzing cPanel, WHM, CloudLinux, LiteSpeed, MariaDB, Exim and security layers together, we fix the root cause of the failure instead of just removing the service.