Hi there.
So.
I installed HA a while ago. like, a long while. It’s been running perfectly fine ever since, until suddenly my supervisor started giving unhealthy errors. i found out ubuntu is now unsupported???
I’ve always kept up to date but now i am not able to update due to an “unhealthy” error i cannot get rid of
I need to update to fix the security issue. there are dozens of others running into these same issues, but we get told to pound sand.
Running on Ubuntu hasn’t been a ‘supported’ system for a long time.
Moral of the story: Don’t wait until there’s a security issue to get yourself up-to-date.
Your running software that is under heavy development, keep it up to date
i’ve been up-to-date. every time there was an update, i updated. it now gives me a stupid error about not running priviliged while it is definitely running privileged.
And you say ‘a long time’, yes i know! i want my house to work, and i’ve based my entire house around HA…
edited the post to clarify. i’ve always been up to date until it literally wont allow me to update.
Using any OS as a base other than Homeassistant OS or a specifically configured debian has been unsupported since May last year.
You’ve had at least seven months to move to something supported.
…why?
It’s ridiculous. Someone on the discord said only debian with no additional packages was supported. like what, am i supposed to just nuke my entire server, reinstall the OS, set-up everything all over again, just because ONE application doesnt want to support one of the most popular OS’s out there?
besides, i dont recall seeing that in the changelogs for updates. i cant move to HAOSS or whatever it is called now, because i have other things i need on my server…
You’ll have to go back to May and find the blog post about it for the ‘why’ 
. I’m not saying that it was a good decision, just that there’s been plenty of time to adapt.
Hassos can be run in a VM, as can debian.
As I said, you’ve had over half a year to consider your options and come up with a solution, ask for help to achieve it etc.
You basically have a choice now of keeping your insecure, unsupported install or taking the appropriate action to ‘upgrade’ your entire system to something supported and secure.
It’s fine to be grumpy about it, but it still needs fixing.
i dont have the option of nukjing my entire system running 30+ applications just because HA is picky about the host OS. do you realize how crazy that is?
i just got the dang thing to update after yeeting the host machine into reboot 10 times and going back to an older supervisor. no clue why that worked. but still, it says UNHEALTHY
Hey, which version of Ubuntu? I am running it on Ubuntu 20.04 via docker. I do get the Supervisor error every-time Supervisor auto-update, but running the script (using sudo) always fixed it. I am currently healthy state and latest version of both HA and Supervisor.
What is your setup like?
Yeah, which is why I didn’t suggest nuking anything 
Backup your current installation in a snapshot
Install your preferred VM hypervisor
Create a VM with either hassos or debian + homeassistant
Restore snapshot + upgrade to latest version
delete the old installation and update any port forwards / ip addresses
20.04 LTS, via docker. the script never fixes it for me.
how easy is that? i was really happy how it was running, just in docker, so i could control it via portainer etc.
there’s a lot of applications and other stuff i’ve tied into HA…
For someone running a server with 30 services, you don’t know much 
Homeassistant will still run in docker, it will just do so in a debian virtual machine. You can recreate anything you are currently doing in homeassistant in the new virtual machine.
I wouldn’t expect it to take longer than an hour all in tbh.
but why go through that hassle if you could just run it on ubuntu and be done with it… 
but hey, thanks for trying to help me. i genuinely appreciate it.
i just dont think i have the performance overhead to run a VM on this machine alongside it’s already busy life.
Update: I was just banned from the HA github for 7 days for linking this thread in the issues i created, where many others reported the same issues. great shit…
I was in the same situation several weeks ago. Basically, my fault for waiting so long to switch to Debian.
I was using Ubuntu 18.04 and the quickest fix was to upgrade to Ubuntu 20.04 (an investment of 90 minutes for an old hard drive).
That bought me some time to upgrade the old drive to an SSD and install Debian 10.
I’d like to say ‘better than late than never’ but, no, I should’ve done it sooner. 
Because you can’t run a supported installation on Ubuntu. It wouldn’t have been hassle if it had been spread across a couple of months and done in stages. Probably could have moved everything across to a debian base, or backed up your entire Ubuntu system, installed proxmox, and run your Ubuntu instance and a hassos instance in parallel and learned it all as you went and still been done with months to spare.
edited. thought i found a fix