Cannot connect to host version.home-assistant.io:443

jordy55 · February 9, 2020, 7:57pm

I currently have the problem that my home assistant cannot reach the home assistant versions page.

I have already read several posts, but with them the problem is that home assistant cannot update. With me the update card is not there at all?

This is my logging when i reload the HassIO supervisor:

20-02-09 19:49:17 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-02-09 19:49:22 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]

When i open the link wich is provided in the logging then i see the JSON file.
What i’ve already done is restart home assistant completely. Also shutdown all addons.

I also deleted all backups to free up any space. But according to the system, only 6.4% has been used. I have a 64 GB card in it. So this should not be the problem either.

Maybe 1 of you has an answer for this.

jordy55 · February 10, 2020, 8:09am

In addition to this, I also saw the following happen this morning.

20-02-10 07:29:54 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-02-10 07:29:59 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'.
20-02-10 07:29:59 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-10 07:29:59 ERROR (MainThread) [hassio.store.git] Can't update https://github.com/danielwelch/hassio-zigbee2mqtt 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/danielwelch/hassio-zigbee2mqtt/': Could not resolve host: github.com'.
20-02-10 07:29:59 ERROR (MainThread) [hassio.store.git] Can't update https://github.com/home-assistant/hassio-addons 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/home-assistant/hassio-addons/': Could not resolve host: github.com'.
20-02-10 07:30:00 INFO (MainThread) [hassio.store] Load add-ons from store: 64 all - 0 new - 0 remove

I have the feeling that something is being blocked / blocked somewhere. I run Pi-hole on home assistant. Could this be the cause?

blafasel · February 14, 2020, 11:38am

I have the exact same problem.
It’s interesting, that I can curl https://version.home-assistant.io/stable.json successfully via ssh on my pi.
And I had this problem before. I solved it by manually downloading the latest update via cli.

But apparently I just solved it by enabling “Listen on all interfaces, permit all origins” in the Pi-Hole addon (under Settings -> DNS).

branitelj91 · February 14, 2020, 2:02pm

I have no Pi-Hole installed, still I have issue in update.

Any idea ?

jordy55 · February 14, 2020, 2:18pm

So I did the following.
Logged in to my router and set the secondary DNS to 1.1.1.1. This worked for me. Now I’m getting al the updates so apparently Pi-Hole did blocked the updates.

Georg · February 16, 2020, 8:51am

Have you tried this instruction? → https://github.com/home-assistant/operating-system/blob/a592fc986610fac9dbaec96f514ee616c1a44d17/Documentation/network.md#static-ip

I was having an issue with the exact same symptoms and that instruction did help me.

jeepotvin · February 20, 2020, 8:14pm

Woah! This worked for me! Thanks.

blafasel · February 21, 2020, 10:58am

Glad I could help
Just for the record, it also works with Listen on all interfaces (better if your Pi-Hole is not firewalled).
It did not work for me with Listen only on interface eth0.

dave-castle · March 4, 2020, 6:45pm

any idea how to fix this error within adguard?

holoduke · March 9, 2020, 8:07am

I have the same issue.
But i have no pihole. I had this as well during installation. Then it went through after 20 retries.
Now its back again

[supervisor.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]

dave-castle · March 11, 2020, 1:20pm

fixed for me with a 2nd static DNS server!

github.com

home-assistant/operating-system/blob/a592fc986610fac9dbaec96f514ee616c1a44d17/Documentation/network.md#static-ip

# Network

## Configure Network
HassOS uses NetworkManager to control the host network. In future releases, you will be able to set up the configuration using the API/UI. Currently only a manual configuration using NetworkManager connection files is supported. Without a configuration file, the device will use DHCP by default. These network connection files can be placed on a USB drive and imported to the host as described in [Configuration][configuration-usb].

## Configuration Examples

You can read the [Official Manual][keyfile] or find many configuration examples across the internet. The system is read-only, if you don't want the IP address to change on every boot, you should set the UUID property with a generic [UUID4][uuid]. Inside `\CONFIG\network\` on the USB or SD, create a file called `my-network` and add the appropriate contents below:

### Default

We have a preinstalled connection profile:

```ini
[connection]
id=my-network
uuid=f62bf7c2-e565-49ff-bbfc-a4cf791e6add
type=802-3-ethernet

[ipv4]

This file has been truncated. show original

niro1987 · March 27, 2020, 10:41pm

I can confirm this fix has worked for me. I’ve used the nmcli instructions to update the ipv4.dns.
Originally I had the Hassio’s own IP address set as the single DNS because I’m using AdGuard, by adding 1.1.1.1 to the ipv4.dns and rebooting the host the issue was resolved!.

zoltant7 · July 2, 2020, 2:00pm

Had the same issue when I upgraded Hassio 0.111 to 0.112. The Supervisor RELOAD did not helped, HAService Restart neither. But a complete HASSIO REBOOT did the trick.

Sokratz · October 12, 2020, 7:31pm

Thanks. fixed my install

cggaldes · November 25, 2020, 10:02am

Thanks for this one

Does this make a PiHole vulnerable in any way? Seeing as the traffic flow is coming from a container it’s probably a necessity.

Perhaps a feature request in PiHole to provide an allow list under the Listen on all interfaces, permit all origins would help to keep a secure and minimalist configuration.