Rate-limiting on the Lets Encrypt API causes letsencrypt:enable to hang rather than throw or warn

[bumblefudge]

• I don't think it's a rate-limiting issue, since i'm not getting error messages to that affect and i have been attempting trying again days later all week
• more info here, i tacked on my issue to a closed one i suspect may be relevant, in case it makes more sense to re-open than to treat here

[bumblefudge]

SURPRISE i was just rate-limited for fumbling too many times in a 24 hour window! maybe there could be an error or warning instead of a timeout when the underlying API response is

?

[josegonzalez]

We actually use certbot so maybe this should be reported to them upstream?

[belal-i]

Hi,

I am facing a similar issue ( #378 ).

I found this workaround, which I run before running dokku letsencrypt:enable myapp

dokku letsencrypt:set myapp graceperiod 30

This fixes the hanging issue, but I believe that this is not the correct way to do it, because if I'm not mistaken, now the certificate won't be renewed until 30 seconds before expiry, which is probably "cutting it close".

I believe the root cause is a semantic mismatch in the code between the graceperiod setting, and lego's --cert.timeout flag. I submitted a PR to fix this issue: #380 ... hope it helps :-)

Kind regards