You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bit of a feature request. I think this could be just an oversight.
Background: all our domains were configured, for whatever reason, to use certbot in standalone mode. I'll probably change this. So they stop & start httpd.
How to reproduce (e.g Puppet code you use)
Create any letsencrypt rule using cron to run certbot with before/after hooks.
What are you seeing
When certbot fails for any reason in a cron run, there's no way to run a command if it fails, only if it succeeds.
Bit of a feature request. I think this could be just an oversight.
Background: all our domains were configured, for whatever reason, to use certbot in standalone mode. I'll probably change this. So they stop & start httpd.
How to reproduce (e.g Puppet code you use)
Create any letsencrypt rule using cron to run certbot with before/after hooks.
What are you seeing
When certbot fails for any reason in a cron run, there's no way to run a command if it fails, only if it succeeds.
So for instance, if you do:
then HTTPD will be stopped, certbot fails, and httpd will not be restarted, even if the failure was transient.
I'd like, perhaps, a "cron_after_command".
The text was updated successfully, but these errors were encountered: