Applicable to:
- Plesk for Linux
Symptoms
-
A wildcard certificate is issued for example.com with 'secure www' option enabled.
-
alias.com and subdomain.example.com are added to the list of issued certificates.
-
On opening https://www.alias.com, a warning about incorrect certificate is shown, for example:
PLESK_WARN: HSTS warning - incorrect cert
Cause
"www" of domain alias and subdomain are not added to SANs list and therefore are not secured by the Wildcard certificate.
This is Let's Encrypt extension bug with ID EXTLETSENC-568 which is planned to be fixed in future updates.
Resolution
As a workaround, it's possible to order few certificates:
-
Go to Domains > example.com > Let's Encrypt
-
Issue a wildcard certificate _without_ including the aliases.
Note: As a result, a certificate which secures "example.com" and " * .example.com" will be obtained.
-
Go to Domains > example.com > SSL/TLS Certificates > Lets Encrypt example.com
-
Rename it to, for example: "Wildcard example.com".
-
Go to Domains > example.com > Let's Encrypt
-
Issue an non-wildcard certificate with marked "Include a "www" subdomain for the domain and each selected alias" and "Secure webmail on this domain" checkboxes and added all aliases to the right-side list.
Note: As a result, will be obtained a certificate for "example.com", "www.example.com", "alias.com", "www.alias.com", etc aliases.
-
Go to Domains > one.example.com > Hosting Settings
-
Select a "Wildcard example.com (one.example.com)"certificate.
Note: Repeat this step (8-9) for each subdomain (two.example.com, three.example.com, etc...)
Comments
2 comments
would be really nice if *.example.com i mean wildcard SSL would be working...
Hello @Jan,
Thank you for the feedback.
Generally, a wildcard certificate may be issued using this instruction.
But indeed, currently due to this bug www is not included.
Please sign in to leave a comment.