DuckDNS domain timeing out

1

I moved to a new Pi and couldn’t get the old domain working so created a new one, the DuckDNS log looks OK:

# INFO: Using main config file /data/workdir/config
Processing XXXX.duckdns.org
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for XXXX.duckdns.org
 + 1 pending challenge(s)
 + Deploying challenge tokens...
OK + Responding to challenge for XXXX.duckdns.org authorization...
 + Challenge is valid!
 + Cleaning challenge tokens...
OK + Requesting certificate...
Warning: Will read cert request from stdin since no -in option is given
 + Checking certificate...
 + Done!
 + Creating fullchain.pem...
 + Done!

And no errors in NGINX Home Assistant SSL proxy. I have Restarted.

Also, I can only get local IP working in Chrome and Edge, for firefox, I just get HA logo and eventually, it times out.

When I go to the domain it times out. It worked OK before. Any ideas?

2

Hi @funkytwig,

Try switching to another DNS Provider.

Recently I’ve seen issues with DuckDNS

3

OK but is stopped working when I moved to new Pi. I do have a dydns on my tp link router. Looks like the duckdns add-on only works with duckdns (not surprising).

How do I setup so let’s encrypt works with tlinkdns.com.

OK, tried to get it working but not quite there. Will post seperatly.