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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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