Hassio installation nightmare

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. :wink:

I went through my share of hell with HassOS as well. Here are some things I’d check:

  1. 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.

  2. 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.

  3. 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

  4. 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.

it could be an issue with your router not resolving DNS correctly, your ISP’s DNS not working at the time, or your ISP blocking the traffic to github or docker hub.

not to forget it’s still showing as a mail server… if you run the portscan now, are pop and imap still there?

You might well be right! I have a content filter here through the ISP which blocks adult sites and a few others, I hadn’t thought of it before, but it could have prevented the installation.

Works fine now it’s installed.

So that’s one more step to try if you’re having trouble - TURN OFF PORN FILTER!

check, as suggested in Hassio installation nightmare, if in trouble, always try without blockers in a private browser-window

I did try in a private window, that didn’t help. This is an ISP content filter, though that I didn’t turn off. Blocked categories:

  • Pornography & adult
  • Suicide & self harm
  • Weapons, violence, gore & hate
  • Drugs & criminal skills
  • Phishing & malware

@ Mariusthvdb yes, the mail ports are still open: