Home Assistant Suddenly Stopped working

This is vague I know but HA was working fine for months and suddenly I couldn’t access it remotely via https and a duckdns cert. It was about time I updated so did so and now port 8123 is refused from inside my local network. It seems http is not working but HA itself is up and running:

pi@hassbian:/home/homeassistant/.homeassistant $ hastatus
[email protected] - Home Assistant for homeassistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabl
Active: active (running) since Wed 2018-10-17 21:50:38 UTC; 3min 8s ago
Main PID: 5058 (hass)
CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
└─5058 /srv/homeassistant/bin/python3 /srv/homeassistant/bin/hass

Pi is listening on port 8123:

pi@hassbian:/home/homeassistant/.homeassistant $ netstat -na |grep 8123
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN

But a connection to the port is refused:

➜ ~ telnet 192.168.100.170 8123
Trying 192.168.100.170…
telnet: connect to address 192.168.100.170: Connection refused
telnet: Unable to connect to remote host

Any ideas? This is a hassbian setup.

The only message I have in the logs is:

pi@hassbian:/home/homeassistant/.homeassistant $ cat home-assistant.log
2018-10-17 22:04:08 WARNING (MainThread) [homeassistant.components.http] legacy_api_password support has been enabled. If you don’t require it, remove the ‘api_password’ from your http config.

I updated from 0.76(pre new authentication) to .80(new authentication) and had issues accessing because authentication issues. I use docker so I actually created a defaulted container then copying the new authentication parts over to HA(basically started from scratch)

There are some authentication files in new HA versions that did not exist in old and will cause you issues. I didn’t need to redo my config, just copied over to new install folder but after about an hour troubleshooting this the 15min this took was worth it

1 Like

Thanks but I don’t use docker, this is hassbian.

The initial tcp connection is getting immediately refused. I can connect to port 8123 from the localhost but not remotely. There is no firewall on the raspberry pi and I can see python listening to the port.

Any other ideas how to troubleshoot this? This is nothing useful in the logs. The log I find strange is the the discovery of itself as an unknown service.

pi@hassbian:~ $ sudo netstat -tnlp | grep :8123
tcp        0      0 0.0.0.0:8123            0.0.0.0:*               LISTEN      16333/python3

Well, turns out I was trying to access the wrong IP! Doh. The original problem was an expired ssl cert.