• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Admin panel expired certificate

RingoStar77

Basic Pleskian
Server operating system version
Debian 10.13
Plesk version and microupdate number
18.0.46.2
Hi!

I cannot access the plesk admin panel through SSL on domain.com anymore. Firefox says 'SEC_ERROR_EXPIRED_CERTIFICATE'.

Plesk was configured to use an existing let's encrypt certificate from domain.com

I can call domain.com without any problems. Certificate is fine there. But as soon as I want to access the admin panel under domain.com:8443 I get the above-noted error. I have already tried to renew the certificate, but this did not help. I also did 'plesk repair web -sslcerts domain.com' - no errors were resolved.
 
Thanks for your quick reply! I was able to login but I don't know, how to reconfigure the certificate. As I mentioned above, I am using an existing one.
 
When you navigate in Plesk to Tools & Settings > SSL/TLS Certificates, what's selected/listed after "Certificate for securing Plesk"?
 
What's the reason you've selected a certificate from a different domain to secure Plesk, instead of the default Lets Encrypt certificate from server pool?
 
There's actually no reason for this. I have changed the setting to use Let's Encrypt from the server pool, but the issue persists.
 
Makes more sense to to use the Let's Encrypt from the server pool, as that the default certificate to secure Plesk. Now to might need to renew the certificate again by clicking the + Let's Encrypt button on the Tools & Settings > SSL/TLS Certificates page.
 
Sorry to hear that didn't solve your issue. Only suggestion I have left is to open an ticket with Plesk support so they can investigate the issue on your server directly.

 
Could be that
# service sw-engine restart
loads the correct certificate after the change in the panel.
 
I have consulted the technical support and they have fixed it with the following command:

plesk bin server_pref --update -panel-certificate "Lets Encrypt certificate"
 
Back
Top