Update to 82 and now I can't access the web interface

Installation Home Assistant OS
1

I clicked the update button in the Hassio tab this morning and, after waiting an hour or so, noticed that I could no longer access the web interface. I have hard booted the Pi several times and nothing. SMB and SSH access still work, so I was able to grab everything in the config folder. My latest full backup was a month ago, however.

I tried renaming the database files and configuration file and did a restart. It automatically created new ones, but still not working.

Any ideas? Should I just blow away the SD card and start from fresh?

Thanks.

1 Like
2

Have you refreshed your browser cache? Ctrl-f5 in chrome/firefox.

1 Like
3

Yeah. Tried different browsers and cleared cache manually. Nothing.

4

Try starting HA in debug and check the logs… Could you post them here?

5

I thought of that and did switch the logger default to debug before another restart. The log is about 1200 lines long. Just post the entire thing here, or is there a specific section maybe? The lions share of the debug logs appear to be Chromecast I think (pychromecast.socket.client) “failed to connect” messages. I assume they are not related?

7

Looks good on first sight (quick look). No errors thrown by any component or core.

I wasn’t expecting a full log trace in this post. Be careful for sensitive data like your location etc. Just my 2 cents… That being said can you double check in your file (word search " ERROR ").

So far HA has never let me down when it comes to showing what is wrong in the logs. This leads me to believe that typically something else must be bad (network? computer?).

There are a couple of steps before you have to format your SD card (and loose your specific configurations like symlinks etc.). I’ve quickly written down what I would try in your case:

  1. Quickly disable all components by commenting them quickly
  2. If the UI starts: Re-enable them 1 by 1
    a. Found the component blocking the start? Check what changed…
    be. No success? Step 3
  3. Try installing HA on other instance (by migrating the configuration YAML’s and other config files). Something that is very easily done when running HA with Docker.
  4. Still no luck? Backup all your data… also those from extra apps you installed like Node-RED and more.
  5. Fresh install
  6. Copy paste everything back

Hopefully this will help you in finding the root cause.

1 Like
8

Thanks for the advice. I will let you know what I figure out.

I really appreciate the help.

9

I’m chasing down the network angle as nothing else is helping yet. I ran a netstat command on my RP3 and I don’t see port 8123 open at all. I’m not overly familiar with Linux, but is there a way to see if the web server is running? Anything else I should check?

10

I had something similar happen once, I ended up using an incognito browser sesstion and it worked.

I’d try logging in with SSH and check that the HA container is actually running, try docker container ls

11

I try that command and I get an error: Got unexpected response from the API: Addon does not exist.

12

So a quick update:

I gave up this morning and started over. I installed a fresh hassio which worked fine. I then copied up my config files and reloaded components which worked as well. Everything was back up and running. I then went into the config to do some cleanup work - setting the recorder to purge after a few days - performed a HASS restart from the gui, and I’m back to the same issue. I can access via SSH or SMB, but not via the web interface. Sigh…

13

Had the same issue after upgrading from 0.81.6 to 0.82: no web interface. After the struggle with V3 Mosquitto broker this week, I think the best lesson is: wait a few days before upgrading :frowning:

2 Likes
14

I’m starting to think you are correct.

My plan is to start over yet again, but not install Mosquitto and leave things for a week.

15

Just in case it helps someone else, I’m 90% certain that this is related to mqtt using mosquitto. I rebuilt from scratch three times today and would experience the same issue within an hour of installing add-ons. I then decided to simplify things and removed all of my mqtt code and skipped installing mosquitto. I have been running perfectly for about 6 hours now.

Could be coincidence though.

16

Who would know without your logs.

1 Like
17

FYI
I had the same issue after an upgrade. Did some investigation, it turned out to be Google Chromecast that blocked it for me. Found some errors in the logging, disabled the discovery component, removed every cast device from the .storage/core.* files and it worked after a restart.

I also use mosquitto which is still in working order now.

1 Like
18

Yup, I can confirm that this is an issue with Chromecast. I disabled it, and haven’t had an issue in 5 days now, even with MQTT running.

19

I have a feeling this is my problem… can you please explain how you modified those files? I don’t understand how to find them. I’m using hass.io

20

It’s in your configuration.yaml. You need to add 2 lines to tell Home Assistant to NOT automatically add the chromecast devices. You should have the “discovery” line by default, so just add the 2 lines below it. Ensure that your spacing is correct:

# Discover some devices automatically
discovery:
  ignore:
    - google_cast

You may need to remove them from the “Known_Devices.yaml” file as well.