Post-mortem: The certbot package defined a systemd timer and a /etc/cron.d/ entry for renewal, so my own crontab entry that defined a post-hook never got to do the renewing
@Gargron put it down to a systemd issue and no one will doubt it :)
@Gargron had the exact same issue recently. fun. fun. fun.
@gargron I had exactly the same problem when I started using certbot, super annoying!
@C_Chell You might want to look at running certbot in certonly/webroot mode, it's a lot less intrusive.
@benofbrown I change it recently, but I have to recheck the configuraiton soon to be sure.
@Gargron I think I also had this issue, thanks for diagnosing
@Gargron had this a year ago. it's sad https://blog.valerauko.net/2018/01/07/about-certs-for-version-control/
@Gargron I've added my hook to the certbot config file before so I could just rely on the default timer - but the documentation on how to do this (and on the config file format in general) was really bad or missing.
@Gargron Strongly recommend acme.sh : )
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!