• 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 is using correct SSL cert; site is stuck with deleted default cert???

G

grimbergen

Guest
I've installed the SSL cert in the main server, and it went in without errors.

Then i checked the box next to the cert and clicked "setup", which caused Plesk to restart with the new SSL cert.

I then deleted the original default cert, and then I stopped/started apache.

I went back to the domain I created to verify that the it had picked up the new cert in the setup page of that domain.

However, the domain site is still using the default cert that is deleted! Plesk (accessed via IP), however, is now using the new, correct cert.

How can this be? Did I miss a step? thanks
 
Back
Top