• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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

P

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
 
You must log in or register to reply here.

Similar threads

R
Issue SSL/TLS cert for mail server not updating (Lets Encrypt)
Replies
2
Views
2K
tessa67
T
C
Question Plesk Login for Customers over Subdomain with Certificate.
Replies
1
Views
252
Martin Dias
Martin Dias
C
Resolved Plesk mail SSL certificates invalid, common name problems (websites fine)
Replies
4
Views
625
Chucky_213123
C
C
Question How can I secure my Mail with Letsencrypt next to Cloudflares Origin Certificate in Plesk?
Replies
4
Views
1K
cpulove
C
P
Resolved SSL issue for some visitors, but not all
Replies
2
Views
2K
pieterpost
P
Back
Top