Can't upgrade above 2022.9.7... no internet connection? Really?

Configuration
1

I am trying to go to 2022.10.3, just updated the supervisor to 2022.10.0.

Not sure that this is the correct sub-forum for this, but it is not a new install issue.

The updater is logging the following:

homeassistant.exceptions.HomeAssistantError: Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, no host internet connection

I really do have an internet connection, verified by ping to 8.8.8.8, nslookup of yahoo.com and nslookup of 8.8.8.8 and I was wireguarded into the system all day from work.

I have looked through a few threads from the past that included this error, but did not find anything that made sense or made it work.

What am I overlooking? Would really like to get this install up to date.

Here is my system info:

## System Information

version | core-2022.9.7
-- | --
installation_type | Home Assistant Supervised
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.5
os_name | Linux
os_version | 5.10.0-18-amd64
arch | x86_64
timezone | America/Chicago
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4896
Installed Version | 1.27.2
Stage | running
Available Repositories | 1119
Downloaded Repositories | 15

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Debian GNU/Linux 11 (bullseye)
-- | --
update_channel | stable
supervisor_version | supervisor-2022.10.0
agent_version | 1.2.2
docker_version | 20.10.12
disk_total | 218.1 GB
disk_used | 16.7 GB
healthy | true
supported | true
supervisor_api | ok
version_api | ok
installed_addons | Dropbox Sync (1.3.0), Duck DNS (1.15.0), File editor (5.4.1), Log Viewer (0.14.0), RPC Shutdown (2.2), WireGuard (0.7.0), SSH & Web Terminal (12.0.2), Samba share (10.0.0), TasmoAdmin (0.20.0), Glances (0.16.0), Check Home Assistant configuration (3.11.0), DHCP server (1.3.0), Network UPS Tools (0.11.0), Samba Backup (5.1.2), Portainer (2.0.0), Home Assistant Google Drive Backup (0.108.4), SDR to Home Assistant (0.1.15b), Mosquitto broker (6.1.3)

</details>

<details><summary>Dashboards</summary>

dashboards | 1
-- | --
resources | 7
views | 15
mode | storage

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | October 11, 2022 at 2:42 PM
-- | --
current_recorder_run | October 12, 2022 at 10:09 PM
estimated_db_size | 259.21 MiB
database_engine | sqlite
database_version | 3.38.5

</details>

<details><summary>Sonoff</summary>

version | 3.3.1 (b20e33c)
-- | --
cloud_online | 0 / 0
local_online | 0 / 0

</details>
2

Everyone with this issue in had dns set incorrectly or other issue

Reboot host

Go to Settings → System → Network and check those are set correctly

3

I understand that… I have rebooted the host a couple of times, have tested dns resolution and still no dice.
Can’t get more generic that the config below, have even removed my pihole as the main dns server, still will not upgrade. I really did search for the answer and tried several things.

This is a standalone host and has never had an issue with dns, have been running it for years.
I have also tested within the hassio_supervisor and homeassistant container shells… same results as below.

image
image

4

Can you still log onto Home Assistant and do you only get the “no internet” when you try to upgrade?

5

Yes, the system is working as expected other than the upgrading. I can login locally, via wireguard on the system and via a port forward for the web interface. Oh and via ssh with the ssh addon.

6

Now we are getting into deep guess at my end. Can you try upgrading from a monitor/keyboard on the Home Assistant host? I am guessing that the upgrade can’t be done over a VPN? (I haven tried it).

7

I have tried the upgrade from the local network… This is a supervised install, I am not sure how I would go about doing the upgrade from the host as the host video does not show or run the web client. I do see that there is the ha os update option from the cli. I would want to be home with the machine before I fired that one off.

I did find this interesting… dig is using an internal nameserver that is the IP address for the addon_core_duckdns. But, it still resolves correctly.
image

8

Did you find a resolution? I have the exact same issue.

9

Nope, and it really pissed me off and I went to a bare metal install running Home Assistant OS. Gave up on the supervised install.

10

Same problem I had.

I managed to disable the host_internet check: ignoring the internet_host condition.

ha jobs options --ignore-conditions internet_host

The network info still the same, but I was able to install all addons I have:

➜  ~ ha network info | grep internet
host_internet: false
supervisor_internet: true

and to reset it back to normal, after addon update completed:

ha jobs reset

I hope it helps…