DuckDNS fails to create cert

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 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"
["error","status"]	403
["error"]	{"type":"urn:ietf:params:acme:error:unauthorized","detail":"Incorrect TXT record \"\" found at","status":403}
["url"]	""
["token"]	"xxxxxxxxxxxxxxxxxxxxxxxxxx"
["validated"]	"2023-10-11T04:54:37Z")

Could be related : Duckdns is down

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

Then tell us more which steps you have completed.

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

token: xxxxxxxxxxxxxxxxxxxxx
aliases: []
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300

Did you go to 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?

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

Have a read of this:

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

More this point:

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

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

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

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

In your router or in home assistant?

Changed in HAOS and in the router

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

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

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