Simultaneous waiting for several dns-challenges
See original GitHub issueI’m using DNS-provider located far away from Let’s Encrypt servers (Yandex). So I have to use long waiting time, like 12 hours (LEXICON_SLEEP_TIME=43200
) to update DNS records. And I need several wildcard domain names. So now it takes 12 hours for each. Could be logic refactored to start all challanges simultaneous and then wait LEXICON_SLEEP_TIME
?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Simultaneous waiting for several dns-challenges · Issue #59 ...
I'm using DNS-provider located far away from Let's Encrypt servers (Yandex). So I have to use long waiting time, like 12 hours (LEXICON_SLEEP_TIME=43200)...
Read more >Gitlab Runner not able to resolve Gitlab URL - Kubernetes ...
I suspect some of the issues and the variance folks are seeing relates to how the cluster ingress is configured. Since the default...
Read more >ACME Orders and Challenges - cert-manager Documentation
After a Challenge resource has been created, it will be initially queued for processing. Processing will not begin until the challenge has been...
Read more >How to Troubleshoot DNS Errors (Timeouts, Codes & More)
Learn how to troubleshoot DNS errors such as timeouts, codes, and more. Answer the question of what is a DNS error and why...
Read more >How To Acquire a Let's Encrypt Certificate Using DNS ...
DNS validation allows for certificate issuance requests to be verified using ... dns-01 challenge for your-domain Waiting for verification.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Upcoming version 3.4.0 integrates this feature!
It was released yesterday. Please close this ticket now.