Hass.io installs but doesn't run?

Installation Home Assistant OS
1

I am trying to install Hass.io again on my Ubuntu 18.04 server in Docker.

I had Hass.io running, It completely collapsed after an update and I wasn’t able to get things working properly. Since I wasn’t too far into anything I decided I’d dump all the Has.io related docker container and start over.

So II mistakenly installed Home Assistant on Docker, the install went smoothly and I was able to access HA on port 8123.

Since I wanted Hass.io I decided to dump Home Assistant and install Hass.io. Unlike a normal docker install where you do things like --name and -p 8123:8123 I ran a curl script found here https://github.com/home-assistant/hassio-build/blob/master/install/README.md

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s

So the Docker Container installs and is running fine. But when I try to connect to IP:8123 I get a > Unable to connect

Firefox can’t establish a connection to the server at 192.168.1.105:8123

Any thoughts before I switch over to HA instead of Hass.io? I’ve tried restating the container with no change.

Thanks,
-Rob

2

Are you sure it’s actually running?

Did you remove the HA docker container before running the installer script?

3

Portainer says the hassio_supervisor container is running.
I’ve tried stopping and restarting it a number of times without success.
When I pull the log for this container the last line says >

18-10-13 03:02:01 INFO (MainThread) [hassio.core] Hass.io is up and running

The first time I ran the installer script I forgot to remove the HA container so I removed both and started the installer script a second time.

4

Hi there,

I have same problem there. When i check docker run, it said

19-02-25 10:19:02 INFO (MainThread) [hassio.core] Hass.io is up and running

but with browser on port 8123, it appear nothing

5

Just as an FYI I never got this sorted out.
I wiped the container and went with Home Assistant. Haven’t looked back.

1 Like
6

I have the same problem, when running sudo netstat -tulpn it’s clear that there’s nothing listening on port 8123. I’m going to take the same solution and throw away hassio - it doesn’t seem worth the hassle :wink: