I’m using the DuckDNS.org service to access my Home Assistant via a HTTPS connection using the LetsEncrypt certificates. For some reason I cannot make connection from outside my home. From internal network it all works fine. The certificate is not expired. I’ve done an upgrade of HA recently. Port forwarding on my router is still enabled and should work as normal. How to debug this? Suggestions?
I’ve seen several others post about issues with DuckDns in the past few days. I believe the DuckDNS service is no longer reliable due to outages Is Duck DNS down? Live status and problems past 24 hours
To check, confirm your the WAN IP on your router is the same IP as your DuckDNS hostname is resolving to.
Indeed, I’ve seen the DuckDNS challenges/issues as well, would be a pity if that platform is not reliable anymore, need to search for alternatives.
Yes, the WAN IP is the same, I’ve checked that indeed.
I’m using Unify as a router/system at home, cannot find anything in the log files about connections being refused (or accepted). So difficult to debug at the moment.
how are you using DuckDNS in HA as there are multiple approaches to this?
I had an issue over last day or two using the Add-on (issue in v1.23 I think), and update today to v1.24 has fixed my remote access over DuckDNS domain
If I do a nslookup of xxxx.duckdns.org I do get the correct IP address. but at the same time browsing to https://xxxx.duckdns.org doesn’t connect to my home assistant.
I would suggest you look at setting up Dynamic DNS on the router. This would actually be more efficient as the router will now when the WAN IP changes and update the provider as opposed to DuckDNS via the HA Integration or add-on which periodically polls to see if your IP has changed.
I would also recommend installing Nginx Proxy Manager to handle certificate renewal and proxying to your HA instance.
Good suggestion on the DynDNS in the router, that has been done.
Nginx has already been installed and renewing the certificate is not an issue, that is working. Also the browser is not complaining about an expired certificate. There is something else ongoing and I cannot figure it our why/what!
Don’t ask me why, I restarted LetsEncrypt, DuckDNS, Nginx all manually and now it is working again. Strange. Will keep monitoring if it happens again.