Nightmare Install!

Installation
1

Hello Everyone,

I’m a newcomer and I’ve encountered some problems while trying to install HA on my Raspberry P4.

Using the Raspberry PI Imager v1.7.4, I’ve attempted to install HA OS 10.5 (RPI 4/400) on my SD card. My LAN is connected to my BT Router which doesn’t have a firewall activated. However, during the setup process, I’ve encountered an issue.

Here’s the problem:

  • 23-08-27 19:11:37 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection

This issue seems to be recurring. Based on some research, it appears that the problem might be related to DNS or timeserver - with the installer attempting to sync with NTP servers.

However, I’m not sure about the correct commands to input into the HA command prompt to resolve this. I’ve been able to connect on the IP, so it seems to work locally.

Could anyone provide some guidance? I’ve been grappling with this for days and it feels like I’m going in circles. I’ve done this once before last year without any issues, so this is particularly frustrating.

Best
Mik - UK

2

Does your router hand out dhcp, and does it see the pi as having an ip address.

2 Likes
3

Yea my router is DHCP, and hands out the same IP as 192.168.1.103…

4

And is port 8123 open on 192.168.1.103?

And can you ping that IP address?

5

Although I think it is a dns issue, I have seen fixes in the forum. If I find I’ll post.

6

I’m seeing this in the logs :-1:
23-04-04 11:22:34 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_FAILED/ContextType.DNS_SERVER

Port open, and can Ping…

7

I am running into a similar situation on HA Core running on a Hyper-V VM and it’s been running just fine that way for the last 4 years. Before any major change I dutifully snapshot the VM first - and this time I’m glad I did!

Upgrade to OS 10.5 went fine, yet when I upgrade to 2023.8.4 the web interface never comes back up.
HA is configured for static IP, VM is responding to ping, yet no love on port 8123.

The CLI on the VM console is available, so I guess I can pull a log, however I need a little guidance how to do that and I’ll be happy to report any findings.