• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Certificate not valide

CobraArbok

Regular Pleskian
I have migrated websites from an old server to a new server.
They had a Let's Encrypt certificate and still a Let's Encrypt certificate.

But previously typing mydomain.tld the user was automatically directed to https: //mydomain.tld without errors, instead now the user receives an "invalid certificate" message.
In Chrome the error is "NET::ERR_CERT_COMMON_NAME_INVALID"

What else is there wrong with this configuration?

In the Hosting settings, the option "Permanent SEO-safe 301 redirect from HTTP to HTTPS" is enabled.
I use the same certificate for the domain and for all its subdomains.
Obviously different certificates for the different domains.
 
Back
Top