#Sorry if this looks like a repeat post,
muted gust
I'm connectiong via ssh: homeassistant.local. At leawst mdns is working.
oblique ridge
After executing
ha dns options --servers dns://192.168.1.1
the error message has changed. When I try to ha super update now, it says:
Error: Abort update because of an issue with AppArmor: Can't fetch AppArmor profile https://version.home-assistant.io/apparmor_stable.txt: Cannot connect to host version.home-assistant.io:443 ssl:default [Try again]
If I "Try again" I get the original error message:
Error: Update of Supervisor failed: Can't install ghcr.io/home-assistant/amd64-hassio-supervisor:2023.12.0: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=2023.12.0&fromImage=ghcr.io%2Fhome-assistant%2Famd64-hassio-supervisor&platform=linux%2Famd64: Internal Server Error ("Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io: no such host")
muted gust
➜ ~ ha core check
Processing... Done.
Post "http://supervisor/core/check": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
umbral gulch
I'm connectiong via ssh: homeassistant.local. At leawst mdns is working.
This thread is about KDM's problem, not yours 😉
umbral gulch
After executing
ha dns options --servers dns://192.168.1.1
the error message has...
Try ha dns options --server dns://8.8.8.8
oblique ridge
I think it has to be "--servers" but yeah, i tried that, too. Same message abotu inability to lookup ghcr.io. Thanks.
oblique ridge
HAHA! I never thought of adjusting the DNS setting in the GUI! Why do I always do these things the hard way?