this post was submitted on 24 Apr 2024
15 points (94.1% liked)

homeassistant

12025 readers
126 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago
MODERATORS
GreatAlbatross@feddit.uk
15
Attempting to use Home Assistant OS (lemmy.world)
submitted 6 months ago by captainlezbian@lemmy.world to c/homeassistant@lemmy.world
21 comments fedilink hide all child comments
 

But I’ve been getting this error:

[supervisor.docker.interface] Can't install ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.4.4: 500 Server Error for http+docker://localhost/v1.44/images/create?tag=2024.4.4&fromImage=ghcr.io%2Fhome-assistant%2Fgeneric-x86-64-homeassistant&platform=linux%2Famd64: Internal Server Error ("Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)") [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec

I’ve tried changing DNS, but it didn’t help and I seem to get no other helpful results from searching. If anyone has any suggestions I’d appreciate it as this seems to be something my home could benefit from but it’s just not loading beyond the CLI

you are viewing a single comment's thread
view the rest of the comments
[–] redcalcium@lemmy.institute 1 points 6 months ago* (last edited 6 months ago) (1 children)

Is this the tutorial you followed? https://www.home-assistant.io/installation/generic-x86-64

On which step did you encounter the error? The step where the home assistant os already written to the target disk and you're told to restart the system with usb stick unplugged?

http error 500 when downloading the container image might be a temporary error on github docker repo side. Try restarting the device and see if the error persist.

[–] captainlezbian@lemmy.world 1 points 6 months ago (1 children)

Yes, I was able to access it from my desktop while it still says the error (initial attempt was Sunday, also attempted Tuesday)

[–] redcalcium@lemmy.institute 2 points 6 months ago (1 children)

Could be cdn issue. Try updating your router setting to use cloudflare dns or google dns. Some people fixed similar issue by using those dns servers.

[–] captainlezbian@lemmy.world 1 points 6 months ago

In my router or on the machine? I’ve tried on the machine, but it didn’t work