Issue Plesk login page is not loading

[Farid]

Have you tried opening the login page with :8080 instead of :8443?

I'm getting message ERR_EMPTY_RESPONSE with port 8080

 

[Peter Debik]

:8880
?

 

[Farid]

Both 8080 and 8880 are making same results for me

 

[Peter Debik]

@Farid Than it is not the "exact same" issue. In your case you'll need to check whether sw-engine and sw-cp-server processes are running. If they are not, please start them.

 

[jkunnel@orchidglobal.]

Hi,
port 8080 is also open.
This is a strange problem, and I am awaiting for anyone to share a solution

Regards
Jomon

 

[Farid]

@jkunnel@orchidglobal. in any case, have you changed the hostname of Plesk and/or customized the url?
I get this issue just after I changed the hostname of Plesk server.

 

[abconline]

I've the same problem. I currently use a customized hostname for my webserver. If I try to enter using the IP-ADDRESS:8443 I can enter. With HOSTNAME:8443 I receive an error (seems like the firewall lock the access using an hostname.) Please write in this thread if you found a solution to use hostname....

 

[Peter Debik]

What is an "error ... like the firewall lock", could you please be more specific what exactly is shown as an error message?

 

[abconline]

 

[Peter Debik]

Did you verify that the domain name you try to use is routed to the IP address of that server and that is set correctly in the server's custom domain configuration? You do not need to add the 8443 port if you use a custom domain name.

 

[abconline]

until the latest versions of Plesk, until a few weeks ago, I access all the web servers using "https://server.domain.com:8443" with the latest updates all the servers are blocked and only work using ipaddess:8443

If you want, with private message, I can send you the addess of all the webservers.

 

[Peter Debik]

@abconline, although I'd like to help directly, due to legal reasons (signing privacy agreement etc.) the team cannot provide on-server support here on the forum. Instead, please open a ticket with support, sign the (online) agreement for server access, then support staff can examine the issue and very likely also fix it directly on your server. https://support.plesk.com

 

[Avery78]

If the Plesk server does not have enough free disk space, this might occur. You should rotate the log files in /var/log/ or delete any unnecessary files if the disk space use is 100%. See the section on Log Rotation for further details.