Since October 1st my connection with my HA machine using my duckdns-URL is really unstable, most of the times I get an error message (see examples below). In the last months I have seen this before but only for 1 or 2 hours, now it has been bugging me for almost an entire day. If I use my local IP I can still reach my machine.
Troubleshooting DuckDNS connection
I have taken the following steps to try and fix the DuckDNS remote connection.
checked if there is a name resolution for my DuckDNS subdomain with a remote nslookup via https://www.nslookup.io/ (there isnāt) ā thanks to @gzxto for the advice!
advice from @nickrout: Using the command dig +trace method you can determine issues and delays in the route from your client device (e.g. iPhone) to the IP address where you HA host machine is located (IP issued by your ISP).
after waiting a second (maybe seconds) the last block should show the IP address issued by your ISP. You can also review the delays along the route (see the last line of every block, it will show for example ā8.8.4.4#53(8.8.4.4) in 38 ms)
resetted router & modem and rebooted the HA host machine
checked if IP registered at DuckDNS and the IP provided by my ISP is still a match (it is)
Had similar frustrations and determined it was duckdns by trying to access my URL in a fresh incognito tab and it says {my-host}.duckdns.orgās server IP address could not be found.
Iāve never had problems before, but since yesterday (about 15 hours ago) iām no longer able to log in.
I suspected Duckdns to start with and this thread confirmes my suspicion.
Is this something that will resolve itself (aka duckdns servers getting back online)?
I am able to get in sometimes (about 1 in a 100 tries). When iām in I can acces everthing just fine, but only for a minute or so.
Same problem. Although my symptoms are a bit different:
Reloading the HA website takes a long time
The app on Android complains about the same. Once connectivity is achieved, it works pretty smooth
Google Home can no longer connect in a stable manner
I donāt distinguish between a local and external URL, because to my perception, once you have ssl enabled, HA will no longer expose unencrypted traffic to the internal network (source). Would be keen to understand how you achieved that, but thatās a different subject.
I am on a Docker system, running on a RPI4. All to the latest versions in my attempt to solve the connectivity issues. Running a Mikrotik router that takes care of the DuckDNS updating, because the router is where my public IP terminates.
OK, so it isnāt just me. Clearly related to duckdns, via browser connecting to local (or even public) IP (and ignoring the ssl certificate mismatch warning) just works all the time. Going via the duckdns url gives issues. Also noticed the issues with google assistant/google home, but that is logical since that needs the URL.
It is very odd, because it works so intermittently. It isn;t that it doesn;t work at all, once in a while it will actually be able to connect - very weird. Nothing appears in the duckdns or HA logs.
Oh well, I assume it will get resolved after the weekend ā¦
Iām having the same issue, at first i tought it was my Home Assistant installation having issues but i can connect trough the local IP just fine. Hoping for a fix from DuckDNS soon.
Same problem here, duckdns is not working correctly.
In the duckdns page i see the correct ip address but if i try to use my duckdns address
I cannot reach my home assistant instance nor my ipcam. With IP address it works.
Thanks all for replying! This makes me pretty confident the root cause of the issue is currently with the service provided by the DuckDNS website. I hope they resolve it soon.
Same here, happened about 2 weeks ago for me as well, pulling my hair out trying to get google assistant to work to find out its actually just duckdns and figured out when I left the house and not using my hairpin nat.
Same Issue here, most annoying google assistant is not workingā¦
Easy to check that itās duckdns, just do a remote nslookup e.g. here https://www.nslookup.io/
There is no name resolution anymoreā¦
Exact same issue here, from a working setup before with no changes. I assume theyāre just having some trouble currently. Thanks all for posting here to confirm the issue.