I’m having this issue, and I’m not runing Unraid - just commandline docker. How can I attempt this description-shuffling on my instance?
As to the ‘this isn’t a stable configuration’, I moved to this configuration when it was made the official configuration for new installs, and HA doesn’t have an OVA for the OS yet, so here I am.
If it makes any difference, I do have SSL.
Not sure how to help outside of Unraid. Basically you are forcing the Supervisor docker image to pull and reset with a new image. Not sure if that makes sense. In unraid everything is broken out to separate installs. Ill post screen shots when I can which will better explain.
e[31m20-03-04 11:29:40 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].e[0m
e[31m20-03-04 11:29:40 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].e[0m
e[32m20-03-04 11:29:45 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m20-03-04 11:29:45 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m20-03-04 11:29:45 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_noderede[0m
e[32m20-03-04 11:29:45 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_noderede[0m
e[31m20-03-04 11:29:45 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].e[0m
e[31m20-03-04 11:29:45 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].e[0m
Errors im getting in the logs. Not sure what the hell they mean… if you notice the SSL false repeated, made me think that had something to do with it. I guess I was wrong.
I’m also seeing this same exact issue…not exactly sure when it started, but pretty sure within the last week or two. I absolutely have SSL set up via reverse proxy set up on my instance. Also not running it from within Unraid, just a regular Ubuntu VM.
Everyone needs to reboot and watch the logs to see if we can find some similarities. If you see errors post them. If you figure something out, please post it. Im glad to see its not just me.
Update: I found this link and followed those steps and mine is back up and running now. Very odd.
Similar! Just pulling the supervisor to latest fixed me up just fine.
So weird… I was jumping over to the supervisor tab andit gave me this update notice… a supervisor update… never have a seen this before… 
The update does not work. Not sure how to fix this in Unraid.
Update: Im up and running with no errors in the logs. All seems right with the world now.
Worked a treat. Thanks.
Hello,
I have still this issue, started around month ago after HA and hassio update + activate SSL. All apps such as SSH server (server is refusing the connection), file editor (pinned to left menu) and supervisor are not accesible. Unfortunately I cannot see even logs.
Do you have an idea how to trigger an update? (rpi3b+)
Maybe somehow via configuration change in sd card?
If you were using unraid, I could help you. Unfortunately I do not know how to do it on Pi. One thought that could work and make the process easier is to install portainer on the pi. Allowing you to manage the container better.
Same happening to me. It has been on and off for a month and now with the latest hassio update it just died. I must say it’s always something with Hassio that breaks with every update. It’s a great idea but I’m getting close to simplify my life and say bye to home automation.
Hi, i have the same problem, hassio supervisor is broken, reinstall directly with script don’t work, made a fresh install and reload my backup and work fine for a couple hours and the problem back, on the log have this “Login attempt or request with invalid authentication from 172.30.32.2”, i think is the last update of pi hole , but who knows
I did hard reset and it helped …
Best regards,
Mariusz
Just did a fresh install.
VM with ubuntu and docker, using the new script.
curl -sL “https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh” | bash -s
Now when entering home assistant i don’t have access to the supervisor tab and get the unable to load the panel source. Any idea hor to solve this. Its a fresh install so that will not work.
Thanks
I have the same problem but without reinstalling.
Good morning,
Here is the deal, clearly something is wrong as we are seeing more and more with these issues. I currently using Unraid as my Nas and Hypervisor. I have a GUI interface that really simplifies the process for me. Maybe those of you that are using Docker, download and install portainer, not within Hassio ( like the addon) but install as a separate container to help. Typically, when we see a problem and our Hassio/supervisor tab does not work, it is because there was an update applied to the DOCK Supervisor. Our current one becomes outdated and we start getting these errors. What I do is, when the problem starts I have to manually update the Repository. Currently this is how it looks: homeassistant/amd64-hassio-supervisor:214 when I start getting problems Ill change it to: homeassistant/amd64-hassio-supervisor:215 or maybe to 216. So basically im guessing what the update would look like. You can try using homeassistant/amd64-hassio-supervisor:latest this will automatically get the most recent update. However this does not work for me in unraid for some reason. Hope that helps.
We need to all open an issue on the Github for Hassio install. Reference this thread so they can better understand the issues we are having.
Good luck, stay safe and well.
For those of you who are using unraid, Here is an alternative to running Hassio but in a VM. I am no longer using the docker version and now using this method . Works well, I can pass through and use my Wyze sense adapter and all…
Same error on an Ubuntu installation. Reinstalled multiple times, it’s fine for a while but then starts throwing the same as error as OP, plus this in the supervisor container: Invalid token for access /app/entrypoint.js
I’m another to add to the list of this same problem now!
I’ve reinstalled supervisor, following: https://www.home-assistant.io/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host
and i still have the same problem?
I’ve also manually deleted the image and container for supervisor, and rerun the scripts from the link above, and neither have fixed this issue…