[GH-ISSUE #35] letsencrypt HTTP-01 challenge possible? #10

New issue

Closed

opened 2026-03-13 15:21:08 +03:00 by kerem · 3 comments

kerem commented

2026-03-13 15:21:08 +03:00

Owner

Originally created by @leonkyneur on GitHub (Feb 1, 2018).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/35

Just noticed my certificate cannot renew, I think it's only since LetsEncrypt dropped support for TLS-SNI.

01/02/2018 12:14:43 pmINFO[0029] http: TLS handshake error from 10.42.176.26:51538: acme/autocert: unable to authorize "xxxxxxx.net"; tried ["tls-sni-02" "tls-sni-01"]

is there any way I can continue to use autocert for the API but with HTTP-01 challenge?

Originally created by @leonkyneur on GitHub (Feb 1, 2018). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/35 Just noticed my certificate cannot renew, I think it's only since LetsEncrypt dropped support for TLS-SNI. `01/02/2018 12:14:43 pmINFO[0029] http: TLS handshake error from 10.42.176.26:51538: acme/autocert: unable to authorize "xxxxxxx.net"; tried ["tls-sni-02" "tls-sni-01"]` is there any way I can continue to use autocert for the API but with HTTP-01 challenge?

kerem closed this issue

2026-03-13 15:21:13 +03:00

kerem commented

2026-03-13 15:21:20 +03:00

Author

Owner

@joohoi commented on GitHub (Feb 1, 2018):

There is! I'm going to write a quick PR to address that. We need to make the autocert use HTTP-01 challenge instead. Sorry I didn't get around this earlier.

However, please note that this means that ACME-DNS needs to be able to bind to port 80 as well.

@joohoi commented on GitHub (Feb 1, 2018): There is! I'm going to write a quick PR to address that. We need to make the autocert use HTTP-01 challenge instead. Sorry I didn't get around this earlier. However, please note that this means that ACME-DNS needs to be able to bind to port 80 as well.

kerem commented

2026-03-13 15:21:25 +03:00

Author

Owner

@joohoi commented on GitHub (Feb 1, 2018):

Thanks for opening the issue!

This is now fixed in master branch, tag v0.3. Please note that you will need to add the new variable to your config.cfg as shown here.

I changed the Docker image builds to an automated process in Docker hub, so it will take a while for the images to get updated.

Sorry for the inconvenience this has caused, and about not getting around it earlier!

@joohoi commented on GitHub (Feb 1, 2018): Thanks for opening the issue! This is now fixed in `master` branch, tag `v0.3`. Please note that you will need to add the new variable to your `config.cfg` as shown [here](https://github.com/joohoi/acme-dns/blob/master/config.cfg#L39-L40). I changed the Docker image builds to an automated process in Docker hub, so it will take a while for the images to get updated. Sorry for the inconvenience this has caused, and about not getting around it earlier!

kerem commented

2026-03-13 15:21:30 +03:00

Author

Owner

@leonkyneur commented on GitHub (Feb 1, 2018):

Thanks for fixing that and also thanks for for acme-dns 😀

@leonkyneur commented on GitHub (Feb 1, 2018): Thanks for fixing that and also thanks for for acme-dns 😀

kerem referenced this issue

2026-03-13 15:33:03 +03:00

[GH-ISSUE #128] K8S: Create wildcard SSL using acmedns provider #49

kerem referenced this issue

2026-03-13 16:13:03 +03:00