3

I am using Let’s encrypt on my production server to handle SSL certificate. My website certificate will expire next week so I regenerated it using the letsencrypt-auto renew command (I didn’t set cron task yet)

The last log I get is 2016-08-20 17:12:20,305:DEBUG:certbot.renewal:no renewal failures which mean certificate has been successfully regenerated

But when I go back to my website and check the certificate properties it still says that it will expire next week.

So:

  • Does Let’s Encrypt wait the last day of certificate to update its new expiration in browser ?
  • Did my new certificate is not working properly which explain browser still give me next week as expiration ?

Can someone help me to clarify the way certificates expiration date works ?
Thanks for your help !

anthony
  • 640
  • 1
  • 10
  • 32

3 Answers3

9

Thanks to Let's Encrypt community, I have been able to figured out what was wrong: I just needed to reload my Nginx server and it updated the expiration time for certificate !

anthony
  • 640
  • 1
  • 10
  • 32
0

I'll just follow up here with a bit more information, for those who are looking at this question for answers.

If you have the renew running in crontab, and you have this issue, you can specify command option: --post-hook 'some command'. And that 'some command' should be the shell command necessary to reload your web server.

wndxlori
  • 196
  • 2
  • 10
  • Now if I could just figure out why I'm still getting emails from LetsEncrypt saying my cert is expiring... (it's not). – wndxlori Jan 11 '17 at 00:40
0

Though coming late, might be useful to someone. Even after restarting apache I still had the issue. A full machine reboot solved it for me. This will be useful only if you have full control of the server machine though.

user3214824
  • 11
  • 1