• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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