Getting 404: Not Found when updating to 0.107

Hello,
I tried updating to 0.107 using the web interface but when it “finished” all I get at the web interface is “404: Not Found”. I’m using a docker installation via the instructions here and has worked up until now. I unistalled and reinstalled home assistant and the same issue is happening. The log file is below but don’t understand whats happening.
Thank you in advance for the help! :slight_smile:


2020-03-18 12:26:25 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.
2020-03-18 12:26:30 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/ping request
2020-03-18 12:26:30 WARNING (MainThread) [homeassistant.components.hassio] Not connected with Hass.io / system to busy!
2020-03-18 12:26:30 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', 8$
2020-03-18 12:26:30 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-03-18 12:26:30 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-03-18 12:26:30 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version:
2020-03-18 12:26:30 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-03-18 12:26:30 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can't read panel info:
2020-03-18 12:26:30 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-03-18 12:26:30 ERROR (MainThread) [homeassistant.components.hassio.discovery] Can't read discover info:

1 Like

UPDATE: i just tried a fresh install using the hassio image, reverted to a previous version using a backup i had, then updated and I’m getting the same error…

1 Like

Hi @theChef613, did you manage to fix this? I’m getting the same errors.

1 Like

Hi @theChef613 and @harpdogg I have exactly the same problem :frowning:
I have update from version 0.105 to 0.107 using web interface (in the same way as I did it many times before). After update always when I try to access web interface by 192.168.1.48:8123 I always get “404: Not Found”. All my automations are working as before. I tried to update to a newest build 0.108.0b3, but without any change.
In the home-assistant.log I don’t see any problem related to UI

2020-04-05 20:50:54 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds.
2020-04-06 04:51:13 WARNING (Thread-3) [pychromecast.socket_client] [Obývací pokoj:8009] Heartbeat timeout, resetting connection
2020-04-07 03:28:40 WARNING (Thread-3) [pychromecast.socket_client] [Obývací pokoj:8009] Heartbeat timeout, resetting connection
2020-04-08 04:24:00 WARNING (Thread-3) [pychromecast.socket_client] [Obývací pokoj:8009] Heartbeat timeout, resetting connection

@theChef613, @harpdogg, @tichao
I just upgraded from 0.104.3 to 0.108.2 and now I’m getting the 404 error. Did anyone ever determine how to fix this?

Hi, I’m still waiting and hoping that somebody reply to this thread with solution…

I made a clean install to 108.2 I was not able to create an acount and I get 404 in Safari and Crome on mac firefox on linux crome on Android and Safri on iphone help

I resorted to installing on virtual box instead of directly on my Ubuntu machine. So far so good.

ok nice, but I would like to have some different solution than compleat reinstall from the scratch :frowning: It must be some configuration issue

Hello some magic happens and web interface suddenly start working :slight_smile: So I’m happy, but curious what causes this problem and how it could cure automatically :thinking: I tried it before on more computers, so it couldn’t be cause for example by web browser cash…

sorry for the late response! I ended up using a fresh install and redoing everything :confused: