• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Outdated SSL certificates

ItsPerona

Basic 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