• 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 WWW Subdomain not secured when using wildcard certificate

TheColin21

New Pleskian
Hi,

I have a domain which is secured with a wildcard Let's Encrypt certificate.
I am using this certificate to secure a subdomain. For this subdomain Plesk shows, that the 'WWW'-subdomain is not secured. I thought, that my wildcard certificate should cover these "subsub"-domains. Am I wrong there or can I somehow get this to work?

Best regards
Colin
 
Wildcard certificates work for +1 level only, means that creating a wildcard certificate for *.example.com:

1. Will work for subdomain.example.com.
2. It won't work for www.subdomain.example.com or sub2.subdomain.example.com since it is considered 2 levels already.
 
Back
Top