Getting the error
Unable to load the panel source: /api/hassio/app/entrypoint.js when attempting to open Configurator, Hass.io, and Node-Red pages (appears to be any page managed by Ingress). I’m on Hassio on a RPi. Home Assistant v0.95.4. Any ideas how to fix this?
Background: We had a power outage the other night. When the power came back on, I had to ssh into the rpi and manually start
hassio homeassistant start. It came up fine, and Hass.io and Node Red worked fine. A few hours after that, Hass.io and Node Red and Configurator stopped working (can’t open them, my Node Red flows aren’t functioning) and I am unable to access their pages.
I’ve restarted Home Assistant
hassio homeassistant restart. No joy.
I’ve rebooted the RPi. No joy.
The HA log gives a similar error message:
Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connection refused].
The 172.30.32.2 IP is not on my network, but research leads me to believe its an internal IP address used by the Hassio docker system.
I’ve found a few similar threads on this forum and the reddit forum, but nothing conclusive. I’d like to avoid re-imaging my SD card if at all possible.
Edit: After the power outage I’m seeing many more warnings and errors that my thermostat and darksky and presence sensors are taking longer than 10 seconds to update (
update of [SensorName] is taking over 10 seconds). Don’t know if this is related or not.
SOLVED: For posterity: I hard unplugged the rpi from the wall. Waited a minute, plugged it back in. SSH’d in, started home assistant, and it all came up just fine. I’m working again, but I’m very very concerned. Don’t like having to hard reboot to solve a problem. I’m guessing that the power outage scrambled my containers somehow, and by hard rebooting I reset them to a good configuration. Not sure why restarting HASSIO and restarting the RPI didn’t do that, but…
2nd EDIT: A few weeks later my SD card completely died and I had to buy a new one and start from scratch. I believe the above issue was a symptom of my card failing. If you’re getting this as well and your configuration looks good, you may want to take some precautionary steps for an SD card about to die (backing up, get another SD card ready).