• 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 Plesk Lets Encrypt outdated, would not update

maennchen1

New Pleskian
Hi!
My Plesk (Version 18.0.26) certificate is outdated. So I decided to renew it manually. After that it's still outdated.
I deleted it (Home > Tools & Settings > SSL/TLS Certificates) regarding to this docs. And create a new certificate. My browser always says I got that same old certificate... :(
I tried another browser on another network, cleared cache a.s.o.. Always the same old certificate.

Checked date from "SSLCertificateFile" (/etc/apache2/plesk.conf or /etc/nginx/plesk.conf.d/server.conf) in /opt/psa/var/certificates/ and it's from now. Are the certificates cached?
How can I fix it?
Bildschirmfoto 2020-05-25 um 15.32.16.png
 
  1. Connect to the server via SSH
  2. Get the PID of the sw-cp-server processes:
    Code:
    # ps awufx | egrep sw-cp-server | grep -v grep | awk '{print $2}'
    1594
  • Kill the sw-cp-server processes:
    Code:
    # kill -9 1594
  • Restart the sw-cp-server service:
    Code:
    # systemctl restart sw-cp-server.service
this should help
 
Back
Top