HAOS Running on TrueNAS Scale VM - Cannot access some external URLs

DaveFace · December 28, 2022, 4:33am

I have a server running TrueNAS-SCALE-22.02.3, and HAOS running on a virtual machine. Most of Home Assistant is working correctly, for example the add-on store and updates work as expected.

However when I went to install HACS I was unable to install from the URL, and after a manual install, it fails to connect to Github (as in, it errors before any input prompt with “Could not authenticate with GitHub, try again later.”)

Trying to ping google in the Terminal fails:

However if I access the VM directly, there is no issue:

The problem appears to be within Home Assistant (or how it’s accessing the network via the VM) but I’m not sure where. It has a separate IP address to the Server: Home Assistant is set to use DHCP and my Router is setting a static IP of 192.168.1.70.

DaveFace · December 28, 2022, 3:31pm

All signs point to a HA Supervisor DNS issue, which makes sense given that the VM’s CLI works just fine.

I found this closed issue from 2020 with the same sort of problem:

github.com/home-assistant/supervisor

Resolving issues with DNS server on the same machine distributed over DHCP

opened 09:54AM - 07 Feb 20 UTC

closed 01:11AM - 17 Apr 20 UTC

niklaswa

stale

**Home Assistant Core release with the issue:** > 104.3  **Home Assistant release with the issue:** >= 198 **Operating environment (HassOS/Generic):** Home Assistant (Hassio) Docker Install on Raspbian  **Supervisor logs:** ``` 20-02-07 08:24:50 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json 20-02-07 08:24:55 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:None [Try again]` 20-02-07 08:16:07 ERROR (MainThread) [hassio.store.git] Can't update https://github.com/hassio-addons/repository repo: Cmd('git') failed due to: exit code(128) cmdline: git fetch --depth=1 --update-shallow -v origin stderr: 'fatal: unable to access 'https://github.com/hassio-addons/repository/': Could not resolve host: github.com'. ``` hassio_supervisor: ``` ➜ ~ cat /etc/resolv.conf search local.hass.io nameserver 172.30.32.3 ``` hassio_dns: ``` bash-5.0# cat /etc/resolv.conf search fritz.box nameserver 127.0.0.11 options ndots:0 ``` **Description of problem:** - Home Assistant (Hassio) can't update the Home Assistant Core version, Home Assistant Addons - Hosts can't be reached via DNS - I've AdGuard as a Home Assistant Addon installed and distributed over my router's DHCP server. Everything else is working fine, Home Assistant Core itself and other devices in my network can use the AdGuards DNS server just fine After removing the Raspberry's IP from the router's DHCP server (DNS server IP) and restarting the machine, it can resolve the urls again

This could be related to Eero routers, which I have. The issue is HA incorrectly detecting the DNS nameserver from the router - and this appears to be correct, if I run HA in DHCP then it detects the Router’s IP instead of the correct DNS nameservers. But I’ve already configured HA to use a Static IP and the DNS servers:

msedge_6EtL0cVBlx

So running ha dns info shows the correct DNS servers:

fallback: true
host: 172.30.32.3
llmnr: true
locals:
- dns://1.1.1.1
- dns://1.0.0.1
mdns: true
servers: []
update_available: false
version: 2022.04.1
version_latest: 2022.04.1

But it still does not work, and the fallback suggests that something is failing?

ha dns logs suggests coredns is failing to start:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] corefile.sh: executing...
[cont-init.d] corefile.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
./run: line 5: /usr/bin/coredns: cannot execute binary file: Exec format error
./run: line 5: /usr/bin/coredns: No error information
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

But ‘no error information’ isn’t giving me much to go on.