• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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