#Instalation

1 messages · Page 1 of 1 (latest)

gloomy ginkgo
#

Hi is it normal to get this message when first instaling HA or am I doing something wrong
2026-03-11 22:00:27.234 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2026.3.1.
2026-03-11 22:00:27.316 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/qemux86-64-homeassistant:2026.3.1: [500] failed to resolve reference "ghcr.io/home-assistant/qemux86-64-homeassistant:2026.3.1": failed to do request: Head "https://ghcr.io/v2/home-assistant/qemux86-64-homeassistant/manifests/2026.3.1": dial tcp 140.82.121.34:443: connect: network is unreachable
2026-03-11 22:00:27.316 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec

#

Its doing the same from around 10 min

severe ember
#

Some errors at the early setup are normal. Looks like a VM. How are you running it?

gloomy ginkgo
#

Oracle virtual machine

severe ember
#

Can you share its network config?

gloomy ginkgo
#

Ye let me just change language to english

severe ember
#

A common issue is using a WiFi adapter for example. Doesn't tend to work reliable.

gloomy ginkgo
#

im using ethernet card

#

@severe ember

severe ember
#

Sorry, was occupied for a minute there. That should be fine. I'd check ha network info and ha dns info but a ip was resolved..
Also monitor ha supervisor logs -vf to see if errors continue to occur.

gloomy ginkgo
#

what specificaly can I check

severe ember
#

It's more for me to check. If you have a valid ip/DNS server assigned mostly.

gloomy ginkgo
#

it does and supervisor logs are repeating the same errors that I posted

#

2026-03-11 22:30:29.246 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:landingpage to ghcr.io/home-assistant/qemux86-64-homeassistant:2026.3.1
2026-03-11 22:30:33.780 WARNING (MainThread) [supervisor.docker.manifest] Failed to connect to registry ghcr.io: Cannot connect to host ghcr.io:443 ssl:default [Connect call failed ('140.82.121.33', 443)]
2026-03-11 22:30:33.781 WARNING (MainThread) [supervisor.docker.manifest] Failed to fetch manifest: Cannot connect to host ghcr.io:443 ssl:default [Connect call failed ('140.82.121.33', 443)]
2026-03-11 22:30:33.781 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2026.3.1.
2026-03-11 22:30:33.796 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/qemux86-64-homeassistant:2026.3.1: [500] failed to resolve reference "ghcr.io/home-assistant/qemux86-64-homeassistant:2026.3.1": failed to do request: Head "https://ghcr.io/v2/home-assistant/qemux86-64-homeassistant/manifests/2026.3.1": dial tcp 140.82.121.34:443: connect: network is unreachable
2026-03-11 22:30:33.796 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec

#

and it does it over and over again

severe ember
#

I'd really like to see the network info.

#

You can also enter login and manually try something like this

nslookup ghcr.io
ping 1.1.1.1
gloomy ginkgo
#

how to get out of the supervisor logs

severe ember
#

CTRL+C.

gloomy ginkgo
#

thx

severe ember
#

Hmm. No response is weird.

gloomy ginkgo
#

I changed it to allow all and its fixed

severe ember
#

From what I know it basically makes the bridge act like a HUB rather than a switch but I'm not sure.

#

Shouldn't be necessary.

gloomy ginkgo
#

but it worked

#

idk how but it works now

severe ember
#

🤷
Anyways, glad you got it working.