This is caused by older startup scripts, which causes the Supervisor to have incorrect permissions. The permissions changed over a half year ago, your instance would have thrown warnings for that same time as well.

Running the install instructions from our website again will fix this issue.

https://www.home-assistant.io/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host

Running the installer again, preserves data.

Generally the above-listed installer command “should” be enough. But as a general good practice, running the full set of instructions might uncover some “older” missing things.

Warning

Note: I strongly disadvise to run manual Docker pull, tag or similar commands, it will only cause things to go out of sync OR ending up with an edge dev version that might be broken.

I don’t know what caused it, but after docker pull homeassistant/amd64-hassio-supervisor:202 docker tag homeassistant/amd64-hassio-supervisor:202 homeassistant/amd64-hassio-supervisor:latest systemctl stop hassio-supervisor.service systemctl start hassio-supervisor.service

It work’s again. it even displays version 207 in the logs. So i guess the pull/tag did nothing, however stopping and starting of hassio-supervisor.service did not work before. ¯\(ツ)/¯

@bratanon can you try the four commands and see if it solves the issue for you?

Why is this closed- it is an ongoing issue.

THANKS EVERYONE! This worked I logged in via ssh sudo docker container stop hassio_supervisor sudo docker container rm hassio_supervisor sudo curl -sL “https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh” | sudo bash -s sudo docker restart homeassistant

I got mine finally working too. I had to fix it slightly differently.

First:

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

When I then tried:

docker tag homeassistant/amd64-hassio-supervisor:latest homeassistant/amd64-hassio-supervisor:latest

I got this error:

Error response from daemon: No such image: homeassistant/amd64-hassio-supervisor:latest

So instead: docker tag homeassistant/amd64-hassio-supervisor:207 homeassistant/amd64-hassio-supervisor:latest

And then, it worked:

docker tag homeassistant/amd64-hassio-supervisor:latest homeassistant/amd64-hassio-supervisor:latest

And finally:

systemctl disable ModemManager.service curl -sL “https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh” | bash -s

For some reason latest / latest didn’t work for me. I have to admit I’m not sure about most of this. So this is just my experience.

Ah… seems to be a problem because before that i already tagged release 206 as latest. Doing this:

docker pull homeassistant/amd64-hassio-supervisor:latest

docker tag homeassistant/amd64-hassio-supervisor:latest homeassistant/amd64-hassio-supervisor:latest

and then doing again:

curl -sL “https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh” | bash -s

seems to have fixed it

So, for everyone on 18.04, this is how I manage to get it to work with help from @ludeeus .

You need to run the install scritp again. # curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s

https://www.home-assistant.io/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host

This works for me!

I’m going to share my fix for “Unable to load the panel source: /api/hassio/app/entrypoint.js.” issue here in case it helps anyone. Just so you know the background, I was trying to move a previous instance of hass.io from an ubuntu 16.04 lxc container into an ubuntu 18.04 VM. Banged my head around for a few hours before figuring this out so here are my steps:

1 sudo -i - Make sure you have network-manager installed or install with apt-get update && apt-get -y install network-manager 2. sudo systemctl stop hassio-supervisor.service 3. docker stop $(docker ps -a -q) && docker rm $(docker ps -a -q) - You may also need to do docker rmi $(docker images -a -q) but I didn’t have to 4. Move your files over from previous installation if you need to 5. sudo systemctl start hassio-supervisor.service - at this point everything started except homeassistant docker container itself (which you can check by running docker ps) so my final step was… 6. reboot now

This seemed to do everything needed to restart the containers with proper networking.

in case anybody else is also unhappy about automatic supervisor updates, vote here: https://community.home-assistant.io/t/feature-request-block-supervisor-auto-updates/112743

Yes, but now your versioning is out of sync, you are running 202, but the system thinks you are running 207.

I think it must have updated itself when I restarted the supervisor service

docker pull homeassistant/amd64-hassio-supervisor:207
207: Pulling from homeassistant/amd64-hassio-supervisor
Digest: sha256:1dfaedd7c36f935b7dc184812fae1649bb1124a0bfa9e3edf9ca411bfa5804b7
Status: Image is up to date for homeassistant/amd64-hassio-supervisor:207
docker.io/homeassistant/amd64-hassio-supervisor:207

REPOSITORY                               TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
homeassistant/amd64-hassio-supervisor    207                 sha256:1dfaedd7c36f935b7dc184812fae1649bb1124a0bfa9e3edf9ca411bfa5804b7   ff6b7ba44d13        35 hours ago        277MB
homeassistant/amd64-hassio-supervisor    latest              sha256:1dfaedd7c36f935b7dc184812fae1649bb1124a0bfa9e3edf9ca411bfa5804b7   ff6b7ba44d13        35 hours ago        277MB

I don’t know what caused it, but after docker pull homeassistant/amd64-hassio-supervisor:202 docker tag homeassistant/amd64-hassio-supervisor:202 homeassistant/amd64-hassio-supervisor:latest systemctl stop hassio-supervisor.service systemctl start hassio-supervisor.service

It work’s again. it even displays version 207 in the logs. So i guess the pull/tag did nothing, however stopping and starting of hassio-supervisor.service did not work before. ¯_(ツ)_/¯

@bratanon can you try the four commands and see if it solves the issue for you?

This worked for me

Go through all the steps for the (re-)installation https://www.home-assistant.io/hassio/installation/#preparation

Do not skip the sudo -i, or systemctl disable ModemManager

So, for everyone on 18.04, this is how I manage to get it to work with help from @ludeeus .

You need to run the install scritp again. # curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s

https://www.home-assistant.io/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host

Also having the same issue on Ubuntu 18.04 LTS, and tried the 4 commands above. Also did not work for me.