Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only acme challenge type of http-01 is supported, config examples reference both sni and dns #292

Open
TomVnz opened this issue Jul 31, 2020 · 2 comments
Assignees
Milestone

Comments

@TomVnz
Copy link

TomVnz commented Jul 31, 2020

http://gobetween.io/documentation.html#Protocols

[acme] # (optional)
challenge = "http" # (optional) http | sni | dns

The info here suggest this can be done, just now sure how - e.g. with cloudflare or another DNS provider. How can I set access token to enable DNS acme verification?

Any help appreciated, thanks!

@nickdoikov nickdoikov assigned nickdoikov and illarion and unassigned illarion and nickdoikov Jul 31, 2020
@nickdoikov
Copy link
Collaborator

I'm not sure that it is possible, exernal dns providers that managing zones works via different API's some of them not providing API at all, so ther's no unified way to do this .

@TomVnz
Copy link
Author

TomVnz commented Jul 31, 2020

I've had some more time to look through the source - src/service/acme.go - and it looks like only http-01 is supported, but as the challenge value within the config file isn't validated, no sensible log information is outputted to say so.

Then looking further, seems the package you use - autocert - doesn't actually support DNS-01 verification see issue:- 23198. So you'd have to switch gobetween to something that does., e.g. one of acmez / lego with certmagic

@TomVnz TomVnz changed the title Lack of documentation to set acme challenge to DNS, and configure providers Only acme challenge type of http-01 is supported, config examples reference both sni and dns Jul 31, 2020
@illarion illarion added this to the 0.9.0 milestone Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants