HOOK_CHAIN="no" ineffective anymore? #360

New Issue

adam · 2025-12-29T01:23:39+01:00

adam commented

2025-12-29 01:23:39 +01:00

Originally created by @v20z on GitHub (Jul 5, 2018).

Hello Gentlemen.

After upgrading from ver 0.4.0 to 0.6.2 I've faced out that HOOK_CHAIN="no" changed behaviour. In past it performed challenges deploy/validation in loop one by one:

HOOK: deploy_challenge for
 + Responding to challenge for 
HOOK: clean_challenge for
 + Challenge is valid!
HOOK: deploy_challenge 
...

But as I noticed in newer version it is simply performs at first either batch or one by one but consecutive all challenges deployment. Then at next stage performs all challenges validation. And finaly ether at once or one by one challenges removal.

My setup is dependent on the original behavior of the HOOK_CHAIN="no" option, i.e. deploy/validation sequence for each domain/cert.

Have I to correct it myself as it was? Or may I expect clarifications and some additional setting for original behavior?

Thank You.

P.S.
If my setup is stupid or incorrectly based on misunderstanding but it made in past as documented at https://github.com/lukas2511/dehydrated/blob/master/docs/hook_chain.md

Originally created by @v20z on GitHub (Jul 5, 2018). Hello Gentlemen. After upgrading from ver 0.4.0 to 0.6.2 I've faced out that HOOK_CHAIN="no" changed behaviour. In past it performed challenges deploy/validation in loop one by one: ``` HOOK: deploy_challenge for + Responding to challenge for HOOK: clean_challenge for + Challenge is valid! HOOK: deploy_challenge ... ``` But as I noticed in newer version it is simply performs at first either batch or one by one but consecutive all challenges deployment. Then at next stage performs all challenges validation. And finaly ether at once or one by one challenges removal. My setup is dependent on the original behavior of the HOOK_CHAIN="no" option, i.e. deploy/validation sequence for each domain/cert. Have I to correct it myself as it was? Or may I expect clarifications and some additional setting for original behavior? Thank You. P.S. If my setup is stupid or incorrectly based on misunderstanding but it made in past as documented at https://github.com/lukas2511/dehydrated/blob/master/docs/hook_chain.md

adam closed this issue

2025-12-29 01:23:39 +01:00

adam commented

2025-12-29 01:23:40 +01:00

@lukas2511 commented on GitHub (Jul 6, 2018):

Please have a look at https://github.com/lukas2511/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 (Jul 6, 2018): Please have a look at https://github.com/lukas2511/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.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#360