Cannot access ip:8123 after burn image to SD card

[Samuel_Yu]

I’m using a Raspberry Pi 3B which used to set up Home Assistant + Homebridge. So I burned a Hass.io image ( [Raspberry Pi 3 Model B and B+ 32bit] as recommended) with a new SD card. Then insert it into my Pi and power on. Then go to its IP:8123 in browser. Nothing (connection refused). Waited 30 minutes, still nothing.

Then I tried several ways try to figure out the problem. I tried a different SD card, no luck. I tried use Win32DiskImager rather than Etcher on Mac with download the image again, still nothing. Now I wonder if the image file itself is corrupted?

Could anyone help? Thank you.

[tom_l]

Is your pi connected by wifi or by Ethernet?

Can you see the pi in your router?

[Samuel_Yu]

It connected by ethernet and I can see it and ping it successfully.

[tom_l]

Do you have an HDMI display you can plug into the pi to see the boot messages?

[anon34565116]

Can your API connect to the Internet? The image assumes it has Internet access.

[Samuel_Yu]

I’ve tried connect Pi with monitor and it stopped here. Any suggestions? Thank you.

[Samuel_Yu]

It seems Pi keeps trying use wlan with ipv6, which I do not use? Is it a default setting? Any idea how to correct it? Thanks.

[tom_l]

Try performing step 4 to provide an IPv4 static IP address: https://www.home-assistant.io/getting-started/

[Samuel_Yu]

Thanks. But it not working. I’ve done a lot of searching and found quit a lot similar issues. It should not related to IPv6 or network setting. Just a bunch of case with fresh install and cannot get to web UI show up. Web UI appears not running or something blocks browser. No solid solution found so far.

[anon34565116]

Something appears to be triggering AppArmor.
I ran Hassio on Raspbian Lite for quite a while before I switched to a Home Assistant manual venv installation. I never ran into those issues.

[Samuel_Yu]

Finally! After digging around for two days. I found out the solution with this post:

Connection refused. Frontend doesn't load. Fresh install

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.

So it appears some certification expired. So this is what I do to resolve the 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 [a date after today]” for example : “date -s 2019-05-25”
5. Type “systemctl status hassos-supervisor” and it start to pull the landingpage!

Now I’m able to see the Preparing Hass.io welcome page!

[anon34565116]

The error you linked to tells me you needed to set the date and time to the current one, not one in the future.
Certificate Authorities do not issue certificates that start validity at a future date. If your machine date is too far in the past it says the certificate is not yet valid.

Setting your date to an incorrect one can cause future issues even though it fixed the current one.