• 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.

CA certificate for self-signed SSL certs

W

wesindc

Guest
I'm setting up self-signed SSL certificates for several domains. When the site is accessed via HTTPS:// the self-signed certificate the CA Authority is listed as not being trusted. Does Plesk have a default CA Authority certificate to use for self-signed SSL certificates? Running Windows Plesk 7.5.6
 
"self-signed" means exactly that -- not signed by a CA.

Certificates are a bit of a misnomer, actually.

What a certificate actually is, is a public key, that is then signed by someone else's private key.

However, a self-signed certifcate is just a public key signed by it's OWN private key.

You use the "CA Cert" section when using someone like GoDaddy's certificate services, where you need to upload an "intermediate" certificate, since GoDaddy's root cert is not installed in most browsers.

Since GoDaddy's root cert is actually signed by another organization, in order to have browsers recognize it, you have to pass the intermediate cert down the line.
 
Back
Top