Hi guys, I have a problem with my HA installation.
I’m running a Proxmox server with a VM with HA installed and for the last 2 years I hadn’t get any problem. In the last two weeks I have issue with updates and down the log.
23-11-29 13:31:23 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2023.11.3
23-11-29 13:31:23 INFO (MainThread) [supervisor.docker.interface] Updating image Package qemux86-64-homeassistant · GitHub to Package qemux86-64-homeassistant · GitHub
23-11-29 13:31:23 INFO (MainThread) [supervisor.docker.interface] Downloading docker image Package qemux86-64-homeassistant · GitHub with tag 2023.11.3.
23-11-29 13:31:38 ERROR (MainThread) [supervisor.docker.interface] Can’t install ghcr.io/home-assistant/qemux86-64-homeassistant:2023.11.3: 500 Server Error for http+docker://localhost/v1.43/images/create?tag=2023.11.3&fromImage=ghcr.io%2Fhome-assistant%2Fqemux86-64-homeassistant&platform=linux%2Famd64: Internal Server Error (“Get “https://ghcr.io/v2/”: context deadline exceeded”)
23-11-29 13:31:38 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
It seems that I can’t reach the server. I have TWO ADGUARD instances on Proxmox but both ah HA IP filtered to bypass any block. Of course I had tried to disable both AdGuard but nothing changes. I had checked the DNS on HA GUI and is fixed to 1.1.1.1. I had tried to ping www.google.com from the terminal instde HA and it’s working. I had tried to ping the server of home assistance and I get “bad port”. It’s not workin. Strange.
I had tried to update SAMBA too and get also an error:
23-11-29 13:53:33 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/amd64-addon-samba with tag 12.2.0.
23-11-29 13:54:15 ERROR (MainThread) [supervisor.docker.interface] Can't install
there is (as of today) a new supervisor-version (2023.11.6) , and this has to be installed, before you can install latest Samba (12.2.0) …
I don’t even wanna know why you have 2 ADGUARD on your proxmox … is ALL traffic on your network “routed” through your Proxmox, or is it just all DNS-queries, from all IP-devices which you find it “practical” to “direct” to your Single NIC Proxmox Device
PS: If you can’t update Supervisor through UI, then go to your Proxmox, and the HA-console, and try to update supervisor there " su update "
I have an instance of AdGuard on Proxmox and a backup instance on a raspberry pi. But they are disabled and I had changed the DNS on my router to 1.1.1.1 and 8.8.8.8.
I had tried to update the supervisor from GUI and CLI but I get:
23-11-29 15:33:56 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor failed: Can't install ghcr.io/home-assistant/amd64-hassio-supervisor:2023.11.6: 500 Server Error for http+docker://localhost/v1.43/images/create?tag=2023.11.6&fromImage=ghcr.io%2Fhome-assistant%2Famd64-hassio-supervisor&platform=linux%2Famd64: Internal Server Error ("Head "https://ghcr.io/v2/home-assistant/amd64-hassio-supervisor/manifests/2023.11.6": Get "https://ghcr.io/token?scope=repository%3Ahome-assistant%2Famd64-hassio-supervisor%3Apull&service=ghcr.io": dial tcp 140.82.121.33:443: i/o timeout (Client.Timeout exceeded while awaiting headers)")
And “frankly” many people seems to “prefer” pinging Google, Google has tons of servers around the world prepared/ready to answer … to me pinging google seems like the worse choice, unless it’s not the “nearest parts” of your connection ( local and IP-provider ) you are wondering about
I have tried “ha core update” and get an error “system in not healty - supervisor”. So I had tried “ha supervisor update” and get “error can’t fetch apparmour profile”
that is strange i can’t ping( nor get answers from nslookup) upon 140.82.121.33 from the terminal( cmd answers correct), on the other hand i don’t have 1.1.1.1, or any other Google DNS in my setup, and no problems with updates, or internal/external traffic
Beside my HA is “local”, meaning no NB, or port-forwarding/reverse proxies etc. to HA-Instance
If people is not “familiar” with a mixed local network environment, they should try to keep things “simple”
PS: If “any” modern “Home” Routers, don’t reconice an IP/domain name, it will pass it on ( to the “outer would”, And many(if not most) IP providers, will have i.e Google as a “backup/fallback/redirect” , so actually no needs for setting this specific anywhere, locally, in my opinion.
I have tried reboot from HA a couple of times and to run reboot from HA terminal. I fave tried to restart the VM a couple o times from proxmox. And here I am
Any ideas of why it says so ?, old current version ?, any “accidental” tampering anywhere ?, what does your network info in console says, can you access the UI, what does the various logs says ( In ADD-ON’s Also ! ) , any “Skipped Updates (3 dots)” or “Repairs(3 dots)” visible in Settings/System, etc
I had restored my backup via Proxmox, it’s dated yesterday. After the boot I have notifications for HA and Supervisor update. I hadn’t tried now to update, I KNOW that it will fail. I had tried in the mornign too from the backup.
HA is on 2023.11.2 and need to update to 2023.11.3
Supervisor is on 023.11.3 and neeto to update to 2023.11.6
No skipped updates, neither hidden.
In the repair section I don’t have anything, neither hidden
I just updated (before you reported this) … i did however rebooted my host first, and checked the logs, so i wouldn’t update upon “unknown errors” … bad habit i have, to secure i.e errors is not there before an upgrade
(Not restarted ! , so try again with a Reboot of your whole proxmox Host )
However the " context dealine exceeded " is doubtfully anything you can do about, but wait it out … maybe
So… maybe there is something to learn about but I’m not really sure. Yesterday I was trying to update the HA server the whole day with a tons of errors as seen above. I was on a trip and I had using the NabuCasa cloud link to get access to the HA instance. Restoring old proxmox backups hadn’t help, at the first update command I get stuck.
In the evening I’ve come home and tried again in local. I had updated my system without any issue. And I don’t know why.
Was a problem with the main server? I don’t know. Was a problem of nabu casa? Don’t know. Yesterday I had left the samba update for today because I’m on a trip. I had updated via nabu casa link and without any issue.
So I don’t have a clear solution and this is bad … it might happen again
