This sounds the same as ’ [Error: INFO (MainThread) [supervisor.updater] No Supervisor connectivity]’ but I have a significantly different setup.
I have had HA running on a RPi for 7 months. I am trying to setup a second as backup. I have RPi 5 with Argon Neo 5 case and 1 TB SSD. The disk was built using the RPi imager. My network is Netgear Orbi (mesh). When I connect a network cable to the new RPi I get the ‘preparing’ screen in my browser, but it fails (no supervisor connectivity). I cannot access the new system via WIFI. I have manually configured wlan0 and it seems connected to my WIFI network using a static IP address. I also reserved that address on my router. My wlan0 address is 192.168.1.239/24 but the supervisor address is 172.30.32.2 (docker?). I didn’t configure interface end0 but it has a mode of auto and an IP of 192.168.1.19/24. Any suggestions about how to address this issue or further clarification questions?
TIA!
Please refer to the requirements for installation. Hard wired. I think it is a limitation of the install scripts.
It is currently hardwired, but still no supervisor connectivity.
Post the logs. [</> formatted please]
Please explain the formatting request.
Forum post option. Preserves spacing, etc. Readability.
Preformatted text2025-06-26 17:48:38.811 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
2025-06-26 17:49:08.813 INFO (MainThread) [supervisor.updater] No Supervisor connectivity, delaying version fetch
2025-06-26 17:49:08.813 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
2025-06-26 17:49:38.814 INFO (MainThread) [supervisor.updater] No Supervisor connectivity, delaying version fetch
2025-06-26 17:49:38.815 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30secPreformatted text
That’s all that is in there?
Your sub-lans may not be transversable. 192.x vs 172.x
My mistake. It had repeated continously for quite a while. I missed this.
2025-06-26 17:58:08.864 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
2025-06-26 17:58:37.603 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2025-06-26 17:58:37.603 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2025-06-26 17:58:37.603 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2025-06-26 17:58:37.603 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2025-06-26 17:58:37.603 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2025-06-26 17:58:37.607 INFO (MainThread) [supervisor.jobs] 'CheckDNSServer.run_check' blocked from execution, no supervisor internet connection
2025-06-26 17:58:37.607 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2025-06-26 17:58:37.607 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2025-06-26 17:58:37.607 INFO (MainThread) [supervisor.jobs] 'CheckDNSServerIPv6.run_check' blocked from execution, no supervisor internet connection
2025-06-26 17:58:37.607 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disk_lifetime/system
2025-06-26 17:58:37.609 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2025-06-26 17:58:37.609 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2025-06-26 17:58:37.609 INFO (MainThread) [supervisor.jobs] 'CheckAddonPwned.run_check' blocked from execution, no supervisor internet connection
2025-06-26 17:58:37.609 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2025-06-26 17:58:37.610 INFO (MainThread) [supervisor.resolution.check] System checks complete
2025-06-26 17:58:37.610 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2025-06-26 17:58:37.628 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-06-26 17:58:37.629 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2025-06-26 17:58:37.630 WARNING (MainThread) [supervisor.jobs] 'FixupStoreExecuteReload.process_fixup' blocked from execution, no supervisor internet connection
2025-06-26 17:58:37.630 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2025-06-26 17:58:38.865 INFO (MainThread) [supervisor.updater] No Supervisor connectivity, delaying version fetch
2025-06-26 17:58:38.866 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
2025-06-26 17:59:08.870 INFO (MainThread) [supervisor.updater] No Supervisor connectivity, delaying version fetch
2025-06-26 17:59:08.870 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
2025-06-26 17:59:38.874 INFO (MainThread) [supervisor.updater] No Supervisor connectivity, delaying version fetch
2025-06-26 17:59:38.874 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
type or paste code here
Sorry about the logs. I will try to straighten them out and repost.
Looks like it is looking for IPv6 access too.
Go back, check your network, and let the packets through.
I guess that means an IPv6 gateway and nameserver? I checked my router and it only lists IPv4 addresses. I don’t see an IPv6 equivalent to 192.168.1.1
I didn’t configure any IPv6 in my other HA system.
The end0 interface does have 2 IPv6 nameservers. I could copy those addresses, but I don’t see any IPv6 gateway.
Is that the one the Supervisor is looking at for the updates it needs to fetch? Check on your console display, either on a HDMI monitor or by SSH to it.
It may be choking on DNS to get to the right repositories.
I can’t see which interface the supervisor is trying to use. Is there some command that would display that? supervisor --info doesn’t.
How do you set the global log level flag? It is currently set to warn.
The error message is ‘no connectivity’, so I don’t think that DNS is the problem. I did hookup my monitor to my other HA (which works) and it has the same supervisor address (172.30.32.2) which I think is a Docker address. It seems like Docker can’t get to the host interface, which I guess is wlan0. My working HA system has end0 disabled and nothing entered. Could it be a Docker config issue?
Worth checking.