Installing HA for the first time on a new Raspberry Pi, which I want to run headless as I have no display/kbd handy.
Followed the instructions to flash an SD using Etcher. The RPi boots, I find its IP on my router, and I can ping it. But browsing http://homeassistant.local:8123 just gives me
# This site can’t be reached
**homeassistant.local** refused to connect.
Same if I use the IP (192.168.0.129:8123). SSH is refused as well.
Where do I start?
Can you ping the ip address?
Yes, I can ping it.
Make sure that your browser doesn’t switch to https when using the IP address.
I’ve tried every possible permutation of name and IP. It identifies to my router as “homeassistant”.
http://homeassistant.local:8123 resolves to “homeassistant.local” in the browser address bar so I don’t see any indication it’s trying to use HTTPS.
It’s always just ERR_CONNECTION_REFUSED.
This is the URL I used for the image:
https://github.com/home-assistant/operating-system/releases/download/6.1/haos_rpi4-64-6.1.img.xz
I’ve now repeated everything with the 32 bit version of HA. No difference. I can ping by IP or as homeassistant.local, but there’s nobody home when I browse to any of these:
http://homeassistant.local:8123
https://homeassistant.local:8123
http://192.168.0.129:8123
Yeah same problem with new install on 64bit 6.1 version.
I tryed and older release (5.9) and this is reached but It is stuck on “preparing home assistant” page.
Eventually succeeded with a different SD card. Clueless as to why.
What card did you use?
Did you create a fresh install of Home Assistant? I’m currently experiencing the exact same issue and I have no clue why this has happened. For me, there is an interesting quirk. The observer URL on port 4357 seems to work fine. But the UI on port 8123 doesn’t.
Doing a new install and unable to get to the URL on port 8123 but like you I can get the Observer on port 4357. Did you ever get this fixed ?
Finally got it to work. Might be obvious but i was banging my head on this for a while.
tl;dr
This is based on the device name on the network.
set the name on the router and the hostname in the device. I did it using this yours might be different. google. Name change in the router should be straight forward, different for different devices, again google.
Full version:
I have HA running as container on my raspberrypi.
I had tried to connect with homeassistant.local and raspberrypi.local
Both failed.
Had tried multiple fresh installs but didn’t work out. But didn’t want to go the route of supervisor. Have other containers i need.
Gave up and just went with the local ip everywhere i needed it.
Was messing with my router today for the some plex stuff and accidentally found that i have a device with the name of raspberrypi-2. I have two raspis 
.
Both have raspberrypi as hostname.
Guessing my router set the second one to raspberrypi-2. (the one running homeassistant)
Tried raspberrypi-2.local and it worked 
.
Jumped straight on it.
Changed the device name in my router for that raspi to homeassistant. Didn’t work.
Restarted the router. Didn’t work.
sshed into the raspi and checked the hostname. It was raspberrypi.
Changed it to homeassistant and rebooted my raspi.
Then restarted my router.
It worked 
. Finally. After more than an year.
Hope this helps.
p.s am actually not sure if its the change in the router or the device or both. But its 1:50AM here. Not messing with this anymore. Someone else can confirm this.
Also for me raspberrypi.local failed maybe since i have two. It might work for you from the start.
Also during the research, found that you can change the local domain ie the term “local” in homeassistant.local in your network to whatever you want. This also might clue you in if the above solution also is not working for you. all the best.
In my experience, it’s good to go an make a hot drink after the first boot of HA. It takes a while to sort itself out on a Pi 3. The 4357 port will be the first to respond, 8123 may take another 5+ minutes.
I had the same problem. I went back the last stable release, the .4 version. That works fine. Wait until they get the bug fixed or just stay 1 release behind the latest release in the future. I was installing on a rasp 4.