Hi there,
I have recently relocated my HA to a temporary home whilst we complete renovations on our house. HA itself is running fine however I am unable to get DuckDNS working. The only real change to my environment is the ISP provided public IP address.
In some of my endeavours to solve this I have:
- Deleted my original DuckDNS token and recreated a new one.
- Uninstalled the DuckDNS add on and reinstalled it.
However I still can’t access my HA instance.
I can ping my DuckDNS Hostname from within my network, and if I click a hyperlink to it from within my network it attempts to connect but then errors with a
“Unable to connect to Home Assistant. Retrying in x seconds…”
The DuckDNS log file is a little perplexing as I dont really understand the issue, I only have one account at DuckDNS with a single subdomain:
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!
[07:03:11] WARNING: KO
[07:03:11] INFO: Renew certificate for domains: and aliases:
INFO: Using main config file /data/workdir/config
ERROR: domains.txt not found and --domain not given
[07:08:15] WARNING: KO
Note using the same router with exactly the same configuration as previously so port forwarding etc is identical. Any help or feedback would be appreciated. 