request_failure and invalid_challenge not executed when HOOK_CHAIN=yes #263

Closed
opened 2025-12-29 01:20:33 +01:00 by adam · 0 comments
Owner

Originally created by @jmptbl on GitHub (Nov 16, 2017).

Today I was struggling to setup dns-01 challenges with HOOK_CHAIN=yes. I had a DNS setup problem which would have caused invalid_challenge to run with a useful explanation, but with HOOK_CHAIN=yes it doesn't run. I noticed the same for request_failure.

Having HOOK_CHAIN=yes is optimal for dns-01, since it allows all the challenges for a cert to be bundled into one DNS update.

Culprit lines:

3d97799d6a/dehydrated (L428)
3d97799d6a/dehydrated (L623)

Originally created by @jmptbl on GitHub (Nov 16, 2017). Today I was struggling to setup dns-01 challenges with HOOK_CHAIN=yes. I had a DNS setup problem which would have caused invalid_challenge to run with a useful explanation, but with HOOK_CHAIN=yes it doesn't run. I noticed the same for request_failure. Having HOOK_CHAIN=yes is optimal for dns-01, since it allows all the challenges for a cert to be bundled into one DNS update. Culprit lines: https://github.com/lukas2511/dehydrated/blob/3d97799d6a269a727fb041f60e0b587c273fbe95/dehydrated#L428 https://github.com/lukas2511/dehydrated/blob/3d97799d6a269a727fb041f60e0b587c273fbe95/dehydrated#L623
adam added the bug label 2025-12-29 01:20:33 +01:00
adam closed this issue 2025-12-29 01:20:34 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#263