/api/hassio/app/entrypoint.js failure

I have Home Assistant 0.107.7 with frontend 20200318.1 and it is performing automation just fine but many panels fail to load (such as supervisor, esphome, glance, file editor). The error message is “unable to load the panel source: /api/hassio/app/entrypoint.js” which is the same for all panels. So, Supervisor can not be used and in hassio that is the only way I know to restore a snapshot or update. In the log I have noticed that it can not reach 172.30.32.2
I sure could use some advice. I went in to add an esphome for a new esp32 module, but I am stopped cold by this. Thanks, Doug

Really need help. I can not figure this out. Maybe a security update? Breaking feature during upgrade? I really do not know how to debug this and any suggestions would be a big help. Thanks, Doug

I can’t help but I am experiencing the exact same issue so I’m glad to know I didn’t break something. I only just switched to supervised. Hopefully someone will come along with some advice.

I am noticing that the hassiosupervisor docker seems to be failing to start.I think I am going to try reinstalling it.

That worked at least for now it seems to be working. For anyone else I removed and reinstalled only the Homeassistant Supervised docker container and left everything else. Not sure what this did but it got it working. I didn’t lose anything but I would recommend backing up your configs just to be safe.

Thanks. I do not know how to re-install the supervisor docker. With the supervisor unavailable, I have not had SSH access. Any suggestions? I have the hass.io on a RPI3B.

Sorry no I can’t help with that. Mine is in Unraid so it was very simple, I am not familiar with the Pi environment

Interesting, the problem went away. As usual, I did various things and can not be sure how it was fixed. I had setup another SD flash with a current download and was investigating what needed to be done to reproduce my system. Then I went back to my original SD to check some values in the config directory. I also removed the zwave transceiver. It powered up working with access to the supervisory panel and all other panels. I will slowly investigate with lots of backups during the process. After a snapshot, I will update to the latest release and restore my zwave transceiver. I find using home-assistant is challenging because it is a very dynamic entity. My time limitations and lack of deep knowledge in the sophisticated software causes lots of problems and mistakes that are challenging to say the least.
Thanks for taking the time to advise and help me.

Interestingly this error showed back up for me today out of nowhere.