Issue Lets Encrypt and Subdomains

[Azurel]

Plesk shows for subdomains, which have already a valid certificate

SSL/TLS Certificates
WWW domain not secured

There is
- Domain subdomain.domain.tld SECURED
- Domain with the "www" prefix www.subdomain.domain.tld NOT SECURED, because its not needed.

Is it really necessary to put the unnecessary "www" for subdmains here?!

 

[pleskpanel]

I've always thought that Plesk should offer a third checkbox when issuing SSL certificates to the effect of "Secure sub-domains with www" when a sub-domain is included given that sub-domains aren't often added with an extra www DNS record and currently the case you identified would cause the issuance to return an error.

But perhaps there is a case why this isn't present in the panel that I'm not aware of.

 

[learning_curve]

We don't use the www prefix on any of our subdomains, but... AFAIK (& this was posted recently in a different thread) a normal Wildcard Certificate only covers one level of subdomains anyway. For Example: If you had a wildcard Wildcard Certificate for *.yourdomain.com, then that will be valid for subdomains like, say 123.yourdomain.com or 456.yourdomain.com, but not 123.456.yourdomain.com or, as shown in your own exmple www.subdomain.domain.com