Increase robustness of SSL renewing #393
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yep. This should be merged first and then I can rebase #311 . |
The playground had an error renewing: ``` Error -> One or more domains had a problem: error: 0 :: POST :: https://acme-v02.api.letsencrypt.org/acme/finalize/514094497/249375107307 :: urn:ietf:params:acme:error:rateLimited :: Service busy; retry later., url: ``` Our renew timer runs once a week at midnight UTC, and my guess is that lots of other servers across the world are doing the same thing causing temporary overloads. These changes are intended to help spread out the load a bit and retry when an error happens anyway.
shepmaster
force-pushed
the
robust-ssl-renew
branch
from
256c1f0
to
9b86e3a
Compare
This was referenced Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The playground had an error renewing:
Our renew timer runs once a week at midnight UTC, and my guess is that lots of other servers across the world are doing the same thing causing temporary overloads. These changes are intended to help spread out the load a bit and retry when an error happens anyway.