HassOS frontend no longer available after latest update

I recently update to whatever the latest HassOS release was (is) and the web GUI is no longer accessible. I’ve gone deep down the rabbit hole trying to debug and the things I can see so far are:

  1. According to the observer the Supervisor is connected
  2. I can access the cli interface by connecting my raspi through hdmi
  3. Nothing about my network has changed so theoretically my IP reservations and port forwards should all be as they were the last time HA was operational

I’ve tried different usb cables, power adapters, Ethernet cords. I’ve done hard reboots, I’ve let the machine cool down, I’ve tried rolling back versions of Core through cli (it said successfully, but who knows)

My first thought was maybe the SD card has gone bad, but I’ve checked it on my windows machine and everything appears as normal. I’d really love to not have to reformat as my last full backup is from months ago and I had things in a really good spot since then.

Appreciate any help!

Can you ping your Home Assistant server’s IP address from your PC?
I would also try pinging your router an your PC from the Home Assistant CLI. Type login at the ha > prompt to get to a real shell.
You should also be able to print your network configuration from the CLI. Check if it is correct.
See if you have any errors in your logs (ha core logs and ha supervisor logs).

I can ping both the HA server from my PC and my PC from the CLI successfully.

The network info from the CLI returned the correct eth0 interface data that I would expect (or at least the same data I had in there this entire time pre and post issue).

Nothing looks concerning (to me) from the ha core logs, and the only red text warnings I’m seeing in the supervisor logs refer to supervisor.addons.validate issues (two addons that I’m not even using, and two that I’ve installed but not set up).

Thank you for your reply, I really hope there’s a solution to be found :slight_smile:

Apologies to anyone experiencing similar issues and finds this post. I was not able to track down the cause or direct solution to this issue.

What I ended up doing was:

  1. connecting the hassOS SD card to my Windows Machine
  2. downloaded this linux filesystem reader
  3. Using that reader I then copied over the entire config/ directory (in my case it was labeled ‘homeassistant’. I might have done that myself way back upon initial setup?)
  4. Reformatted and flashed my SD card with the latest hassOS image (per the official instruction page)
  5. Set up the fresh install as if I was going to start from scratch
  6. Installed samba share add-on (Windows wasn’t natively set up to handle this! I had to enable 1.0 manually after 20 minutes of banging my head against the keyboard)
  7. Copied over my ‘recovered’ config/ directory on top of the fresh install
  8. Rebooted my pi and everything came back great!

I had no idea about the ‘Check Config’ add-on available through the Supervisor. I will absolutely be using this before any future upgrades. I will also be better about doing full backups through the GUI from now on.

And take your backups off your SD

Copying your backups to another location

You often need a backup in case your system has crashed. If you only store them on the crashed device, you won’t be able to access them easily. We recommend that you manually copy them from /backup to another machine on occasion. Or even better, create an automation to handle that, or make use of one of the following add-ons:

Yes, great point!

I briefly looked at the Google Drive Backup method, but after seeing the setup process I wasn’t sure how secure it was (just my gut, might be totally unfounded). Is there one from your list that you recommend over the others?

I use google drive backup myself.