• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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