-
-
Notifications
You must be signed in to change notification settings - Fork 709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's Encrypt "Service Busy" response #886
Comments
Retries will be supported in an upcoming release but I can't give you any specific time for that. I have a big project ending this month and hope I'll be able to work on a bit of delayed work on dehydrated after that. |
hi - any news on this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
Based on https://community.letsencrypt.org/t/new-service-busy-responses-beginning-during-high-load/184174, Let's Encrypt is now sending 429 responses back when the requestor is not rate limited, but when the Let's Encrypt servers are too busy.
Will dehydrated-io support this error in that it waits for the retry-after period and then retries, or is it the projects response that all users should implement this retry logic themselves?
Best regards,
Guus
The text was updated successfully, but these errors were encountered: