Works for me, too! Error occured over the weekend, today morning I did search this forum for the error, found this posting and fixed it. Less than ten minutes for searching and fixing. Thank you!!! 
LetsEncrypt - SSL certificate renewal not working - Cron job abort due to missing bind variable
-
- patched
- web4you
- Closed
-
-
Can confirm the solution from @Nuxwin's earlier post works like a charm on Ubuntu 16.10, 18.04, Debian 8 and Debian 9 on i-MSCP 1.5.3.
-
-
I meantioned it worked earlier, but it seems it does request the renewal and receive the signed certificate, but it doesn't seem to be updated in the host, if I check the certificate in browser it's still the old version. You can investigate on my server if you wish, you have access already (jo****.pl*.*l).
This is very strange!
-
if I check the certificate in browser it's still the old version.
Close your browser (fully). Then retry.
-
-
Close your browser (fully). Then retry.
This doesn't help, also sslshopper decoder says the same, very strange.
The let's encrypt interface does say the date 3 months in advance...
-
This doesn't help, also sslshopper decoder says the same, very strange.
The let's encrypt interface does say the date 3 months in advance...
Did you at least tried to restart Apache2 ... Please check the cert under /etc/letsencrypt with help of openssl: openssl x509 -noout -text -in <certpath>
Anyway, the issue here has nothing to do with the thread
-
-
Did you at least tried to restart Apache2 ... Please check the cert under /etc/letsencrypt with help of openssl: openssl x509 -noout -text -in <certpath>
Anyway, the issue here has nothing to do with the thread
Thanks for youre instructions.
The SSL Shopper (and my browser) give the end date: July 19, 2018
The actual certificate in /etc/letsencrypt says: Oct 7 21:00:08 2018 GMT
Somehow the certificate is not used for apache, even when I restart apache.
-
Display More
Thanks for youre instructions.
The SSL Shopper (and my browser) give the end date: July 19, 2018
The actual certificate in /etc/letsencrypt says: Oct 7 21:00:08 2018 GMT
Somehow the certificate is not used for apache, even when I restart apache.
Well, send me all access data through my email, then I'll investigate. Don't forget to give me the domain name involved too...
-
-
Thanks, it's en route.
-
So, I confirm that there is no problem.
On https://www.sslshopper.com/ssl…tname=grethavanderveen.nl there are a link to force check without caching result:
These results were cached from July 9, 2018, 1:50 pm PST to conserve server resources.
If you are diagnosing a certificate installation problem, you can get uncached results by clicking here.Once done, you get the expected result:
This is confirmed by my browser
-
-
Nuxwin
Set the Label from to be fixed to patched -
Nuxwin
Closed the thread.
