HAOS is installed and running locally (at least apparently, not sure how much of it is running but I have a Ha> prompt) but remote access via lan says error:
supervisor.docker.interface] Can't install ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.11.3: 500 Server Error for http+docker://localhost/v1.47/images/create?tag=2024.11.3&fromImage=ghcr.io%2Fhome-assistant%2Fgeneric-x86-64-homeassistant&platform=linux%2Famd64: Internal Server Error ("Get "https://ghcr.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)")
This is on a miniPC with AMD cpu, 8GB/256GB.
I simply balena etched the image I downloaded to the SSD and removed secure boot from the BIOS.
Here is where I got the image: https://github.com/home-assistant/operating-system/releases/download/13.2/haos_generic-x86-64-13.2.img.xz
The PC had normal network access prior and the error above is what’s displayed on a second PC when I put homeassistant.local:8123 in the URL box.
The log is quite long and I can post it entirely if necessary. Before this error, there is also an error about the supervisor:
[supervisor.supervisor] Update of Supervisor failed: Can't install ghcr.io/home-assistant/amd64-hassio-supervisor:2024.11.4: 500 Server Error for http+docker://localhost/v1.47/images/create?tag=2024.11.4&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/2024.11.4": Get "https://ghcr.io/token?scope=repository%3Ahome-assistant%2Famd64-hassio-supervisor%3Apull&service=ghcr.io": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)")
[supervisor.core] Can't update Supervisor! This will break some Add-ons or affect future versions of Home Assistant!
I have access to the machine directly (keyboard and monitor attached), as I said I have a Ha> prompt and I looked at the help available host --help but did not find anything that would let me change the network settings.
My network router/access point is using the DNS provided by my ISP (Cox) but I am on the home network so I don’t think that DNS should affect operations locally.
When I try to get to that site (https://ghcr.io/v2/) directly from the browser I do get a permission error ({"errors":[{"code":"UNAUTHORIZED","message":"authentication required"}]}) but the browser does find the site.
I initially tried running HA Core under WSL on my main Windows PC (which is always on) and while it worked (I did not actually connect any of my home IoT stuff, but the user interface seemed to be fully working at the time), I could not fgure out how to start/restart everything (including networking) automatically in case of power interruption, so I have installed HAOS directly on a mini PC I bought for that purpose (HP EliteDesk 705 G3)
Problem is fixed. This post was the clue but there was still an issue with the post linked above: first-time-install-raspberry-pi-4
In articular, in the paragraph:
Change containers by using the command login. This should bring you to a different # CLI. The command nmcli con will display the internet connections, take note of the first entry in green and its exact name: “Supervisor eth0”. Now enter nmcli con edit “Supervisor eth0” to enter the nmcli environment. Enter the command print and it will show a large output, and if your screen is high enough resolution you should make out the ipv4.dns value. Enter the command remove ipv4.dns in order to remove all entries from the ipv4.dns value. Then use the command set ipv4.dns 1.1.1.1 to add a correct DNS address to the network configuration, using 1.1.1.1 or the DNS address in your router’s settings. Enter print again and confirm the ipv4.dns value is correct. Finally enter save and quit to apply the changes and leave the nmcli container.
Before the changes take effect, we need to restart home assistant. Enter the command exit to be returned to a login prompt, and use “root” again to enter the ha > CLI we were in before. Once you’re here, enter the command host restart and then wait for several minutes for your device to reboot. This command will not give any immediate output, but the device will eventually restart.
The issue is that my network interface was not eth0. From the host shell, I used nmcli connection and it showed that my interface was enp1s0 instead of eth0, so I replaced eth0 with enp1s0 in the instructions and it worked.
