• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Can't accessing Plesk log in page over HTTPS

Patashoow

Basic Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
Plesk Obsidian 18.0.60
Hello,

When I try to access my Plesk panel through the URL "https://domain.tld:8443" it says that the connection is not secured even if my SSL certificate is fully valid for "domain.tld". So how could I fix that?

Everything was working just fine few minutes ago.
 
And is domain.tld different from the server host name?

By default only the SSL certificate for the host name is used for securing traffic on port 8443.
 
In fact the host name is "mail.domain.tld". The SSL works perfectly for "domain.tld". Is there anything I should do?
 
If the hostname is mail.domain.tld, then only mail.domain.tld wil have a secured connection on port 8443. Secured connections for port 8443 on other domains is currently not supported. You can vote for that feature here: Supporting SSL resellers
 
Back
Top