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
Originally created by @PHPGuus on GitHub (Sep 19, 2022).
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
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.
@lukas2511 commented on GitHub (Sep 19, 2022):
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @PHPGuus on GitHub (Sep 19, 2022).
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
@lukas2511 commented on GitHub (Sep 19, 2022):
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.
@bschelling commented on GitHub (May 13, 2023):
hi - any news on this?
@ThiefMaster commented on GitHub (Jan 2, 2025):
Hey, any updates on this?
@bleve commented on GitHub (Sep 30, 2025):
There is a very simple config option to get this working:
CURL_OPTS="--retry 5"