#request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

1 messages · Page 1 of 1 (latest)

crimson latch
#

Can you run ha network info and these commands in order?

login
ping 1.1.1.1
ping ghcr.io
nslookup ghcr.io
nslookup ghcr.io 1.1.1.1
crude crown
#

Copy that

#

Took awhile to get a ping back from ghcr, and didn't get any kind of response from the nslookup

crimson latch
#

Can you share the result of all of that via screenshots/album?

crude crown
#

Well, the dog was barking so went to check, and came back and it seems to be restarted, one moment

crimson latch
#

That's just a picture of the banner. The outputs of all the commands are missing.

crude crown
#

Lemme rerun them, they all cleared out when I walked out of the room

crimson latch
#

Networking appears to work fine. Maybe it fixed itself? The restart hints towards it. Wouldn't be the first time this happens.

crude crown
#

Yeah, still stuck in a loop

crimson latch
#

You can try if running ha supervisor reapair, waiting a minute or so and then running ha host reboot fixes anything.

crude crown
crimson latch
#

I don't necessarily expect this to work if the supervisor has issues though.

crude crown
#

Yeah seems like this work around for installing on a Pi might be busted too, trying to look for the latest supervisor with the old version 🤷‍♂️

crimson latch
crude crown
#

So need to make the DNS for my router static to 1.1.1.1?

crimson latch
#

No. You an run something like this.

ha dns options --fallback=false --servers dns://8.8.8.8
ha host reboot

I'm not certain this will fix anyththing but you can try.

crude crown
#

Happy to try anything just to get started with the system lol

crimson latch
#

I'd also try to run docker pull ghcr.io/home-assistant/raspberrypi5-64-homeassistant:2024.6.4 manually. It's a bit annoying to type in though.

crude crown
#

Rebooting now lol

crimson latch
#

journalctl -ru docker.service might also have something useful to say.

crude crown
#

lol i kept mistyping the fallback one, but if its still trying to 6.2 after reboot, should i still try the docker pull

crimson latch
#

Doesn't help that the CLI language expect you to use a american keyboard layout.

#

Only if it still doesn't work.

crude crown
#

Still didnt work, same error, when running the docker pull command, it just pulled up basic info about the docker command

crimson latch
#

Maybe you have a typo.

crude crown
#

Any idea? I'm not seeing it

crimson latch
#

You have to enter login first. The ha > CLI does not understand such commands.

crude crown
#

Ahh gotcha

crimson latch
#

It will probably say the same and if it does I'm not sure what else to try right now :/