I’m having an issue where Home Assistant becomes inaccessible after an uncertain period – both externally and locally. I followed this guide to expose HA externally using FritzBox’s MyFritz DDNS.
After some time, I can no longer access HA externally and just get an “Unable to connect” browser error.
When trying to connect locally via homeassistant.local:8123, I get the same message. However, if I try accessing via the server’s IP:8123, I only see the HA logo and nothing else loads.
When attempting SSH access, I get the following error:
Thanks for the suggestion, but that’s not the issue. When I unplug the Pi and plug it back in, I can log in normally, and everything works as it should. I also checked the File Editor for banned IP addresses, but there aren’t any—which makes sense because I’m able to log in from every account and device I’ve tried.
That would make sense—I’m not very experienced with network traffic and troubleshooting. Do you have any suggestions on how I could start figuring this out?
Another odd behavior: While the Pi is unreachable, my Zigbee devices also seem to stop communicating with it—at least that’s my assumption. When I reboot the Pi, I can see the Zigbee devices updated their states normally, but they stoped responding at the exact same time HA became inaccessible. After that, they flatline completely.
This makes me think the issue might be deeper than just network routing, because Zigbee should continue working locally even if the router is disconnected, right? It almost seems like the Pi is freezing or crashing entirely, rather than just losing network connectivity.