Unable to load the panel source: /api/hassio/app/entrypoint.js

Check here, looks like the issue has been ID’d. If you have a way to modify your secrets.yaml via access to your host, you should be able to fix it.

https://github.com/home-assistant/hassio/issues/1292#issuecomment-531550991

Same on 0.97.2. But without any power outtake or anything. System was just running and running

1 Like

I reinstalled yesterday my hass.io system completly new (other reasons), migrated my config the the new system and also got the error. I also have the latest version installed. I did not see any new version or fixes on github. Is there maybe an other solution for that problem?

I reflashed my pi yesterday and think I have everything set up again now, not getting the errors any more.

1 Like

Just go to user menu on the left and be sure advanced mode is on. This was the solution for me after a fresh install of the Hass.io package on synology DSM.

1 Like

Hello, this error occurs when installed with the hasssio package on synology.

Current issues

The installation process does not play nice with the Synology Firewall (or Adguard/PiHole) and could show errors like this below. Make sure to disable the Firewall before starting the installation (thanks @ohminy for pointing this out).
Copy to clipboard
[hassio.utils.dt] Can’t fetch freegeoip data: Cannot connect to host http://ip-api.com/ ssl:None [Try again]
[hassio.updater] Can’t fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant

Sometimes there are communication issues between Home Assistant and hass.io 16, with this error message : Unable to load the panel source: /api/hassio/app/entrypoint.js. Restarting the package seems to fix this or follow the fix below.
Fix: (I don’t think it is possible to make this automatic atm)
Stop the package (from Package Center).
Go to the Docker package page and find the hassio_supervisor Container (under the Container tab).
Stop the hassio_supervisor (if it still is running), right click and choose Action -> Clear.
Make sure that the homeassistant container is stopped.
Start the Hass.io 50 package from Package Center.
Wait a minute and make sure that the homeassistant container is started (in the Docker package) or start it manually.

source: Hass.io on Synology DSM (native package)

1 Like

Did you manage to get it to work?

Where do you find that panel? Could you share a screen shot?

image

1 Like

I just did update to 206 and have the same issue. I have hassio installed on docker.

Give it a few minutes, that’s because it can’t load the supervisor page that’s been updated. It should come back up

Same issue here after update to 106.5.
hassio installed on docker + nodered + hacs

“on docker” :roll_eyes:

You didn’t choose to install on docker or not. You chose a different Operating System.

Those running on generic linux installs (not “on docker” installs) need to run through the install steps again.
https://github.com/home-assistant/supervisor/issues/1556#issuecomment-594079796

2 Likes

Just encountered this issue, installed 106.5 a few days ago and it was fine till tonight…

Running hassio, how can I fix it?

Same here… installed 106.5 a few days ago and yesterday the supervisor panel is not working.

Also running on hassio

1 Like

Had similar issues, fixed with steps posted on: https://github.com/home-assistant/supervisor/issues/1556

sudo -i docker pull homeassistant/amd64-hassio-supervisor:latest
sudo docker tag homeassistant/amd64-hassio-supervisor:latest homeassistant/amd64-hassio-supervisor:latest
1 Like

Those of us on Hassio can’t run sudo commands.
-bash: sudo: command not found

What now for us poor bastards on docker?

Can’t load supervisor, esphome, configurator…

I believe this is the related error:

2020-03-10 09:42:38 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-03-10 09:42:38 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version: 

Edit:
Just chatted with cogneato on discord and solved the problem
Run ha su repair through ssh.
First time it didn’t run, power cycled the Pi and ran it again and now it’s repaired and working.
Thanks @cogneato!

2 Likes

Hey! Same error for me , not using docker.

I received the error message:
Post http://supervisor/supervisor/repair: dial tcp 172.30.32.2:80: connect: no r oute to host

When trying to do the command above through SSH

Edit: Just rebooted the PI and now I cant even SSH. Says connection refused.

Docker is there no matter what. You can’t have the Supervisor without docker. The Supervisor is a docker container.

You either install the image on an SD which comes with docker ready to go, or you install it on some other OS and install docker yourself. The only choice people are making is the OS. People who say “i installed it on Docker” don’t know what actually makes their system different than the version they would flash to an SD card.

That said, you can connect directly to the pi using a keyboard and monitor and use “root” to enter the custom cli, and from there you can enter “login” to continue to the host os console.

2 Likes

I know this issue was closed on January 20th as ‘not a Supervisor issue’. The Supervisor can not be accessed when this happens. This is a systems issue and needs a systems solution.

Mine system is the pre-built HassOS image on and RPi 4. I don’t seem to get anything on the video ports, so the keyboard and monitor solution is not possible. SSH connections are refused.

The only solution seems to be to pull the plug and reboot the Pi.

I’ve only been using HA since last July, and I’ve had to do this a few times. About half the time, the system never comes back on line and I have to start over from scratch.
I’m tired of having to reload the system.
And only once has any of the restore from backup work at all, so I had to re-create my configuration.yaml and my node-red flows.
I have had to completely re-install the entire every couple of months.

This needs a systems solution; even just a way to cleanly restart the RPi.

Is GPIO shutdown enabled on HassOS to enable a hardware shutdown button?

I there ANY other way to recover?

Thanks,
-Mike