Hi all, I’m sure anybody who uses duckdns for home assistant hit this error at some point. This frequently happens during system updates among other things.
Of course the duckdns addon is a truly awesome addon that actually handles everything from the point of installation but sometimes, we may have to intervene when the automation failed.
I was puzzled at first, and wasted hours trying to solved the issue. It turned out that the system updates successfully, but the duckdns addon wasn’t running or the cron check did not detect any ip change when it actually did.
I can ssh in and see the logs, and it seems the service has started successfully but I can’t still login thru xxxx.duckdns.org. I have set up the router to forward port 443>hassio.local:8123. At this point, I can access the lovelace interface using hassio.local:8123.
So I run a quick check to see what my public ip was at www.whatismyip.com and then ran a quick nslookup of xxxx.duckdns.org. As expected, the ip dont match. The xxx.duckdns.org was pointing to another IP Address, which was actually my previous public ip address.
So what to do next is to trigger duckdns to update our public ip. It is done by simply calling a url, and supplying the token key and the new ip address which is outlined here.
Once it is done, you can browse to your duckdns domain~!
He has always been interested in computing. He is very passionate when it comes to technology oriented knowledge. He knows that the more that one knows, the more that one needs to learn. Experienced in content management and forms processing, he was a FileNet and Datacap Specialist. He is also a part time gamer and streams sometime.