1. Caddy version (caddy version
):
Windowx x64, 2.3.0
+module GitHub - caddy-dns/cloudflare: Caddy module: dns.providers.cloudflare (works)
+module GitHub - caddy-dns/lego-deprecated: (DEPRECATED) DNS modules so Caddy can solve the ACME DNS challenge with over 75 providers (I would like to use)
2. How I run Caddy:
I am using NSSM to run Caddy as a service on Windows 10 20H2 x64 (everything but my issue works like charm)
a. System environment:
see above
b. Command:
caddy.exe run --config C:\Services\Caddy2\Caddyfile --watch --environ
c. Service/unit/compose file:
none
d. My complete Caddyfile or JSON config:
https://mycoolsubdomain.v6.rocks:2096 {
log {
level INFO
output file logs/mycoolsubdomain.v6.rocks-access.log
format single_field common_log
}
tls {
dns lego_deprecated rfc2136
}
respond "It works."
}
I set the environment variables
RFC2136_NAMESERVER=ns1.dynv6.com
RFC2136_TSIG_KEY=tsig-123456.dynv6.com
RFC2136_TSIG_ALGORITHM=hmac-sha256
RFC2136_TSIG_SECRET=<my token>
3. The problem I’m having:
The ACME challange does time out / does not work.
4. Error messages and/or full log output:
Caddy prints this on the console:
{"level":"warn","ts":1612467943.5180006,"logger":"tls.issuance.acme.acme_client","msg":"HTTP request failed; retrying","url":"https://acme-staging-v02.api.letsencrypt.org/directory","error":"performing request: Get \"https://acme-staging-v02.api.letsencrypt.org/directory\": read tcp [b16b:00b5:9c0:3800:dc94:56e5:d625:4e56]:52537->[2606:4700:60:0:f41b:d4fe:4325:6026]:443: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen."}
{"level":"warn","ts":1612467946.519031,"logger":"tls.issuance.acme.acme_client","msg":"HTTP request failed; retrying","url":"https://acme-staging-v02.api.letsencrypt.org/directory","error":"performing request: Get \"https://acme-staging-v02.api.letsencrypt.org/directory\": read tcp [b16b:00b5:9c0:3800:dc94:56e5:d625:4e56]:52538->[2606:4700:60:0:f41b:d4fe:4325:6026]:443: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen."}
{"level":"warn","ts":1612467955.5882125,"logger":"tls.issuance.acme.acme_client","msg":"HTTP request failed; retrying","url":"https://acme-staging-v02.api.letsencrypt.org/directory","error":"performing request: Get \"https://acme-staging-v02.api.letsencrypt.org/directory\": read tcp [b16b:00b5:9c0:3800:dc94:56e5:d625:4e56]:52539->[2606:4700:60:0:f41b:d4fe:4325:6026]:443: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen."}
{"level":"error","ts":1612467955.5882125,"logger":"tls.obtain","msg":"will retry","error":"[mycoolsubdomain.v6.rocks] Obtain: [mycoolsubdomain.v6.rocks] creating new order: provisioning client: performing request: Get \"https://acme-staging-v02.api.letsencrypt.org/directory\": read tcp [b16b:00b5:9c0:3800:dc94:56e5:d625:4e56]:52539->[2606:4700:60:0:f41b:d4fe:4325:6026]:443: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":5,"retrying_in":600,"elapsed":710.8568515,"max_duration":2592000}
Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
(German, means) An existing connection was closed by the remote host.
5. What I already tried:
6. Links to relevant resources:
I took the idea that this should work somehow from here: dynv6 APIs
The module seems to follow this RFC2136 :: Let’s Encrypt client and ACME library written in Go.
I also asked for help here: h**ps://community.dynv6.com/t/caddy-and-rfc2136/1200
Last link has ** because I am not allowed to post this many links.
Thanks for you time reading this.