[GH-ISSUE #315] Certificate maintenance routine not working with v1.0 release #170

New issue

Open

opened 2026-03-13 16:02:13 +03:00 by kerem · 0 comments

kerem commented

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

Owner

Originally created by @p3l1 on GitHub (Sep 4, 2022).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/315

In the latest version of the Docker Image v1.0 the automatical aquiring of a Let's Encrypt certificate is not working. There is no error thrown or any hint on why this is happening.

I used the same configuration with the v0.8 release, where everything is working.

[general]
listen = "0.0.0.0:53"
protocol = "both4"
domain = "dns.example.org"
nsname = "dns.example.org"
nsadmin = "dns.example.org"
records = [
    "dns.example.org. A 0.0.0.0",
    "dns.example.org. NS dns.example.org",
]

debug = true

[database]
# Database engine to use, sqlite3 or postgres
engine = "postgres"
connection = "postgres://acme:password@database/acme?sslmode=disable"

[api]
ip = "0.0.0.0"
disable_registration = false
port = "443"
# possible values: "letsencrypt", "letsencryptstaging", "cert", "none"
tls = "letsencrypt"
# only used if tls = "letsencrypt"
acme_cache_dir = "api-certs"
notification_email = "dns@example.org"
corsorigins = [
    "*"
]
use_header = false
header_name = "X-Forwarded-For"

[logconfig]
loglevel = "debug"
logtype = "stdout"
logformat = "json"

Log Output v0.8 directly after starting with this configuration:

acme-dns    | time="2022-09-04T22:13:33Z" level=info msg="2022/09/04 22:13:33 [INFO][cache:0xc000124550] Started certificate maintenance routine"

For v1.0 there is no entry regarding the certificate maintenance routine. When trying to access the API via HTTPS the following error appears:

acme-dns    | time="2022-09-04T22:29:02Z" level=info msg="http: TLS handshake error from 10.8.0.3:53232: no certificate available for 'dns.example.org'"

Any idea whats happening?

Originally created by @p3l1 on GitHub (Sep 4, 2022). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/315 In the latest version of the Docker Image `v1.0` the automatical aquiring of a Let's Encrypt certificate is not working. There is no error thrown or any hint on why this is happening. I used the same configuration with the `v0.8` release, where everything is working. ``` [general] listen = "0.0.0.0:53" protocol = "both4" domain = "dns.example.org" nsname = "dns.example.org" nsadmin = "dns.example.org" records = [ "dns.example.org. A 0.0.0.0", "dns.example.org. NS dns.example.org", ] debug = true [database] # Database engine to use, sqlite3 or postgres engine = "postgres" connection = "postgres://acme:password@database/acme?sslmode=disable" [api] ip = "0.0.0.0" disable_registration = false port = "443" # possible values: "letsencrypt", "letsencryptstaging", "cert", "none" tls = "letsencrypt" # only used if tls = "letsencrypt" acme_cache_dir = "api-certs" notification_email = "dns@example.org" corsorigins = [ "*" ] use_header = false header_name = "X-Forwarded-For" [logconfig] loglevel = "debug" logtype = "stdout" logformat = "json" ``` Log Output `v0.8` directly after starting with this configuration: ``` acme-dns | time="2022-09-04T22:13:33Z" level=info msg="2022/09/04 22:13:33 [INFO][cache:0xc000124550] Started certificate maintenance routine" ``` For `v1.0` there is no entry regarding the certificate maintenance routine. When trying to access the API via HTTPS the following error appears: ``` acme-dns | time="2022-09-04T22:29:02Z" level=info msg="http: TLS handshake error from 10.8.0.3:53232: no certificate available for 'dns.example.org'" ``` Any idea whats happening?