bckthomas
commented
4 years ago It worked fine for months. I followed this video for the installation https://www.youtube.com/watch?v=aAh8_8u-Zw0
Open Falsen opened 4 years ago
bckthomas
commented
4 years ago It worked fine for months. I followed this video for the installation https://www.youtube.com/watch?v=aAh8_8u-Zw0
colinfrei
commented
4 years ago I just had this issue again, after installing an update of a HACS app. It's only ever happened since using HACS, so I do feel there's a link there.
Unplugging the hardware resolved it.
ludeeus
commented
4 years ago It's only ever happened since using HACS, so I do feel there's a link there.
I really doubt that, but there is a reason you get this on every startup for every custom_component you have ;)
WARNING (MainThread) [homeassistant.loader] You are using a custom integration for xxxxx which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
LennyLip
commented
4 years ago same here
20-04-11 19:03:02 ERROR (MainThread) [supervisor.api.security] Invalid token for access /homeassistant/info
20-04-11 19:14:29 ERROR (MainThread) [supervisor.api.security] Invalid token for access /app/entrypoint.js
JXGA
commented
4 years ago I have started to get this error, too. My supervisor container kept stopping by itself. I tried reverting to 214 & 215, but it kept auto-upgrading to 216 and stopping. Somehow it has come back up again, but now I get 'Invalid token for access' errors all over the place.
Tried ha su repair but all that seemed to do was delete all of my other stopped containers without asking.
Edit: I do not run watchtower, it seems supervisor updated itself. I certainly didn't do it.
bckthomas
commented
4 years ago There are some errors with hassio on homeassistant reboot
2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/options return code 403. 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /supervisor/options return code 403. 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/info return code 403. 2020-04-11 22:18:31 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version: 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /ingress/panels return code 403. 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can't read panel info:
JXGA
commented
4 years ago There are some errors with hassio on homeassistant reboot
2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/options return code 403. 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /supervisor/options return code 403. 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/info return code 403. 2020-04-11 22:18:31 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version: 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.handler] /ingress/panels return code 403. 2020-04-11 22:18:31 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can't read panel info:
I get these too - I imagine it's due the supervisor 'invalid token'.
dereitz
commented
4 years ago 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!
I don't want to jinx it, but I do want to provide an update. I still have Watchtower disabled and after this reinstall, my HA installation has been flawless. It seems to point to the fact that Watchtower was interfering with my installation. I plan to revisit Watchtower again but will be using labels as others have done.
moobaabaa
commented
4 years ago Here I am again with a busted Supervisor upgrade. Went from 17 to 19. This happened when I went from 14 to 16 so I completely wiped everything and restarted. 16-> 17 was fine.
20-04-23 03:53:00 INFO (MainThread) [supervisor.discovery] Load 1 messages
Traceback (most recent call last):
File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/src/supervisor/supervisor/__main__.py", line 47, in <module>
loop.run_until_complete(coresys.core.setup())
File "uvloop/loop.pyx", line 1456, in uvloop.loop.Loop.run_until_complete
File "/usr/src/supervisor/supervisor/core.py", line 77, in setup
await self.sys_ingress.load()
File "/usr/src/supervisor/supervisor/ingress.py", line 56, in load
self._cleanup_sessions()
File "/usr/src/supervisor/supervisor/ingress.py", line 74, in _cleanup_sessions
valid_dt = utc_from_timestamp(valid)
File "/usr/src/supervisor/supervisor/utils/dt.py", line 87, in utc_from_timestamp
return UTC.localize(datetime.utcfromtimestamp(timestamp))
OverflowError: timestamp out of range for platform time_t
Any ideas? I unplugged and plugged it back in.
This is running in docker on raspbian on an rPi4.
kuchel77
commented
4 years ago I was having the same issue on a standard Ubuntu 19.10 running no other software that should interfere with HA.
What it seems is that the tokens for accessing HA from the supervisor had disappeared, so that when it went through the check in supervisor/api/security.py the self.sys_homeassistant.supervisor_token was none.
Deleting the supervisor image, upgrading to 219, reinstalling didn't work at all like it had previously.
What did work however, was running
ha core rebuildEdit: had wrong formatting above.
Which seemed to refresh the tokens, and so that now my system is back up and running, and no longer has the same issues. As soon as it was done, I had access to the Supervisor panel again, as well as access to the other ingress panels that had disappeared. I am not sure why the token disappeared (initially this time on 0.108.0 and 217 after a reboot from an extended power outage) but it is back and working again after a reboot.
drthanwho
commented
4 years ago Same issue for me too. Occurred last night. I was editing a code for a switch and after last restart Supervisor isn't connected and I have lost all ability to restart HA now since all possible options require you have access to Supervisor. Only option is to power cycle. SSH is not working, yet other addons like samba, wireguard and deconz are working (but ingress icons missing)
It can't be HACS as I never touched that. I literally just added one line for "command_state" of a switch so I doubt it would be that either.
I know there was an update rolled out for Supervisor (@pvizeli ?), so was wondering if that could be the issue? Do these install themselves if you restart HA? I'd also have assumed that if HA coudn't connect to Supervisor during boot that safe mode would kick in :(
These are some of the logs relating to the issue
2020-04-22 23:15:31 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /supervisor/ping request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:15:31 WARNING (MainThread) [homeassistant.components.hassio] Not connected with Hass.io / system to busy!
2020-04-22 23:15:31 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/options request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:15:31 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /supervisor/options request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:15:39 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-04-22 23:15:39 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version:
2020-04-22 23:15:40 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /ingress/panels request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:15:40 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can't read panel info:
2020-04-22 23:15:41 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /discovery request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:15:41 ERROR (MainThread) [homeassistant.components.hassio.discovery] Can't read discover info:
2020-04-22 23:15:55 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:16:45 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:16:49 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:20:00 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:21:10 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:22:06 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:25:52 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:25:53 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:25:58 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:26:47 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:27:56 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /host/reboot request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-04-22 23:27:56 ERROR (MainThread) [homeassistant.components.hassio] Error on Hass.io API:
2020-04-22 23:30:20 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:30:52 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
2020-04-22 23:34:26 ERROR (MainThread) [homeassistant.components.hassio.http] 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)]
Hybr1dth
commented
4 years ago Same issue here. Cannot access supervisor, cannot SSH in anymore. Any service restart called via developer tools gives connection issues.
Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] Client error on /addons/supervisor/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] Client error on /addons/http/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] Client error on /addons/core_ssh/start request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] Client error on /addons/supervisor/start request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] Failed to call service hassio/restore_full. expected dict for dictionary value @ data['service_data']. Got 'snapshot'
dereitz
commented
4 years ago 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!
Sadly, this error has reappeared today (~1 month/27 days or so after reinstall). There have been no significant changes to my system that I can recall other than the normal upgrades of the HA container via the Supervisor. I'm still running Ubuntu 16.04 and still have Watchtower DISABLED. Is there any logging/debugging/etc that I can provide to help diagnose this issue? It seems to be related to the tokens. Perhaps they expire in certain circumstances????
dereitz
commented
4 years ago Ok, so might be a slightly different problem this time... logs below, which might be a failed auto-upgrade (sorry for the additional comment/noise):
20-05-01 19:18:45 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json 20-05-01 19:18:45 INFO (MainThread) [supervisor.store] Load add-ons from store: 69 all - 0 new - 0 remove 20-05-01 19:28:45 INFO (MainThread) [supervisor.tasks] Found new Supervisor version 20-05-01 19:28:45 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 220 20-05-01 19:28:45 INFO (SyncWorker_6) [supervisor.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 220. 20-05-01 19:28:56 INFO (MainThread) [supervisor.supervisor] Fetch AppArmor profile https://version.home-assistant.io/apparmor.txt 20-05-01 19:28:56 INFO (MainThread) [supervisor.host.apparmor] Add or Update AppArmor profile: hassio-supervisor 20-05-01 19:28:56 INFO (MainThread) [supervisor.host.services] Reload local service hassio-apparmor.service 20-05-01 19:28:56 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1 20-05-01 19:29:01 INFO (MainThread) [main] Stopping Supervisor 20-05-01 19:29:01 INFO (MainThread) [supervisor.api] Stop API on 172.30.32.2 20-05-01 19:29:01 WARNING (MainThread) [supervisor.misc.forwarder] DNS forwarding is not running! 20-05-01 19:29:01 INFO (MainThread) [supervisor.core] Supervisor is down
dereitz
commented
4 years ago Ok, so might be a slightly different problem this time... logs below, which might be a failed auto-upgrade (sorry for the additional comment/noise):
20-05-01 19:18:45 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json 20-05-01 19:18:45 INFO (MainThread) [supervisor.store] Load add-ons from store: 69 all - 0 new - 0 remove 20-05-01 19:28:45 INFO (MainThread) [supervisor.tasks] Found new Supervisor version 20-05-01 19:28:45 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 220 20-05-01 19:28:45 INFO (SyncWorker_6) [supervisor.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 220. 20-05-01 19:28:56 INFO (MainThread) [supervisor.supervisor] Fetch AppArmor profile https://version.home-assistant.io/apparmor.txt 20-05-01 19:28:56 INFO (MainThread) [supervisor.host.apparmor] Add or Update AppArmor profile: hassio-supervisor 20-05-01 19:28:56 INFO (MainThread) [supervisor.host.services] Reload local service hassio-apparmor.service 20-05-01 19:28:56 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1 20-05-01 19:29:01 INFO (MainThread) [main] Stopping Supervisor 20-05-01 19:29:01 INFO (MainThread) [supervisor.api] Stop API on 172.30.32.2 20-05-01 19:29:01 WARNING (MainThread) [supervisor.misc.forwarder] DNS forwarding is not running! 20-05-01 19:29:01 INFO (MainThread) [supervisor.core] Supervisor is down
Yes, so "docker stop hassio_supervisor" and "docker start hassio_supervisor" and I'm back in business. Sorry for the additional comments -- guess I should have taken a closer look before commenting!
dcoliv
commented
4 years ago Hi, I'm experiencing similar problems too. I left behaviour and logs in another issue, which might be related to this one:
https://github.com/home-assistant/supervisor/issues/1675#issuecomment-623438301
rainfactor
commented
4 years ago Mine keeps crashing daily and I see this:
Can't read last version: 10:13:15 AM – Hass.io (WARNING) - message first occurred at 12:07:32 AM and shows up 12 times 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)] 10:13:15 AM – Hass.io (ERROR) - message first occurred at 1:02:36 AM and shows up 11 times 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)]
Then the supervisor keeps looping(recreate-delete) and never comes back unless I restart the whole NAS The hass container along with all the other ones are running on Docker Synology
It drives me crazy as I don't know what is causing it.
sblantipodi
commented
4 years ago I have only official integrations and the issue still there.
EGP01
commented
4 years ago I have started having this issue. This is the second time in 2 weeks. None of the supervisor commands are working and I cant get ssh access to reboot so I am going to have to manually pull the plug. I hope it doesnt bork my install. I have copied all my config files just in case as I cant run or check snapshots
I am running a standard install ie. Raspberry pi 3, Home assistant (i.e.all in 1 HASSOS, supervisor etc sorry cant remember the new naming system).
I am running some custom components including HACS. I noticed the supervisor wasn't working after the lastest HACS update and I couldn't reboot. Could be coincidence??
sblantipodi
commented
4 years ago this problem is pretty urgent to me, is there some fix planned?
jebentancour
commented
4 years ago same problem here
BasTijs
commented
4 years ago Mine got killed again. The entry error in the UI and if I SSH it says something like this for each command: Get http://supervisor/supervisor/logs: dial tcp 172.30.32.2:80: connect: no route to host
DickiePhitt
commented
4 years ago I have exactly the same problem. Again standard Rpi3, Hass, etc I have neither the tech skill / time / inclination to be continually problem solving. Like many others I'm using HA as a tool, not a full time occupation. Needs a fix or many like me will be walking
rainfactor
commented
4 years ago I have exactly the same problem. Again standard Rpi3, Hass, etc I have neither the tech skill / time / inclination to be continually problem solving. Like many others I'm using HA as a tool, not a full time occupation. Needs a fix or many like me will be walking
Not sure if you realize that this is a free project that is being worked on by ppl in their spare time. Yes there will be occasional glitches and one is expected to get his hands dirty and tshoot. If you are not willing to do that or don't have time maybe this is not for you and maybe can find a paid alternative where you can ask for help and will receive it in due time as you will be paying for it.
dereitz
commented
4 years ago Can anyone reliably replicate the issue? Knock on wood, but I haven't had the issue since I disabled Watchtower and uninstalled/installed using the install script again.
drthanwho
commented
4 years ago I don't have any reliable evidence to support this but I seem to get it only when there is a supervisor or HassOS update. And during restarting the update installs itself and then that's when supervisor doesn't come back.
I wish I had something better to offer. It definitely doesn't help when everyone just comments saying "same", "same here" etc. without able to pinpoint the reason. And definitely no matter how annoying it might be blaming the devs is not helping anyone.
rainfactor
commented
4 years ago As I have posted here as well my update is as follows: Since the Docker based support was announced to be discontinued, I have moved to a VM hosted on my NAS. running the original HASS Os I haven't had any issues since then. Everything is working perfectly (for me anyways). The consensus as far as I could read is that the Docker virtualization seems to be adding an extra layer of complexity that breaks as you can tell. I am no dev and not sure what exactly would that be
cogneato
commented
4 years ago @rainfactor "docker based support" was never discontinued. This install requires docker in order to exist. Docker is included with HassOS. All the addons are docker containers.
You are not managing it yourself or mucking it up with Watchtower or Portainer or running this whole docker ecosystem inside another container...these are all good things.
rainfactor
commented
4 years ago @rainfactor "docker based support" was never discontinued. This install requires docker in order to exist. Docker is included with HassOS. All the addons are docker containers.
You are not managing it yourself or mucking it up with Watchtower or Portainer or running this whole docker ecosystem inside another container...these are all good things.
My wording was far from perfect. I meant the Docker Images of the HASS like the "all in one" images that one may deploy from the Docker repository. NOT the official HASS OS . I may not be the smartest one or I am lacking basic Docker knowledge and couldn't build a good image for myself therefore I simply stopped using this kind of setup and switched to one of the official HAssOs that works perfectly in a VM
rct
commented
4 years ago I just ran into this on 0.111.4, using a "supervised" install. My guess at this point is supervisor tried to update itself and the process failed. I'm basing that on:
ha supervisor commandsUsing docker stop to stop the supervisor container that was no longer accepting connections resolved things. Once the container died, systemd restarted it.
Unfortunately I wasn't able to capture the logs from before supervisor was restarted.
KentuckyMC
commented
4 years ago Same issue here now. Yesterday everything worked like a charm, waking up today and the things are broken. Got different errors now when restarting by the settings > server maintenance:
Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
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)]
Can't read last version: 13:46:33 – Hass.io (WARNING) - bericht kwam voor het eerst om 12:51:33 en verschijnt 2 malen
As mentioned here: https://community.home-assistant.io/t/unable-to-load-the-panel-source-api-hassio-app-entrypoint-js/126821/136 there is a new version of the supervisor? When I look into my settings, I still see 229 over there, but it's very suspicious that that update was from yesterday. Any thoughts? @pvizeli Maybe?
robbinjanssen
commented
4 years ago I experienced the same this morning, however my supervisor did update to 231 (might have done that automatically after a reboot?)
darylvL
commented
4 years ago I also started experiencing this issue this morning, while I didn't update my supervisor (or anything else on my home assistant) in the last 9 days.
colinfrei
commented
4 years ago I had this issue again for the first time in a while. The main thing I recall doing recently is the latest HassOS update.
v1-valux
commented
4 years ago Same problem here.. Installed via Supervised Docker Install (on raspi-os). Neither Supervisor, nor HA can be started again (after rebooting).
The problem came up after the last HA update (113.3) Supdervisor Version is 229
v1-valux
commented
4 years ago I managed to solve the Issue by using Portainer (Docker Management) to recreate the container with the latest image.. Now it starts up all the containers including home-assistant again..
Maybe thats the way to go here..?
pvizeli
commented
4 years ago This is not an issue, it show just there is an issue which can be affected by so many things. This means, everybody here can have a different issue which end up in "/api/hassio/app/...". The only way to send us the needed information on a supported system is to enable the new diagnostics function.
I lock now this issue because all helps are just for his own system and will 99% not work for others. You need debug the issue for you local system or send diagnostics reports which is the only way that on next update this bug for one of the writer here is fixed.
pvizeli
commented
4 years ago You can use the help portal: http://my_ip_addr:4357
Home Assistant release with the issue: 0.106.5
Operating environment (HassOS/Generic): Raspberry PI, installed with .iso
Supervisor logs:
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.