starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-13 23:23:32 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Support sequential validations instead parallel validations #544

New Issue
Closed
opened 2025-12-29 01:27:05 +01:00 by adam · 1 comment
adam commented 2025-12-29 01:27:05 +01:00
Owner
Copy Link

Originally created by @marcomsousa on GitHub (Aug 19, 2021).

Support sequential validations instead parallel validations

Right now if I execute dehydrated with two domains:
dehydrated --cron --hook ./hooks.sh --challenge dns-01 --domain a.example.com --domain b.duckdns.org
dehydrated try to deploy the two challenge at the same time. Only after, will responding the challenge for both domains. (parallel)

Since my scenario are:

  • a.example.com CNAME b.duckdns.org
  • _acme-challenge.a.example.com CNAME _acme-challengeb.duckdns.org

I can only validate if I can force dehydrated to do sequential validations.
Deploy 1 challenge, validate 1 challenge, clean, deploy 2 challenge, validate 2 challenge, clean. (sequential).

Originally created by @marcomsousa on GitHub (Aug 19, 2021). Support sequential validations instead parallel validations Right now if I execute dehydrated with two domains: `dehydrated --cron --hook ./hooks.sh --challenge dns-01 --domain a.example.com --domain b.duckdns.org` dehydrated try to deploy the two challenge at the same time. Only after, will responding the challenge for both domains. (parallel) Since my scenario are: - a.example.com CNAME b.duckdns.org - _acme-challenge.a.example.com CNAME _acme-challengeb.duckdns.org I can only validate if I can force dehydrated to do sequential validations. Deploy 1 challenge, validate 1 challenge, clean, deploy 2 challenge, validate 2 challenge, clean. (sequential).
adam closed this issue 2025-12-29 01:27:05 +01:00
adam commented 2025-12-29 01:27:05 +01:00
Author
Owner
Copy Link

@lukas2511 commented on GitHub (Aug 19, 2021):

https://github.com/dehydrated-io/dehydrated/blob/master/docs/troubleshooting.md#dns-invalid-challenge-since-dehydrated-060--why-are-dns-challenges-deployed-first-and-verified-later

@lukas2511 commented on GitHub (Aug 19, 2021): https://github.com/dehydrated-io/dehydrated/blob/master/docs/troubleshooting.md#dns-invalid-challenge-since-dehydrated-060--why-are-dns-challenges-deployed-first-and-verified-later
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#544
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?