x/crypto/acme: Retry on LetsEncrypt rate limit #40161
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using?
What did you do?
I called
acme.Client.AuthorizeOrder
when the renewal rate limit for the desired domain has been exceeded.See: https://letsencrypt.org/docs/rate-limits/
What did you expect to see?
I expected the call to fail quickly and return the rate limit error. There is no value in retrying for a rate limit failure.
What did you see instead?
The acme HTTP client code will retry for 429 errors.
In the case of a LetsEncrypt rate violation LetsEncrypt returns 429. For example:
This results in the retry code executing until the context timeout is reached. If the context has no timeout then the code will make calls to LetsEncrypt forever.
The text was updated successfully, but these errors were encountered: