Articles in this section

Subdomain with www prefix is marked as not secured, even though wildcard certificate is installed for main domain in Plesk

Alexander Davydov
Updated
Plesk for Windows Plesk for Linux kb: technical

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Symptoms

Second level subdomain test.login.example.com is marked as "not secure", even though a wildcard certificate is installed for *.example.com

Cause

Wildcard certificates cover only one level of subdomains.

Resolution

Issue certificate for test.login.example.com including www prefix.

Was this article helpful?

Comments

1 comment
Date Votes
  • Avatar
    Scott Bourquin

    creating a valid secure connection to the plesk panel has been very frustrating.  

    Following the directions at IONOS to add a subdomain, I am unable to secure the plesk panel with its own certificate or a wildcard certificate or a free certificate.  I either get "Not Trusted" or mismatch.  How does it make sense that Plesk doesn't have some very simple method of adding a certificate so the SSL is forceable and doesn't have to be bypassed to access the server.  

     

    0

Please sign in to leave a comment.