I've said this in the past, certbot was badly coded, used too much memory and lacked vision. But there are two great alternatives, written as bash scripts (thats right.. bash scripts!)
https://github.com/acmesh-official/acme.sh https://github.com/dehydrated-io/dehydrated give them a try, they are very nicely coded, support plugins, various popular cloud and DNS providers and support all the latest ACME protocol features. They don't only work for Let's Encrypt, they support other free certificate providers as well. They work on all popular *BSD systems, Linux distros (Fedora, Ubunty, Alpine, etc) and a bunch of embedded devices. On Sat, 22 Apr 2023 12:02:34 -0400 Viktor Dukhovni via Postfix-users <postfix-users@postfix.org> wrote: > On Sat, Apr 22, 2023 at 11:25:14AM -0400, Viktor Dukhovni via Postfix-users > wrote: > > On Sat, Apr 22, 2023 at 01:08:06PM +0200, Matus UHLAR - fantomas via > > Postfix-users wrote: > > > > > >You should set a POST_HOOK in certbot renew (assuming you're using > > > >certbot, that is) that restarts or reloads the web server. > > > > > > I guess this exactly what failed. > > > > The "post hooks" in certbot are not *reliable*. If for some reason they > > don't succeed, they're retried on the next scheduled certbot run. This > > is a design flaw. > > Oops, I meant to write "*not* retried". > > -- > Viktor. > _______________________________________________ > Postfix-users mailing list -- postfix-users@postfix.org > To unsubscribe send an email to postfix-users-le...@postfix.org _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
