Update of Home assistant or addons failed - system not healthy

Installation Home Assistant OS
,
24

@badabing
I have exactly the same setup and issue you describe. +1

25

Absolutely, I spend hours to figure out why my system thinks it might be unhealthy instead of fixing it when it is really unhealthy.

26

GNU Debian and latest version of Docker installed two weeks ago after my Raspian install would no longer run Supervisor reliably. Supervisor would stop after 5 mins to 1 day with no error.
Today I see supervisor has no access to the internet and getting similar messages in log. Reboot, update and upgrade reboot, remove WG and DuckDNS reboot, add loopback to etc/host reboot all failed. Tried restarting Docker container for Supervisor and have a clean log file. However, after a reboot i get

19-02-14 10:12:53 WARNING (MainThread) [supervisor.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1125)')]
19-02-14 10:12:53 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection
19-02-14 10:12:53 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 6 Home Assistant secrets
19-02-14 10:12:53 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/raspberrypi4-homeassistant with version 2021.3.4
19-02-14 10:12:53 INFO (MainThread) [supervisor.hassos] No Home Assistant Operating System found
19-02-14 10:12:54 WARNING (MainThread) [supervisor.jobs] 'StoreManager.update_repositories' blocked from execution, no supervisor internet connection
27

Your time is wrong.
It thinks the certificate is in the future so won’t connect to the server.
Set your time.

28

@dtalens, thanks!
It worked for me.

sudo docker restart hassio_supervisor

29

Yes, this solved the problem for me.

Followed the instructions to update from here: Install Docker Engine on Debian | Docker Documentation (However I did not apply uninstall)

30

I have same message for latest update (Oct.) and I’m running my HA on RASP4
Any advice?

1 Like
31

Following an advice online I did this via SSH and it solved the problem. It took a while to run…
ha su repair
ha core rebuild
ha host reboot

9 Likes
32

I have debian, rebooting doesn’t help me, although everything worked before. To date, I still can’t update
{
“home_assistant”: {
“installation_type”: “Home Assistant Supervised”,
“version”: “2022.9.6”,
“dev”: false,
“hassio”: true,
“virtualenv”: false,
“python_version”: “3.10.5”,
“docker”: true,
“arch”: “armv7l”,
“timezone”: “Europe/Moscow”,
“os_name”: “Linux”,
“os_version”: “5.10.60-v7l+”,
“supervisor”: “2022.10.0”,
“host_os”: “Raspbian GNU/Linux 10 (buster)”,
“docker_version”: “20.10.18”,
“chassis”: “”,
“run_as_root”: true
}Снимок1

Снимок2
Снимок2992×56 8.81 KB

33

I have this same configuration, and the same issue… from the moment I updated to supervisor version 2022.10.0. Tried other ideas on this page. Everything is up to date, including docker, and no other problems or errors in the configuration are noticeable.

… just figured out it was complaining (for the first time) about other containers that I run (in my case just Portainer). I removed that container and the updates are working… a bit annoying really, but ok.

1 Like
34

Thanks, works for me! Good job figuring this out!
Stopping portainer was actually enough for me to enable updates.

sudo docker stop portainer

Then refresh the Updates page in HA, until you can update something.
Then don’t forget to start portainer again:

sudo docker start portainer

You could do this as soon as the last update has been started…

2 Likes
35

This also worked for me.
I was not able to install Z-Wave JS Addon or any Addons at all.
But now it is working.
Thanks

36

Thank you! That helped!

37

Topicstarter @Freestila!
Set solved status to finded answer!
@plaksnor finded a solution.
But I preferred to remove the Portainer:

sudo docker stop portainer
sudo docker rm portainer
sudo reboot
2 Likes
38

Why is it considered ok to eliminate Portainer as an acceptable solution?
It sounds like a bug to me.

1 Like
39

No, it’s not a bug.

1 Like
40

Saw this today after being stopped from further updates since 10.1, complaining about unhealthy system. I’m glad I found it and was able to stop portainer and remove it. Performed updates to 10.5 like a charm. Next step to add back the portainer to docker. Running on a debian VM on proxmox. Thank you

41

Super!! This worked for me. Thank for your help!

1 Like
42

Yup!!! Portainer is problem. Just remove is not thing error!
Thank you!

1 Like
43

My issue was not related to portainer although I was also running it. I stopped and removed it but still continued to face the issue. My issue was resolved by running the following commands - I dont know what do they do, but answers to a similar question on reddit suggested to do so:

ha su repair
ha core rebuild
ha host reboot
3 Likes