DuckDNS fails to create cert

Configuration
1

I’m trying to set up DuckDNS addon but after filling in the configuration and starting the addon I get this in the log:

 + Deploying challenge tokens...
OK + Responding to challenge for xxxxx.duckdns.org authorization...
 + Cleaning challenge tokens...
OK + Challenge validation has failed :(
ERROR: Challenge is invalid! (returned: invalid) (result: ["type"]	"dns-01"
["status"]	"invalid"
["error","type"]	"urn:ietf:params:acme:error:unauthorized"
["error","detail"]	"Incorrect TXT record \"\" found at _acme-challenge.xxxxx.duckdns.org"
["error","status"]	403
["error"]	{"type":"urn:ietf:params:acme:error:unauthorized","detail":"Incorrect TXT record \"\" found at _acme-challenge.xxxxx.duckdns.org","status":403}
["url"]	"https://acme-v02.api.letsencrypt.org/acme/chall-v3/272738501986/-dYCJA"
["token"]	"xxxxxxxxxxxxxxxxxxxxxxxxxx"
["validated"]	"2023-10-11T04:54:37Z")
2

Could be related : Duckdns is down

3

Problem for me started yesterday. And I still have the same problem now 14 hour later

4

Then tell us more which steps you have completed.

5

All I’ve done is install the addon and added this config:

domains:
  - xxxxx.duckdns.org
token: xxxxxxxxxxxxxxxxxxxxx
aliases: []
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300
6

Did you go to duckdns.org and set up your domain?

When you go there, does the ip address reported by your domain admin page match the ip address given to your router by your ISP?

7

Yes I have set up a domain at duckdns and the IP there matches my WAN IP. So I’m not behind CGNAT

1 Like
8

Have a read of this:

9

But where do I add the CNAME? I’m only usning duckdns
And I dont use any alias

10

More this point:

This only works when your provider supports an API for automated creation of DNS records

11

But this is a addon for duckdns and duckdns is the DNS-provider. I dont understnad what I’m supposed to do

12

Try setting your router to use 1.1.1.1 or 8.8.8.8 as the DNS server, instead of your ISP’s DNS server.

13

I’ve already tried different DNS-server. 1.1.1.1, 1.0.0.1 and 8.8.8.8
Does not solve the issue

14

In your router or in home assistant?

15

Changed in HAOS and in the router

16

:man_shrugging: I’m out of ideas then. Sorry.

17

Now during the night the addon has created certs. Without me changing anything
So the problem must have been at DuckDNS’s end

18

Yeah. There have been a few issues reported in the last couple of days. All their end.