Replies: 1 comment 1 reply
-
|
What network settings are you using in Home Assistant? (Settings > System > Network > Configure network interfaces. Try setting 8.8.8.8 and/or 1.1.1.1 there directly. If you continue to experience the problem, also share the DNS logs (Settings > System > Logs, select DNS on the top right). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, about 6 weeks ago my HAOS stopped updating, as far as I can see without any local changes. As it was getting out of date I started with backups and a fresh install of Debian 13, KVM virt-manager and HAOS 16.2. I am on starlink so the internet is quick. I am running a Asus GT-AX6000 router.
That failed during the Preparing Home Assistant phase with
2025-11-01 07:18:20.296 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/amd64-hassio-supervisor:2025.10.0: 500 Server Error for http+docker://localhost/v1.51/images/create?tag=2025.10.0&fromImage=ghcr.io%2Fhome-assistant%2Famd64-hassio-supervisor&platform=linux%2Famd64: Internal Server Error ("Get "https://ghcr.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)")After trying all sorts at home with no results I got it to run at a neigbour's house and so HAOS is up and running apparently normally, but on returning home it will still not update, and gives one of two similar errors as below:-
Looking through the logs I also see
Thinking it must be the config on my router I configured an old Asus router to (I think) identical address (10.31.13.71 netmask 255.255.255.0) and dns servers (8.8.8.8, 1.1.1.1). That allowed the updates to complete. However on reverting to the newer router (which I need to do for other reasons) any new update fails as before.
I have since been nagging away at this for weeks now, and have changed every dns flag back and forth with no success.
I have also reverted the router firmware to one two releases earlier and even loaded the latest Asuswrt-Merlin firmware. Nothing seems to make a difference except using the older router which has never failed.
I assumed this was a dns issue, but the two routers appear identical and running nslookup ghcr.io on both gives the same ip address (4.237.22.32 as a Non-authoritative answer).
So now I am well past my network skill level, and need to troubleshoot this problem.
I assume this is some problem when trying to download the update or new version.
What can I do to find out what the new router is blocking? Can I manually try and download an update or is there a way to obtain a more detailed log?
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions