Failure to obtain certificate from issuer with duckdns

1. The problem I’m having:

So, I’ve been trying to use caddy to set up a reverse proxy for my Jellyfin server. I followed this tutorial on YT: Full Install of Caddy + DuckDNS + Jellyfin with in Depth Setup for Windows - YouTube

Whenever I run the command “caddy run --config Caddyfile”

Here is the caddy file

domainhere.duckdns.org {
    reverse_proxy 192.168.0.187:8096
    tls {
        dns duckdns accesstoken
    }
}

2. Error messages and/or full log output:

These same errors repeat over and over again

2023/03/25 17:32:32.542 ←[34mINFO←[0m   http.acme_client        trying to solve challenge       {"identifier": "domainhere.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme.zerossl.com/v2/DV90"}

2023/03/25 17:32:32.580 ←[31mERROR←[0m  http.acme_client        cleaning up solver      {"identifier": "domainhere.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.domainhere.duckdns.org\" (usually OK if presenting also failed)"}

2023/03/25 17:32:32.968 ←[31mERROR←[0m  tls.obtain      could not get certificate from issuer   {"identifier": "domainhere.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "[domainhere.duckdns.org] solving challenges: presenting for challenge: adding temporary record for zone \"duckdns.org.\": DuckDNS request failed, expected (OK) but got (KO), url: [https://www.duckdns.org/update?domains=domainhere.duckdns.org&token=accesstoken&txt=hwmbzZ7_503d3JqwBTkXpaE_ewphopVVDAWO7m1b_ys&verbose=true], body: KO (order=https://acme.zerossl.com/v2/DV90/order/2kjKHJhxfJDOILtE971VfA) (ca=https://acme.zerossl.com/v2/DV90)"}

2023/03/25 17:32:32.972 ←[31mERROR←[0m  tls.obtain      will retry      {"error": "[domainhere.duckdns.org] Obtain: [domainhere.duckdns.org] solving challenges: presenting for challenge: adding temporary record for zone \"duckdns.org.\": DuckDNS request failed, expected (OK) but got (KO), url: [https://www.duckdns.org/update?domains=domainhere.duckdns.org&token=accesstoken&txt=hwmbzZ7_503d3JqwBTkXpaE_ewphopVVDAWO7m1b_ys&verbose=true], body: KO (order=https://acme.zerossl.com/v2/DV90/order/2kjKHJhxfJDOILtE971VfA) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 3.2490082, "max_duration": 2592000}




3. Caddy version:

v2.6.4

4. How I installed and ran Caddy:

Following the tutorial above, I went to the caddy download page, added duckdns as one of the plugins I would like to use.

I then created a directory called C:\Tools\Caddy. I then renamed the custom exe name to simply caddy.exe. In this same directory I created the Caddyfile (contents listed above).

I then ran “caddy run --config Caddyfile” and got the errors listed in Number 2.

a. System environment:

Windows 10.

b. Command:

caddy run --config Caddyfile

c. Service/unit/compose file:

None

d. My complete Caddy config:

domainhere.duckdns.org {
    reverse_proxy 192.168.0.187:8096
    tls {
        dns duckdns accesstoken
    }
}

5. Links to relevant resources:

Full Install of Caddy + DuckDNS + Jellyfin with in Depth Setup for Windows - YouTube

Hmm, that’s odd. The DuckDNS spec doesn’t give much information about what could be the problem in this case: Duck DNS - spec

Are you sure your API token is correct? It should look like a UUID, i.e. letters a-f and 0-9, with - dashes in between. Are you sure your DuckDNS account has that subdomain already registered?

1 Like

Hmmm… I’m not sure what happened. I guess there must have been a typo. This time to double check, I copied and pasted and I did get a certificate, but I swear that this is what I did before.

Will come back if there’s more problems.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.