Can't fetch Whoami data: Cannot connect to host services.home-assistant.io:443 ssl:default

[carusoray]

Describe the issue you are experiencing

New install on Raspberry PI 4. Used Raspberry Pi Imager. OS Version: Home. Assistant OS 12.1 Home Assistant Core: landing page

During setup, I go to the new system page http://homeassitant.local:8123 and see:

"Error installing Home Assistant"

The first related warning is:

23-04-04 10:58:29 WARNING (MainThread) [supervisor.utils.whoami] Can't fetch Whoami data: Cannot connect to host services.home-assistant.io:443 ssl:default [Try again]

System has internet connectivity and is able to ping and pinged. System is attempting to connect to internal DNS server.

Logs attached.

logs.txt

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

1. Create a new install image SSD using Raspberry PI Imager.
2. Boot the system.
3. Wait for the failure.
4. Cry...

Anything in the Supervisor logs that might be useful for us?

I can't get this to page because the system will not install.

System Health information

I can't get this to page because the system will not install.

Supervisor diagnostics

No response

Additional information

No response

[moddroid94]

Hi @carusoray ,

Seems like a bug that has been around for a while, there are some solutions in https://github.com/home-assistant/operating-system/issues/1636 and https://community.home-assistant.io/t/error-ha-installation-no-supervisor-internet-connection/674192

in short you can check if the IP and DNS server of the Pi get correctly assigned by the modem, it can be a mismatch between host date and actual date, it can be that the Pi gets an IPv6 DNS instead of an IPv4 one.

have you tried connecting a monitor to the Pi and see the console output? that way you can check the network configuration and maybe there are more info on the error.

hope it helps :)

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.