GitHub is blocked / HACS

I have been struggling to get HACS to update. I have taken all sorts of routes to resolve this problem, but cannot find a resolution. It appears that I cannot access GitHub.

I think it is a bug so I have opened an issue. However, it would be great if someone could point me to a quick solution ot error on my part.

I was originally running the Generic x86-64 directly on the host. But I could not ping, even though I could ping I could ping the IP address successfully, but not However, I could ping from a number of other computers on my network.

To test this issue I did clean installs of a number of OS’s on the box:

As you can see, I can run ping successfully on each of these installs.
I then installed HA successfully on Proxmox and then installed Terminal. When I open Terminal and try to ping I get an error.


This is a system health report after I did a clean install of Generic x86-64.

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?


Did you upgrade the Operating System.


Steps to reproduce the issue

  1. Install Lubuntu on the host, and run ping successfully.
  2. Install (Windows) Tiny on the host, and run ping successfully.
  3. Install Proxmox on the host, create a VM following these instructions, and run ping successfully
  4. Install HA in the Proxmox VM using the instructions above, install Terminal and run ping with the error. Please note that the only add-on installed is Terminal.

In all instances, I also pinged other sites such as,, successfully. The only errors I got were for

Anything in the Supervisor logs that might be useful for us?

Filtered on GitHub
22-06-21 15:59:36 INFO (MainThread) [] Cloning add-on repository

Anything in the Host logs that might be useful for us?

Host log filtered on GitHub
[    2.033012] sof-audio-pci-intel-apl 0000:00:0e.0:        download it from

DNS Full Logs
[INFO] - 41705 "A IN udp 28 false 512" FORMERR qr,rd 28 0.036633166s
[INFO] - 9369 "A IN udp 28 false 512" FORMERR qr,rd 28 0.042024412s

System Health

version core-2022.6.6

installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.9.12
os_name Linux
os_version 5.15.45
arch x86_64
timezone Europe/Lisbon

The first thing that comes to mind is a DNS issue.
Can you ping i.ex. from the HA cli?

If you run ha resolution info what do you see? is unique from the others you are testing because only A (ipv4) queries resolve on it, there is no answer for AAAA (ipv6) ones. The reason why that matters is in my post here:
Local DNS! - #117 by CentralCommand

So in short, if you are using a DNS server that is returning something other then NOERROR for AAAA queries on then that will break A queries as well in Home Assistant containers. There should be an issue listed when you run ha resolution info if that’s the case though.

1 Like

ipv6_error true is good?

what is addon_pwned true ?

[email protected]:~$ ha resolution info
- enabled: true
  slug: dns_server_ipv6_error
- enabled: true
  slug: supervisor_trust
- enabled: true
  slug: dns_server_failure
- enabled: true
  slug: free_space
- enabled: true
  slug: core_security
- enabled: true
  slug: addon_pwned
issues: []
suggestions: []
unhealthy: []
- os
- software

That’s just saying the check is enabled. If the check was failing it would be listed under issues and it’s not.

However it looks like it’s saying you’re on an unsupported system. Which is odd because that is different then your screenshots. What is your setup? Is this supervised or HAOS?

Thanks @CentralCommand. Please see below.

@CentralCommand , the reply above was from @avd706, not @MilesAheadToo, which is me.

1 Like

Yes, I can ping,,

@CentralCommand, below is the result of running the commands you refer to in the post to which you refer.

Can you pinpoint the problem from the combination of results?

Whoops, that makes more sense. Was on my phone so only saw a small subset of the thread and didn’t notice the user change.

Nope, that all looks correct. Doesn’t seem like DNS issue is the problem. Or at least if it is I’m not sure why it would only be an issue for github. The AAAA type query is the only obvious DNS pitfall with github compared to the others I’m aware of.

Just to check, it is still broken right? Cloudflare had a bunch of outages yesterday which broke all sorts of things unexpectedly. I didn’t specifically hear that their DNS server broke but the focus was more on all the websites that got taken down because of it so idk for sure.

@CentralCommand, it is working now.

I used the commands in the link you sent me, set the Google wifi DNS to ‘Automatic’, deleted and reinstalled HACS, with all the required restarts, and so far everything seems to be working fine.