My home assistant HOAS works perfectly well with local control. Automations work, I can log in locally, etc.
I have, long ago, set up a duckdns remote access. It worked fine, but stopped allowing me to connect a few days ago. The integration is reporting that everything is fine. Nothing changed in my setup or internet provider. It just won’t let me connect, be it via the app or a web page. It’s also indépendant from the device I use.
While the app can’t connect, it still sends notifications related to automations.
I’m at my wits end, looking for advice from anyone.
Extra info : this morning, physically removed from my home, I entered the duckdns web address directly in Chrome . I saw “Connecting to Home Assistant” which tells me the problem doesn’t come from duckdns. However, it won’t connect, showing the “retry in x seconds” message.
I’m not sure, but there might be a correlation between the 2025.10.3 update which was released recently. I’m not sure there’s a correlation.
The problem began before the AWS outage unless it was reported after the downtime began).
Log in to the DuckDNS admin page (where you set up your domain name) confirm the IP address it has associated with your domain is the same as the public IP address of your router.
If not your ISP may have enabled CGNAT, most will allow you to opt out of this.
Also check the DuckDNS add-on logs, make sure it is not failing to renew the LetsEncrypt security certificate.
Thanks for commenting. I’ll look into that from home. I can confirm that the DuckDNS integration’s log is returning no errors, that’s a start (I’ll look at the Let’s Encrypt).
Remotely, I can see the Home Assistant welcome page, where it’s telling me it’s trying to connect, so duckDNS apears to be working because it’s leading me to the right server. I just can’t connect to it. It’s telling me “unable to connect to Home Assistant. Retrying in x seconds”
I’ll try with the browser. I uninstalled and reinstalled the app completely. I’ll still try to clear the cache to see if some remaining files were there, but given that both the app and several browsers act up at the same time, I fear it’s my install.
Are there reported issues with 2025.10.3 ? I’m not sure about the correlation, but it might be the cause. If so, I guess I should report it but I don’t know where to formally do that for a Core update.