• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Issue Let's Encrypt Not Securing Plesk (8443)

Mark Bailey

Basic Pleskian
Hi,

I used Let's Encrypt to create an SSL certificate for the hostname, which is in the format bb.domain.com. I set the system to use that certificate to secure Plesk itself. If I go to the server's hostname alone in a web browser, I get the default page and the browser says "secure". It shows a certificate from Let's Encrypt. But if I go to bb.domain.com:8443, I get a security warning that the certificate is not trusted. And the certificate info doesn't show Let's Encrypt, it looks like the self-signed cert.

So, the certificate is installed and valid, but doesn't work when accessing Plesk via 8443. What can I do?

Thanks,

Mark
 
Back
Top