starred/acme-dns

Fork 0

mirror of https://github.com/acme-dns/acme-dns.git synced 2026-04-27 04:45:48 +03:00

[GH-ISSUE #186] tls = "letsencrypt" client still use ACMEv1? #79

New issue

Closed

opened 2026-03-13 15:42:16 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @NiasSt90 on GitHub (Oct 17, 2019).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/186

time="2019-10-17T07:29:13Z" level=info msg="http: TLS handshake error from $IP: 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details."

the time of ACMEv1 is over...

Originally created by @NiasSt90 on GitHub (Oct 17, 2019). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/186 > time="2019-10-17T07:29:13Z" level=info msg="http: TLS handshake error from $IP: 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details." the time of ACMEv1 is over...

kerem closed this issue

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

kerem commented

2026-03-13 15:42:27 +03:00

Author

Owner

@joohoi commented on GitHub (Oct 17, 2019):

~~Which version of acme-dns are you using at the moment?~~

edit: this is irrelevant

@joohoi commented on GitHub (Oct 17, 2019): ~~Which version of `acme-dns` are you using at the moment?~~ edit: this is irrelevant

kerem commented

2026-03-13 15:42:32 +03:00

Author

Owner

@joohoi commented on GitHub (Oct 17, 2019):

Ok, so this is related to the Golang autocert package. The ACMEv2 was added as default just a few days ago.

I'll do a new release of acme-dns shortly.

@joohoi commented on GitHub (Oct 17, 2019): Ok, so this is related to the Golang autocert package. The ACMEv2 was added as default just a few days ago. I'll do a new release of `acme-dns` shortly.

kerem commented

2026-03-13 15:42:37 +03:00

Author

Owner

@NiasSt90 commented on GitHub (Oct 18, 2019):

ok, thx.
I've struggled into huge problems because of this, because it looks like the acme-dns REST api can't be access thru http-only. It always redirects to their own https endpoint (the documentation doesn't mentioned this) and therefore a ssl-cert is always needed to access the acme-dns rest api.

@NiasSt90 commented on GitHub (Oct 18, 2019): ok, thx. I've struggled into huge problems because of this, because it looks like the acme-dns REST api can't be access thru http-only. It always redirects to their own https endpoint (the documentation doesn't mentioned this) and therefore a ssl-cert is always needed to access the acme-dns rest api.

kerem commented

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

Author

Owner

@joohoi commented on GitHub (Oct 18, 2019):

On the upcoming weekend I'm planning to finish work towards migrating from autocert to certmagic, a few DNS RFC fixes and moving to automated challenge responses using DNS validation. This will fix a wide array of issues along with this one.

@joohoi commented on GitHub (Oct 18, 2019): On the upcoming weekend I'm planning to finish work towards migrating from `autocert` to [certmagic](https://github.com/mholt/certmagic), a few DNS RFC fixes and moving to automated challenge responses using DNS validation. This will fix a wide array of issues along with this one.

kerem commented

2026-03-13 15:42:47 +03:00

Author

Owner

@joohoi commented on GitHub (Oct 18, 2019):

I've struggled into huge problems because of this, because it looks like the acme-dns REST api can't be access thru http-only. It always redirects to their own https endpoint (the documentation doesn't mentioned this) and therefore a ssl-cert is always needed to access the acme-dns rest api.

Acme-dns REST api can be accessed through HTTP, if you set tls = "none" in the config.cfg

@joohoi commented on GitHub (Oct 18, 2019): > I've struggled into huge problems because of this, because it looks like the acme-dns REST api can't be access thru http-only. It always redirects to their own https endpoint (the documentation doesn't mentioned this) and therefore a ssl-cert is always needed to access the acme-dns rest api. Acme-dns REST api can be accessed through HTTP, if you set `tls = "none"` in the `config.cfg`

kerem commented

2026-03-13 15:42:52 +03:00

Author

Owner

@joohoi commented on GitHub (Oct 20, 2019):

This was implemented in #190 and is included in v0.8 just released!

@joohoi commented on GitHub (Oct 20, 2019): This was implemented in #190 and is included in v0.8 just released!

kerem referenced this issue

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

[PR #81] [MERGED] Make ACME cache directory location configurable #281