Supervisor can't reach Github.com for Add-ons

Installation Home Assistant OS
1

Supervisor is unable to connect to github.com in order to find/update add-ons. Supervisor is on version 2021.04.3. The issue it laid out well here (No valid repository for https://github.com/home-assistant/addons - #75 by netjedi), but none of the DNS things they’re mentioning there are changing anything.

  1. I’m on a Home Assistant Blue
  2. I have no ad blocking, security filtering, or anything else enabled on my Eeros
  3. I’ve changed my host DNS settings to 8.8.8.8 and 1.1.1.1 and I get the same thing every time a reboot.
21-05-10 22:02:26 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/home-assistant/addons repository: Cmd('git') failed due to: exit code(128). 
cmdline: git clone -v --recursive --depth=1 --shallow-submodules --progress https://github.com/home-assistant/addons /data/addons/core.
2

This only started happening semi-recently, but I can’t remember when the last time Supervisor was updated.

3

If you are able to bypass the eero (even temporarily) - you will be able to do the update.
If you:

  1. Setup your phone to share its network via Wifi
  2. in HA, go to Supervisor → System → Host (top right) and change the WiFi details to join this
  3. Reboot Host

Then leave for around 10-15 mins, does this fix the issue (noting that your HA will pickup a new temporary IP from the phone)

After this, then (using the new temporary address from the phone or Nabucasa etc) re-set the networking and reboot again

If this works then you are experiencing the same issues that other eero users are.
(seems that something is very broken in the eero networking stack from the last update) - I have told them about it but not sure it is being diagnosed further.

What we really need is someone to packet cap from the HA box the DHCP leasing negotiations and DNS queries between a) behind the eero’s and b) not behind the eero’s

Hope this helps

4

Unfortunately, Home Assistant Blue has no WiFi, so I’m not sure I can get around the eero.

5

Actually, I was able to dust off an old Airport Express to use as a router. And your fix worked! Thank you. We’ll see if it lasts.

6

Well, it did work. Within a couple of hours of putting it back on the Eero I got the same issues again.

7

Sadly this is consistent with others. I suggest raising a ticket with eero support
(hopefully this will help it get some attention and resolve in the next eero update)

From the eero app:
Settings → Troubleshooting → E-mail Support

Reference issue entitled “Issue after last update” that was raised on 27/4 and was being actioned by “Jeffrey” at eero Customer support.

I have also pointed them in the direction of the forum and my original posts on the matter.

If I had more time I would do some packet caps of the DHCP leasing process and DNS queries from the HA end (or via an intermediate laptop running Wireshark) to compare the differences.

8

Changing my Eero DNS to 8.8.8.8 (rather than HA host) seems to have helped so far. Nslookup in the Supervisor was returning SERVFAIL for a bunch of different urls, GitHub.com included.