Can’t log in remotely with duckdns anymore

I’ve been using duckdns to access my HA for about a year now, suddenly something happened and I am no longer able to connect.

I had followed someone’s instructions on YouTube to set up the remote access, it was long enough ago that I don’t remember exactly what steps I used to set up.

I’m not sure if there was something I did, or if something just stopped working. Over the weekend, my wifi went down, and I had to reboot my Home Assistant yellow using the blue shut down button, and when it restarted at least one of my integrations wasn’t working. I restored my latest backup and sometime during this period the remote access stopped working (it had been working earlier in the day, and the backup was from 2 days before it stopped working)

I don’t know what to do to figure out what isn’t working. I know there are multiple ways to enable remote access, so I’m not able to give enough information to help me, but does anyone have any suggestions on anything I can check?

More than likely, the internal IP you used on your router for port forwarding to HA was changed when you restarted HA

Log into your router. Go to the port forwarding setup, make sure the internal IP address for you HA Yellow is what is configured in your router.

1 Like

Thanks for the response. I checked, and the port forwarding looks correct. The address is the address of my HA Yellow.

While checking that, I noticed I have a raspberry pi zero that was running as a web server that had become disconnected, I believe it was part of the process (running nginx or hosting certificates or something; this was set up a while ago, so I don’t remember exactly what was part of this setup). I plugged it back in, but i’m still not able to connect. I will check back later to see if it will allow me to connect.

I don’t think that the port forwarding was the issue, but it has led me to something i believe may be the issue. I may have to go through the entire setup process again (If I can find which video i followed) and take better notes to document what is needed to keep the system running.

Thanks again.

Just to follow up, I did find the issue finally.

The NGINX Home Assistsnt SSL Proxy add-on had apparently not started after the backup restore (and subsequent restarts) even though the ‘Start on Boot’ and ‘Watchdog’ options had been set prior.

I noticed a few other issues after the restore, a couple automations that were triggered by one of my Chromecast Audio needed the entity reset, the name has been changed.