News for hackers. Stuff that matters.
Re:CA Root expired on 30 May 2020 by kl4m on Saturday May 30, 2020 @06:05PM (#23365179)
Good old "cert replaced but apache/nginx failed to reload" has bitten me more than once...
Re:CA Root expired on 30 May 2020 by Sebb767 on Saturday May 30, 2020 @08:03PM (#23365978)
Me too! Especially with the short expiration times of LetsEncrypt. But I really don't want to put `nginx -s reload` in the Cron, in case I'm tinkering with the configs and they're suddenly live (which only really happens at staging or at home of course, but still).
Re:CA Root expired on 30 May 2020 by emilburzo on Sunday May 31, 2020 @03:59AM (#23368010)
You can use `nginx -t && nginx -s reload` for that.

It will first check the configs/paths, and only then, if successful, signal nginx to reload.

Re:CA Root expired on 30 May 2020 by Sebb767 on Monday June 01, 2020 @07:31AM (#23377401)
That's what I usually do. My problem is that I might be adding a location and nginx reloads between that and adding access restrictions (i.e. because I took a break to google).
Re:CA Root expired on 30 May 2020 by amaccuish on Sunday May 31, 2020 @07:07AM (#23368741)
Certbot has deploy hooks which is where I'd put the nginx reload statement. The hooks are run automatically when a new certificate is issued.
Re:CA Root expired on 30 May 2020 by Sebb767 on Monday June 01, 2020 @07:29AM (#23377375)
Oh, that's a great idea! Thanks :)