Raise acme challenge expiration from 180s to 3600s #492
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
aast weekend, acme took tens of minutes to go through for me. This broke the letsencrypt task flow as the challenge token disappeared from the table meanwhile.
|
Changing this value alone will not allow the verification to run longer. |
|
Can you please elaborate? Because the change did resolve the issue for me - the token was still in the table when the verification finished. |
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.
Last weekend, acme took tens of minutes to go through for me. This broke
the letsencrypt task flow as the challenge token disappeared from the
table meanwhile.