Unable to access via DuckDNS URL for the last week

Hello,

My DuckDNS URL to my home assistant instance stopped working about a week ago despite not changing anything that I can think of. It’s been working mostly fine for almost 9 months prior. When I go to the URL, I just the “Unable to connect to HomeAssistant. Retrying in xx seconds” page. Can’t access on web or mobile app via DuckDNS address, but I can still access via local IP address. I can still ping the DuckDNS address and it responds. This has happened before, but never lasted this long and has always resolved itself. I have tried the following steps to fix but nothing has worked:

  • Stop and restart DuckDNS Add-On
  • Uninstall and reinstall DuckDNS Add-On
  • Verify public IP address has not changed
  • Verify port forwarding in router still configured (
  • Remove and recreate domain in DuckDNS
  • Restore a known working HA backup

DuckDNS add-on logs show the following (sanitized)

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[11:00:48] INFO: OK
{my public IP address here}
NOCHANGE
[11:00:50] INFO: Renew certificate for domains: neeshdfeesh.duckdns.org and aliases: 
# INFO: Using main config file /data/workdir/config
Processing neeshdfeesh.duckdns.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jul 23 13:52:26 2023 GMT (Longer than 30 days). Skipping renew!
[11:05:55] INFO: OK

DuckDNS add-on config (sanitized):

domains:
  - neeshdfeesh.duckdns.org
token: {my-token-here}
aliases: []
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300

config.yaml:

#SSL Keys HTTPS access via DuckDNS
http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: true
  login_attempts_threshold: 10

Not sure what else to do at this point, any help would be appreciated.

Ok, of course, in the 3 minutes since I posted this, it started working again. All I did was go in to my router port forwarding rules, click edit, and then click save. Maybe rebooting the router to reload the rules would have also worked. No idea what happened or if that even did anything but it works now. YMMV.

2 Likes

I had the very same problem, and the very same solution worked for me too.
The issue was caused by an outage, after which my router seems not to have considered port forwarding rules.
Many thanks