Plesk for Windows
Plesk for Linux
kb: technical
ext: le
ABT: Group A
Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
- Warning in browser is shown whenever the domain with installed Let's Encrypt SSL is accessed with www-prefix like
https://www.example.com:CONFIG_TEXT: NET::ERR_CERT_AUTHORITY_INVALID
CONFIG_TEXT: Your connection is not private
This server could not prove that it is www.example.com; its security certificate is from example.com. This may be caused by a misconfiguration or an attacker intercepting your connection. -
Certificates is shown "WWW domain not secured" under Domains > example.com > SSL/TLS Certificates
Cause
The certificate was issued only for the domain example.com, without www-prefix.
Resolution
Reissue certificate with www-prefix:
- Login to Plesk;
- Open Domains > example.com > SSL/TLS Certificates
- Check the option Include a "www" subdomain for the domain and each selected alias;
- Click Reissue Certificate.
Comments
2 comments
Does this also apply to subdomain, e.g., https://www.mysubdomain.topleveldomain.com ?
We are getting this error. We have a wildcard SSL issued in Plesk as a wildcard for the TLD. And then one issued in the subdomain without the "www" checked.
Hi,
Wildcard certificates works 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.
Please sign in to leave a comment.