• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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