Connection refused. Frontend doesn't load. Fresh install

Configuration
1

Hi guys,
I’m having a breakdown here, really.
My entire house is connected via HassIO and the SD card just broke magically yesterday. It won’t read anymore. We’re in the dark now basically and I have no backup.
Sound great, no? It gets better:
I purchased a brandnew 8GB SanDisk SD Card yesterday and tried flashing HassOS onto it like the instructions said and put it into my RPi3.
I waited for hours and nothing came up. Upon finding the DHCP IP of my RPi, I was able to ping it, but when trying to access it with IP:8132, it just gives “Connection Refused” and that’s it. I’ve tried flashing (HassOS x86 and x64) it on varios computers, Laptops. I even tried acessing it from various browsers on different PCs. Nothing. I also tried ResinOS 1.3 and 1.2. It starts up and … Nothing. Connection Refused. I gave it plenty of time. Hours.
I plugged a TV onto the RPi3 to view the output. With ResinOS there’s only a white screen with the HassIO logo on it, but with HassOS I see Linux loading everything correctly and setting up ethernet links as it should. Nothing fails. After starting up, I hooked a keyboard up and tried restarting various services, but everything fails with “HTTP failed - dial tcp: connection refused”.
I have no bad internet at all (40Mb/s) and I even tried pinging things with HassOS and it reportet it “alive”.

I don’t know what to do. It’s a nightmare. These are FRESH installs. It worked on the previous card beautifully.
I tried setting the IP fixed where the old install was and the IP even shows up at the address that I configured, but also gives Connection Refused.

I’m sitting here like 10 hours straight now. I wish I were joking. I begun 19:00, now it’s 05:00 and still nothing. The entire home is dark, there’s literally no water (since that was also controlled by it) and I can’t anymore. I know, it was a dumb design, but now I need help :confused:

TLDR: Freshly new install won’t load frontend. Shows connection refused. Tried flashing HassOS and ResinOS. Tried various PCs and Browsers. TV hooked up on RPi shows “HTTP failed - dial tcp: Connection refused” for every command.

TV Output attached:

20181012_044129
20181012_0441292851×1603 1.81 MB

Thanks in advance for any clue.

2 Likes
2

thats the first thing I noticed… If this is a Hassio image it should be ip:8123

3

It was 8123, not 8192. I’m tired. Sorry. It doesn’t work.

4

I guessed you might be tired, that’s why I mentioned the port just in case it was lack of sleep causing you to miss it.
Have you tried installing a standard distro (like raspbian) and just check that you can get that to boot all the way to the desktop? New card does not always = good working card.

Also have you tried connecting from other devices (laptop/tablet/phone) to the Hassio install just to make sure its nothing funky at your PC end.

5

After digging one more hour I looked into supervisor, because 172.30.32.2 is the supervisor, someoe somewhere said.
I typed in the console as root: systemctl status hassos-supervisor and saw that it was throwing errors like: “https://docker… blabla… Certificate has expired or is not yet valid. Cannot install landingpage. Retrying in 60 secs”.
To me “has expired or is not yet valid” seems that the time was wrong and I adjusted it fiddling around with date +%Y%m%d -s "10120000" to set the 12th October 2018 (That command didn’t make any sense, but anyways).
As soon as I typed that, the LAN begun to blink downloading stuff and the frontend welcomed me setting up Home Assistant.

I think HA should display some basic HTML pages showing the users errors like those (Where did errors occur, which errors, etc). Damn, I spent 11 hours on that.

I probably go to sleep now.

And thanks @allan for your help too.

EDIT: To clarify, you can get root access using following guide:
First, log in as “root” and a blank password
Then, the cursor should display something like "hassio > "
Then, type in “login” and wait a bit, it should take you to the root accout. You easily know this, if the cursor has a “#” before it.

EDIT:

1 Like
6

And the ultimate lesson here should be…

Make Backups of your SD Card!

When I was running on a Pi I would backup after every tested working major config change and/or before a HA update.

7

I think I have learned that now.

And I’ve just noticed something: The “date” command was just a fancy fix. Pulling the plug and then powering the RPi back on made it loose the time again, and thus I can’t download AddOns and stuff, because it will give that certificate error.
The router time is correct, so it should push the time from it, but it doesn’t. RPi says 28 january, and we’re in the 12th october.

I’m looking for a fix for that, because adjusting that thing everytime won’t do it.

Is there a way to enable/change a NTP server on HassOS?

8

I assumed that was already in place as I have never set the time on my Pi3 running a HassOS install and its always been right so far…

9

just had a quick look over on github as the HassOS repo and I might be wrong but NTP is there and looks to be using…

server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
server 3.pool.ntp.org iburst

Perhaps its having an issue resolving those names or connecting to NTP through your router/firewall?

10

Did you ever fix this?

Having trouble with RPi 3 B+

2 Likes
11

I got the same error message.

My problem/fix is that I use multiple routers and subnet. When I modified the port forward in the first ruter. It resulted in the error message “Connection refused” when trying new install on a Pie with hassio.

For a old setup running hassio on a Pie 3, the access was as normal, but my ruter setup was preventing me from doing a update from hassio.

When I tested both of my Pies on the first ruter, every thing workd fine.

I can now move both of my Pies and just setup the port forwarding propperly again.

Hope this make any sens, or give you some ide for more troubleshooting.

1 Like
12

How did you connect using the root account. I get a connection refused on that too.
@Valentino_Stillhardt

13

You must physically connect a screen/keyboard/mice to your RPi and access it from there, that way you can log in as root with no additional steps, such as certificates and shite.

14

Thanks for the quick response.

I have connected a screen and its blank for me.

15

No problem :slight_smile:

You must reboot the RPi with the screen plugged in in order for it to “initialize” the screen.

16

Thanks, that helped. I can see the screen now. I see a “Welcome to HassOS” hassio login:
I entered root and hit enter and I did not see any response for a long time but I now finally can see the hassio prompt. Thank @Valentino_Stillhardt for your help.

17

I think you need to have access to the internet.
Mine got the same problem as yours, it turns out that my router is blocking access to the internet. After I allow it to reach the internet, I start to get the “Preparing Hass.io” page.

18

Thank you! This solution saved my day!

Here is my steps to correct the same problem.

  1. Connect Raspberry Pi with HDMI monitor and USB keyboard
  2. Login with root
  3. Type “login” and it will show prompt#
  4. Type “date -s [current date or after]” for example : “date -s 2019-05-25”
  5. Type “systemctl status hassos-supervisor” and it start to pull the landingpage!
2 Likes
19

Do you mean Snapshots? If not what is your procedure to back up the SD Card?

20

no, not snapshots. i don’t use hassio so I don’t have snapshots available.

I think SD card backups are only possible if you don’t use hassio. i’ve heard that is because the file system isn’t compatible with most backup software.

Someone who uses hassio might be able to help you out more on that side.

Otherwise i just used Win32DiskImager on my windows machine and create an image of the SD card.

Either way, a regular SD card backup or snapshot is extremely important. Or even the minimum of just copying your config directory contents to a safe location off of your HA machine will be a huge help in case of a failure.