Worth checking, but yes.
Perhaps look at how you have your network setup. For example, perhaps you have a separate ip range for your wireless devices (like 192.168.1.x), and maybe they aren’t setup to allow communications between them?
Are you using a wired or wireless device while attempting to access http://192.168.0.83:8123 ? If you’re trying wireless, try from a wired device.
Also, do you have any other networked devices on your network that you use as “servers” of some sort (to confirm that your modem or switch isn’t blocking communications)?
Nothing too unusual, both wired and wireless are local (192.168.0.x). I’m using a mesh wifi, but that shouldn’t make a difference, there’s only one router and so only one DHCP server. It’s currently plugged straight into the router.
I’ve tried as wired and wireless devices to access, no difference.
I’m really hoping it’s something simple I’ve overlooked…
Have you taken a few minutes to hook it up to a monitor to see what the screen shows? Sounds like it is probably hung with an error.
might be worth checking if its a Safari issue. Try Chrome? Firefox. and use a private window to prevent any blockers from interacting.
Also, did you try the App? See if it recognizes any Homeassistants?
Can’t connect with Safari, Edge, Chrome nor Firefox. So it’s not a PC or Mac issue. Sadly, the Home Assistant app won’t work until Hassio is installed with a password etc.
It’s very, very strange. The only thing I can think of is it’s either a faulty Pi, (but it was brand new and it works with Raspbian). Or somehow there’s a major flaw in those images (32 and 64bit). I have downloaded it again, just in case there was any corruption; still doesn’t work 
How long have you waited after turning it on for the first time after flashing the card?
He mentioned that.
Good point, missed that.
Try nmap and see what ports are open?
Good idea nickrout - I don’t have nmap, but ran a portscan through Network Utility and IP Scanner Home, they both came up the same:
Not sure if this helps…?
I don’t know why port 80, 110, 143, 993, and 995 would be open. Those services don’t run on hassio…
Yep, you have the scanner pointed at a mail server by the look of those ports.
At last - SUCCESS! I mamboed to get this installed by going to my brother’s house, so I assume it had something to do with my router. Either way, it works fine at mine now and the 8123 port, crucially, is open.
Thank you to EVERYONE for helping, perhaps this process might be of use for someone in the future!
cAPS
But what exactly was the process that fixed it? I can’t see how “going to your brother’s house” is a well documented procedure. 
I went through my share of hell with HassOS as well. Here are some things I’d check:
-
Your power source. Make sure it’s 5v and 2.5 + amps. Don’t use a smart phone or tablet charger; the power feed is not consistent enough and causes issues. Use a proper Pi power source.
-
Check your microSD card. I was using a cheap 64GB card and it was not working well. Make sure its a quality high speed card from a reputable maker.
-
If you can ping to your HassOS install, delete your cache and cookies in your browser. Make sure that you don’t have any password saved in your browser for HassOS
-
User a static or reserved IP address.
In terms of how long it takes to install HassOS, you should look at about 5-10 minutes for it become pingable, and another 10-20 minutes for it to be accessible through a browser.
If it is taking hours for HassOS to install and/or load, I suspect that your SDcard or power source is bad.
1 Like
And useless for anyone who doesn’t have a brother.
1 Like
Sorry if I didn’t make it clear, I took the Pi to another house and managed to connect through his router. So it was most likely my router that was somehow blocking the 8123 port. Once it was installed at his house, I took it home and it then worked on the original ip address as it should.
I have no idea why the 8123 port wasn’t visible, but as the portscan shows, it wasn’t there. And even with a new Pi, various quality SD cards, an official 2.5A charger and trying from various browsers/platforms, I was still getting nowhere.
If it helps, I am using a Sky Broadband router, as I’m based in the UK. It’s not very flexible, but there’s no reason why it shouldn’t have worked.
Thank you again, everyone, for the time you’ve spent to help me troubleshoot.
That’s not even possible. Your router doesn’t block internal ports.
It sounds like it never finished downloading the docker images while it was at your house which has nothing to do with ports on the router
Because the docker container wasn’t running that listens on that port.
Still very strange as I attempted it many times, as detailed.
I can’t see how it couldn’t have downloaded, I left it overnight on one try and on another I left it for 24hrs and many times for shorter periods. My broadband is fair at 16mbps. The only thing I didn’t try is using wireless, as I had it plugged directly in the router.