• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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