• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Outdated SSL certificates

ItsPerona

New Pleskian
Server operating system version
Ubuntu 22.04.1 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.49
A few months ago I updated my dedicated server with plesk from ubuntu 20 to 22, when I made the change, I had some certificates in plesk assigned to some subdomains.

These subdomains currently have outdated SSL certificates because they continue to use the old certificate generated when I was using Ubuntu 20. These certificates do not appear in plesk and from Ubuntu Server when executing certbot it tells me that there are no certificates.

From Plesk it allows me to generate new certificates without a problem, but the websites continue with the old expired certificates.
 
Certbot should not have played a role on a Plesk installation. Were the old certs generated "manually" on the console and then uploaded to Plesk? Maybe you can review the SSL certificate drop down box on the "Hosting Settings" page of the domain(s) and select the correct, new LE cert from there? If that box already shows the correct selection, it will probably help to run
# plesk repair web <domainname>
with <domainname> being the domain that needs the cert update, because the command will remove and recreate the web server configuration files for the domain. It will use the current database entries from the Plesk psa database for it so it will use the right cert.
 
Back
Top