mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
Dehydrated does not work with step-ca and http-01 challenge #474
Reference in New Issue
Block a user
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?
Originally created by @sebageek on GitHub (Apr 18, 2020).
I cannot obtain certificates with dehydrated from current master, as it seems to fail to communicate to the CA that it is interested in a http-01 challenge. I'm testing with dehydrated from
dbb0ef1and step-caCA/0.14.3-rc.2.32bitbadger2. Originally I tried v0.6.5, which resulted in the same result as #689.In my tests dehydrated gets a challenge that is placed in the
acme-challenges/directory, but the CA never asks my webserver for it. The error message from the CA suggests that it is only trying to do dns-01 validation, not http-01 validation.Dehydrated config:
Dehydrated output:
I added a
echo " --- result: $result"in line 824 for getting the CAs error message.For reference, this is the ca log for an issue attempt:
I installed the step-ca following this tutorial by installing https://github.com/smallstep/certificates and https://github.com/smallstep/cli/ from the releases and then issuing the following commands:
The step-ca works fine with another ACME client like acme.sh, tested with
./acme.sh --server https://10.100.1.8:9443/acme/acme/directory --issue -d foo.dn --webroot ../dehydrated/webroot/ --force.@lukas2511 commented on GitHub (Jul 4, 2020):
It's weird that it tries to use dns dns-01 challenge, obviously that can never complete if it should be http-01... wondering if that is related to the json parsing issues... If this is still relevant would you mind testing the dehydrated version from here (https://github.com/dehydrated-io/dehydrated/tree/jsonsh) and see if it works now?
@danimo commented on GitHub (Sep 17, 2020):
@darix has validated that this works with current master after the switch to json.sh. I think this can be closed.
@lukas2511 commented on GitHub (Sep 17, 2020):
@danimo thx, closed.