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

Plesk CP will not use default certificate

K

KeithD

Guest
I have a certificate at https://www.serverlogin.com that works fine. That certificate is set as the Default on Server>Certificates.

But when I try to access Plesk Control Panel https://www.serverlogin.com:8443 I get an invalid cert made out to Plesk instead of the one to that domain.

How do I tell Plesk CP to use that domain's cert? I've done this on older Plesk versions so I can direct all domains to use the same https://www.serverlogin.com:8443 for accessing the CP. This is on a Plesk 8.1 CentOS.

Additional question which may have bearing on this - How do I set the default domain for an IP? At Server>IP I have "none" for Default Domain for all IPs, shared and exclusive. How do I set those?
 
Back
Top