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
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:
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 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: