• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Question Use Let's Encrypt wildcard cert to secure Plesk Panel and Site Preview URLs?

gbotica

Regular Pleskian
Hi,

On Plesk 17.9 I've been using an LE certificate to secure the actual Plesk Panel site for a while now. Although, back when I set this up I had to create a "dummy" website with the domain that the Plesk Panel uses, otherwise installing the LE cert for the Panel would fail. (I think this issue has been resolved now, but I haven't tested it).

So now that LE does wildcard certificates: does this mean we can install a LE wildcard cert for securing Plesk Panel and also have it work for Plesk Preview URLs?

Let's say my Plesk Panel URL is https://server1.webhost.com:8443

A preview URL on this server might be: https://mywebsite.com.123-123-123-123.server1.webhost.com

Should I be able to install a wildcard certificate for Plesk Panel and have it also available for Site Preview URLs?

Thanks in advance for any advice you can offer.
 
Back
Top