• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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