You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we use dehydrated_challengetype == 'http-01' but we define a specific domain with dns_01 the dns-01-lexicon.yml is not included and dehydrated can't issue the certificate.
You can set dehydrated_use_lexicon: yes, but that would cause the role to request all certificates via dns-01, even if the per-certificate-config says http-01. That the dns-01-lexicon is not included is indeed not working as intended.
I think the best would be to let dehydrated_use_lexicon depend on dehydrated_challengetype (yes if dns-01, else no)
For the other part, the hook script would need to be converted to a template and only call lexicon, if the challengetype is dns-01 (while considering per cert configs).
I have some Ideas here I'll try out on the weekend or early next week.
Include dns-01-lexicon.yml only depending on dehydrated_use_lexicon.
default vaule for dehydrated_use_lexicon is changed to depend on
dehydrated_challengetype (true if dns-01).
If we use dehydrated_challengetype == 'http-01' but we define a specific domain with dns_01 the dns-01-lexicon.yml is not included and dehydrated can't issue the certificate.
Exemple :
2 solutions :
What do you think ?
Yoann
The text was updated successfully, but these errors were encountered: