Articles in this section

See more

Domain is not secured over WWW even though Let's Encrypt certificate is installed

Avatar
Dinara Aspembitova
Updated
Follow
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:

  1. Login to Plesk;
  2. Open Domains > example.com > SSL/TLS Certificates
  3. Check the option Include a "www" subdomain for the domain and each selected alias;
  4. Click Reissue Certificate.

Comments

2 comments

Sort by Date Votes
  • Avatar
    Azurelink

    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.

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    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.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles