Facebook
Twitter
BizMarquee
Basic Pleskian
I secured my panel with a Lets Encrypt! certificate, but it did not automatically renew, and it expired and now my panel is not secured, but SA says it is. Is there a command line I can run to re-secure my panel?
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
Resolved Security Advisor - Plesk Panel Certificate Expired
- Thread starter BizMarquee
- Start date
U
UFHH01
Guest
Hi BizMarquee,
Since Plesk Onyx, Plesk provides the following wiki - article for your question:
Could you pls. explain, what "SA" should stand for? You should consider to refrain from abbreviations, because due to national and international differences such abbreviations can lead to misunderstandings.
Since Plesk Onyx, Plesk provides the following wiki - article for your question:
=> Secure Plesk Panel · plesk/letsencrypt-plesk Wiki · GitHub
... and with the newest Plesk Let's Encrypt Extensions, you should consider to inspect Let's Encrypt issues in your "panel.log".
... and with the newest Plesk Let's Encrypt Extensions, you should consider to inspect Let's Encrypt issues in your "panel.log".
BizMarquee
Basic Pleskian
SA = Security Advisor.
WielM
New Pleskian
I'm having the same problem. My secured sites worked for 3 months and than expired. They were renewed as I can see using
where I can read:
But the expired sites still show the privacy error page (NET::ERR_CERT_DATE_INVALID)
A manual renew also didn't work (which is not surprising as it seems that the cert files have the right dates)
Code:
openssl x509 -in cert-xxxxxx -text -nooutwhere I can read:
Code:
Validity
Not Before: Sep 25 23:53:00 2017 GMT
Not After : Dec 24 23:53:00 2017 GMTBut the expired sites still show the privacy error page (NET::ERR_CERT_DATE_INVALID)
A manual renew also didn't work (which is not surprising as it seems that the cert files have the right dates)
Last edited:
U
UFHH01
Guest
Hi WielM,
pls. have a look at your "panel.log" ( => /usr/local/psa/admin/logs/panel.log - /var/log/plesk/ ), as Let's Encrypt logs its actions there. If you desire help for further investigations, pls. consider to post the corresponding entries from your logs, so that people willing to help you have something to start with their investigations.
Additional informations:
pls. have a look at your "panel.log" ( => /usr/local/psa/admin/logs/panel.log - /var/log/plesk/ ), as Let's Encrypt logs its actions there. If you desire help for further investigations, pls. consider to post the corresponding entries from your logs, so that people willing to help you have something to start with their investigations.
Additional informations:
Sometimes, it is as well a good idea to change the log - level ( TEMPORARILY! ), to get more informations in Plesk - log - files:
WielM
New Pleskian
Solved!
Obviously, the renew process restarts apache and nginx. The nginx restart failed during restart (didn't pass the config-test) and therefore the old instance of nginx kept running, with the old certificate information! After repairing the nginx config, the renewed certificate became active after an nginx daemon restart.
Maybe you have the same problem, BizMarquee?
Obviously, the renew process restarts apache and nginx. The nginx restart failed during restart (didn't pass the config-test) and therefore the old instance of nginx kept running, with the old certificate information! After repairing the nginx config, the renewed certificate became active after an nginx daemon restart.
Maybe you have the same problem, BizMarquee?
Similar threads
