Article ID: 113605, created on Apr 4, 2012, last review on May 10, 2014

  • Applies to:
  • Plesk for Linux/Unix

Check the Web Interface

Try opening it in the browser:
 
https://<server_ip or hostname>:8443

If it shows a Parallels Plesk Panel (PP) login page, try logging in:               

If the login is successful, but you still doubt that your PP installation is consistent, refer to this article:

113604 Identifying a failed Parallels Plesk Panel for Linux upgrade

If you see an error message, you may search for it in our knowledgebase.

If you see nothing and the login page is not opening, try using telnet to connect to port 8443:

# telnet <server_ip> 8443

             If this command returns a “Request timed out” error, check if port 8443 is blocked by a firewall on the server where PP is installed.

If it acts as if a connection has been established, try opening the Web Interface in a different browser.

Check services

If none of the above troubleshooting advice helps, an issue with the control panel service is likely indicated:

Check whether the control panel service is running:
# /etc/init.d/psa status
sw-cp-serverd (pid 1192) is running...

If you see “psa is stopped” instead, try starting it:
# service psa start

Even if the service starts with no errors, it is recommended that you check the service’s error log file (/var/log/sw-cp-server/error_log) to see why it failed.

If you find an error message after taking the above steps, try searching for it in our knowledgebase.

If the above steps produce no errors, but you still doubt that your Parallels Plesk Panel installation is functioning properly, you may check your installation for consistency as described in this article:
 

113604 Identifying a failed Parallels Plesk Panel for Linux upgrade

29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF