supervisor icon indicating copy to clipboard operation
supervisor copied to clipboard

Cannot access supervisor "unable to load panel source: /api/hassio/app/entrypoint.js"

Open Falsen opened this issue 4 years ago • 88 comments

Home Assistant release with the issue: 0.106.5

Operating environment (HassOS/Generic): Raspberry PI, installed with .iso

Supervisor logs:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing... 
[15:22:28] INFO: Update udev informations
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
20-03-08 15:22:56 INFO (MainThread) [__main__] Initialize Supervisor setup
20-03-08 15:22:57 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/armv7-hassio-supervisor with version 209
20-03-08 15:22:57 INFO (MainThread) [__main__] Setup Supervisor
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: de.pengutronix.rauc - /
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager
20-03-08 15:22:58 INFO (MainThread) [supervisor.host.info] Update local host information
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-03-08 15:22:58 INFO (MainThread) [supervisor.host.services] Update service information
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-03-08 15:22:58 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-03-08 15:22:58 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-03-08 15:22:58 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
20-03-08 15:22:58 INFO (MainThread) [supervisor.host.services] Reload local service hassos-apparmor.service
20-03-08 15:22:58 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-03-08 15:22:58 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-dns with version 1
20-03-08 15:22:58 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-audio with version 8
20-03-08 15:22:58 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-08 15:22:58 INFO (MainThread) [supervisor.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-03-08 15:22:59 INFO (MainThread) [supervisor.audio] Start Audio plugin
20-03-08 15:22:59 INFO (SyncWorker_5) [supervisor.docker.interface] Clean hassio_dns application
20-03-08 15:22:59 INFO (SyncWorker_4) [supervisor.docker.interface] Clean hassio_audio application
20-03-08 15:23:03 INFO (SyncWorker_5) [supervisor.docker.dns] Start DNS homeassistant/armv7-hassio-dns with version 1 - 172.30.32.3
20-03-08 15:23:04 INFO (SyncWorker_4) [supervisor.docker.audio] Start Audio homeassistant/armv7-hassio-audio with version 8 - 172.30.32.4
20-03-08 15:23:04 INFO (SyncWorker_9) [supervisor.docker.interface] Attach to homeassistant/raspberrypi2-homeassistant with version 0.106.5
20-03-08 15:23:04 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /
20-03-08 15:23:04 INFO (MainThread) [supervisor.hassos] Detect HassOS 3.12 / BootSlot B
20-03-08 15:23:05 INFO (SyncWorker_10) [supervisor.docker.hassos_cli] Found HassOS CLI homeassistant/armv7-hassio-cli with version 21
20-03-08 15:23:07 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/core repository
20-03-08 15:23:07 INFO (MainThread) [supervisor.store] Load add-ons from store: 20 all - 20 new - 0 remove
20-03-08 15:23:07 INFO (MainThread) [supervisor.addons] Found 3 installed add-ons
20-03-08 15:23:07 INFO (SyncWorker_8) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-configurator with version 4.7
20-03-08 15:23:07 INFO (SyncWorker_3) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-ssh with version 7.1
20-03-08 15:23:07 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-letsencrypt with version 4.7
20-03-08 15:23:08 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-03-08 15:23:12 INFO (MainThread) [supervisor.snapshots] Found 3 snapshot files
20-03-08 15:23:12 INFO (MainThread) [supervisor.discovery] Load 0 messages
20-03-08 15:23:12 INFO (MainThread) [supervisor.ingress] Load 3 ingress session
20-03-08 15:23:12 INFO (MainThread) [supervisor.secrets] Load Home Assistant secrets: 1
20-03-08 15:23:12 INFO (MainThread) [__main__] Run Supervisor
20-03-08 15:23:12 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-03-08 15:23:12 INFO (MainThread) [supervisor.utils.gdbus] Call de.pengutronix.rauc.Installer.Mark on /
20-03-08 15:23:12 INFO (MainThread) [supervisor.hassos] Rauc: B - marked slot kernel.1 as good
20-03-08 15:23:12 INFO (MainThread) [supervisor.addons] Phase 'initialize' start 0 add-ons
20-03-08 15:23:12 INFO (MainThread) [supervisor.addons] Phase 'system' start 0 add-ons
20-03-08 15:23:12 INFO (MainThread) [supervisor.addons] Phase 'services' start 0 add-ons
20-03-08 15:23:12 INFO (SyncWorker_10) [supervisor.docker.interface] Start homeassistant/raspberrypi2-homeassistant
20-03-08 15:24:19 ERROR (MainThread) [supervisor.api.security] Invalid token for access /homeassistant/options
20-03-08 15:24:19 ERROR (MainThread) [supervisor.api.security] Invalid token for access /supervisor/options
20-03-08 15:24:19 ERROR (MainThread) [supervisor.api.security] Invalid token for access /homeassistant/info
20-03-08 15:24:19 ERROR (MainThread) [supervisor.api.security] Invalid token for access /ingress/panels
20-03-08 15:24:20 ERROR (MainThread) [supervisor.api.security] Invalid token for access /discovery
20-03-08 15:24:24 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-03-08 15:24:24 INFO (MainThread) [supervisor.addons] Phase 'application' start 1 add-ons
20-03-08 15:24:24 INFO (SyncWorker_11) [supervisor.docker.interface] Clean addon_core_configurator application
20-03-08 15:24:28 INFO (SyncWorker_11) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-configurator with version 4.7
20-03-08 15:24:33 ERROR (MainThread) [supervisor.api.security] Invalid token for access /app/entrypoint.js
20-03-08 15:24:33 INFO (MainThread) [supervisor.tasks] All core tasks are scheduled
20-03-08 15:24:33 INFO (MainThread) [supervisor.hwmon] Started Supervisor hardware monitor
20-03-08 15:24:33 INFO (MainThread) [supervisor.core] Supervisor is up and running
20-03-08 15:24:33 INFO (MainThread) [supervisor.host.info] Update local host information
20-03-08 15:24:33 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-03-08 15:24:33 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-03-08 15:24:34 INFO (MainThread) [supervisor.host.services] Update service information
20-03-08 15:24:34 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-03-08 15:24:34 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-03-08 15:24:34 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-03-08 15:24:35 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-03-08 15:36:56 ERROR (MainThread) [supervisor.api.security] Invalid token for access /app/entrypoint.js
20-03-08 16:00:21 ERROR (MainThread) [supervisor.api.security] Invalid token for access /app/entrypoint.js
20-03-08 16:03:50 ERROR (MainThread) [supervisor.api.security] Invalid token for access /app/entrypoint.js

Description of problem: The problem first occurred after updating, I had a quite old version before. From mid-January or something. After updating the supervisor panel was no longer accessible and I got the error "Unable to load panel source: /api/hassio/app/entrypoint.js". Naturally, I restarted Home Assistant & the PI a few times, and suddenly it started working again. Later I was working on some other things with my configuration which required me to restart Hass, at first it was working well. However, after a few restarts, the issue occurred again.

I am very new to Home Assistant and I just recently figured out how to gain SSH access, so please tell me if there is something I can try.

Falsen avatar Mar 08 '20 16:03 Falsen

Since I have installed the update 0.106.4 on HassOS, this error also appears with me.

So I cannot access the supervisor anymore.

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

What do I do now if I don't have SSH access?

Node Red is not installed.

Protokolldetails ( ERROR )

Logger: homeassistant.components.hassio.http Integration: Hass.io (documentation, issues) First occured: 6. März 2020, 22:06:36 (18 occurences) Last logged: 19:09:05

Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]

https://community.home-assistant.io/t/cant-enter-in-supervisor-unable-to-load-the-panel-source-0-106-4/176988

https://community-home-assistant-assets.s3.dualstack.us-west-2.amazonaws.com/original/3X/e/3/e33406e5c1fa4f783a82e82ac5e03e272d536ed4.jpeg

phunkybeam avatar Mar 08 '20 18:03 phunkybeam

All good again, it was probably HACS after an update and a HardReset it runs again.

phunkybeam avatar Mar 08 '20 18:03 phunkybeam

This specific error is always the bane of me. I manage three different HA installations and inevitably over the last 18 months this starts happening every few months on one of them. A painful full reinstall and re-setup is required.

It sure would be nice for some way to "reinstall" or reset the supervisor FROM homeassistant core so this is resolved without having to muck around with manually updating things on the command line, or performing a full reinstall.

rsnodgrass avatar Mar 20 '20 14:03 rsnodgrass

Similar problem for me since latest supervisor update. Running latest HA on RPI3B+ Screenshot_20200329-220947 Tried to relaunch HA didn't helped

chris669 avatar Mar 30 '20 08:03 chris669

This issue started out of the blue for me last night as well.

colinfrei avatar Mar 30 '20 08:03 colinfrei

Same here, I've not updated anything and now I get the same error. I also see this in the logs Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]

After reboot the error is gone but also my hassio/supervior dashboard is empty, only showing the core and OS updates

BasTijs avatar Mar 30 '20 09:03 BasTijs

I could resolve this through updating HACS and restarting a few times - not sure what helped exactly.

colinfrei avatar Mar 30 '20 12:03 colinfrei

Can someone please gives me the latest command line to reboot Supervisor, as it changes all the time...

chris669 avatar Mar 30 '20 14:03 chris669

I could resolve this through updating HACS and restarting a few times - not sure what helped exactly.

For me this went into a 500 error and after hard-reboot I cant load the HA webinterface anymore.... anyone know how to remove or update HACS through command line or anything I can try that may solve this? I can access it through samba and SSH.

BasTijs avatar Mar 30 '20 15:03 BasTijs

My problem is when I try to reboot with ha supervisor restart I get a "connection refused" ?? My Google 2 factors is enabled, may be this the cause?

chris669 avatar Mar 30 '20 16:03 chris669

Some thing to me. I noticed the CPU around 90% all the time. And no access to supervisor.

marcozoppy avatar Mar 30 '20 22:03 marcozoppy

@pvizeli, what's your suggestion as command lines are refused (connection) and web interface not available? Dirty (unplug) reboot??

chris669 avatar Mar 31 '20 07:03 chris669

Hi, Same issue as @chris669.

Can't access to supervisor from web interface: Unable to load the panel source: /api/hassio/app/entrypoint.js.

From the CLI I get a connection refused error message:

ha supervisor info or ha supervisor reload or ha supervisor update or ha supervisor logs

Get http://supervisor/supervisor/info: dial tcp 172.30.32.2:80: connect: connection refused

No reboot, no dirty unplug. I have not yet tried to reboot de raspberry pi3 because I still have access by ssh. I'm afraid of losing ssh access after the reboot. I use hassio with Home Assistant 0.107.7.

Best regards

monpelaud avatar Mar 31 '20 13:03 monpelaud

Ok, as no other solutions, I tried the dirty reboot, unplugging my RPI3 and as I was very lucky, it worked, but I hate doing this. So good luck!

chris669 avatar Mar 31 '20 14:03 chris669

Ok, as no other solutions, I tried the dirty reboot, unplugging my RPI3 and as I was very lucky, it worked, but I hate doing this. So good luck!

Same thing for me Hard reboot ! I uninstall HACS... maybe it's the problem

thom13 avatar Mar 31 '20 18:03 thom13

Also the same problem here. Rebooting doesn't seem the solution so far. After reboot I can ssh, but the frontend doesn't come alive. HA 0.106.5, on a RPI3

JayOne73 avatar Apr 01 '20 18:04 JayOne73

Also the same problem here. Rebooting doesn't seem the solution so far. After reboot I can ssh, but the frontend doesn't come alive. HA 0.106.5, on a RPI3

I will reinstall soon because of the problems this introduced, but I managed to get in by doing a 'hassio ha check" and fixed the new config errors due to the auto update. So I cleared the config file and custom_components which allowed to make a snapshots (save your databases etc..) once I got in.

BasTijs avatar Apr 01 '20 18:04 BasTijs

Also the same problem here. Rebooting doesn't seem the solution so far. After reboot I can ssh, but the frontend doesn't come alive. HA 0.106.5, on a RPI3

I will reinstall soon because of the problems this introduced, but I managed to get in by doing a 'hassio ha check" and fixed the new config errors due to the auto update. So I cleared the config file and custom_components which allowed to make a snapshots (save your databases etc..) once I got in.

Well, that didn't the trick for me. So I have installed HA from scratch with a snapshot from 4 days ago. Only excluded the Googledrive backup addon, because that addon stopped working a few days ago. For now the system is up and running again with supervisor 214.

Really pisses me off that you can't control the updates of the supervisor and breaks a running instance after an automatic update.

JayOne73 avatar Apr 01 '20 21:04 JayOne73

Same problem here. Also rerunning the install script did not solve the issue.

floari avatar Apr 04 '20 10:04 floari

Same problem here. I had been having intermittent issues for a while that might have been related to running watchtower (which kept trying to update the supervisor). I have completely removed watchtower, and now I get this error 100% of the time. Would appreciate if anyone could help!!

dereitz avatar Apr 04 '20 15:04 dereitz

Just to update. I completely stopped all services, all docker processes, and removed all my docker containers and images that were associated with the HA installation on my system, but did NOT remove anything from /usr/share/hassio where the config/data is stored. I then installed from scratch using the install script, and my system is once again working. It makes no sense to me why a reinstall would work, but sure enough it did for me. Performing the reinstall was far easier than trying to debug the issue for me!

dereitz avatar Apr 05 '20 16:04 dereitz

@dereitz It works everytime for me too. Basically, if the homeassitant and supervisor images are pulled fresh from the repos for a reinstall, everything fixes itself and starts working. But, a few minutes or sometimes hours later, the same issue resurfaces.

I'll add some logs here shortly, but from what I noticed, there seems to be some DNS related lines that come up before this issue comes up again. It usually happens when it's trying to load some add-on.

ajayjohn avatar Apr 05 '20 16:04 ajayjohn

I face the same problem. ATM I dont have the time to digg deeper into, but maybe tomorrow I will try to reinstall all docker thing. My Installation ist on homeassistan 107.7

Its anoying!

r100gs avatar Apr 05 '20 17:04 r100gs

Just want to comment that i have the same issue every couple of months (or weeks?) AND IT DRIVES ME CRAZY

oooseun avatar Apr 05 '20 19:04 oooseun

same issue here

sailhobie avatar Apr 06 '20 02:04 sailhobie

I constantly get this same issue too.

Kanishkaz avatar Apr 06 '20 04:04 Kanishkaz

I too am having the same issue. Mine runs via Docker and portainer shows hassio supervisor updated April 5th sometime. Trued restarting container, but still face the same issue. Anyone have luck on this?

devtech8 avatar Apr 06 '20 07:04 devtech8

A simple message like " ok, we're working on it" would be appreciated...

chris669 avatar Apr 06 '20 08:04 chris669

I’m having this same issue but it’s happened every night the past 3 nights. The only way I’ve been able to fix it is to stop the supervisor services, remove all supervisor containers along with the home assistant container, rerun the setup script, and reboot. This gets everything working again and all is well all day but sometime around midnight it breaks again. Very frustrating because when it breaks all of my addons stop working which means no node red, which means no security system while we sleep. Is there any way to figure out what exactly is going on to make this happen?

I also have watchtower running. Could the issue be that it's updating Supervisor around midnight? I've disabled the container and will see if it breaks again this evening.

Justalurker1213 avatar Apr 06 '20 10:04 Justalurker1213

Is anyone running Watchtower? If so, check the Watchtower logs to see if it is attempting to update your HASSIO supervisor container. You may also want to keep an eye on the uptime of the HASSIO supervisor container.

In my case, Watchtower was attempting to update the HASSIO Supervisor container, and it was restarting the container in order to attempt to do so. Again, I have no idea why this would "corrupt" the install, but hoping we can find a pattern in order to assist the developers in determining the root cause.

dereitz avatar Apr 06 '20 12:04 dereitz