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