• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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