Hassio supervisor: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]

paul_price · May 30, 2020, 2:26am

Thanks for sharing this. I a a novice when it comes to understanding how docker and containers work. I installed portainer on hassio and first tried restarting the homeassistant container but it did not solve the problem. I then blindly did what you suggested and deleted/removed the homeassistant and restarted the Pi. It took a long time to reboot and I thought I had totally stuffed things up BUT when it did finally boot up (about 5 minutes) the error was gone. I don’t know how this worked but that is not important to me - all I know is it did work and didn’t break anything.

jd1900 · June 11, 2020, 12:23pm

Same error here.

Fabricio_Angeletti · August 19, 2020, 5:02pm

This bug is active.
How can I fix it?

matti · November 30, 2020, 7:24am

I changed my network configuration and devices resulting to this " error (mainthread) [supervisor.homeassistant.api] error on call http://172.30.32.1:8123/api/config: " matter.

My problem was mainly because of

custom component floureon (floor thermostats) causing problems because my IP-addresses went wrong due to device changes
My old range extender changed device MAC addresses and my DHCP with ASUS router were binded to MAC-address (how else…) so my IP-addresses were wrong and I corrected these
But my new powerline ethernet device was not refreshing DHCP IP-addresses and required a reboot to the IP addresses to be correct.

I fought with this problem for hours removing docker containers, restoring backup etc… Until I tried to reboot the new powerline device…

So in honor of old style problem solving my advice is:
a) Reboot your machines, including network adapter. And to be extra sure shutdown everything and then boot them up from top to bottom: internet-connection => routers/switches => computers/devices…
b) Check you network configurations…
c) Check your custom components…

Ridings · March 28, 2021, 6:57am

Thanks Matti, I had exactly this problem.
As per your suggestion, I turned off all of my routers, raspberry pi and powerline adaptors.
Then started everything up again.
Bingo! all was working. Error gone.

thanks!

Germo · June 3, 2021, 4:12pm

I have this issue after I tried to upgrade from 2021.5.4 to 2021.5.5
The update was not successful
I am not able to restart Hass via the gui. It will shutdown, but it never comes back.
The only way to restart Hass is to unplug the raspberrypi and to plug in again.
Supervisor is not available in Hass.

And I have no idea how to solve this. I am not a docker specialist but just a simple Hass user.

Here is some content from the log

2021-06-03 17:58:02 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /addons/core_samba/info request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
2021-06-03 17:58:02 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /addons/core_check_config/info request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
2021-06-03 17:58:02 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /addons/core_configurator/info request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
2021-06-03 17:58:02 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /addons/core_duckdns/info request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
2021-06-03 17:58:02 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved

Germo · June 3, 2021, 4:28pm

And when I check the observer I see these log entries

[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] udev.sh: executing... 
[15:41:23] INFO: Using udev information from host
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[15:41:23] INFO: Starting local supervisor watchdog...
21-06-03 15:41:27 INFO (MainThread) [__main__] Initializing Supervisor setup
21-06-03 15:41:27 INFO (MainThread) [supervisor.bootstrap] Initializing Supervisor Sentry
21-06-03 15:41:27 INFO (MainThread) [supervisor.bootstrap] Seting up coresys for machine: raspberrypi3
21-06-03 15:41:27 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attaching to Supervisor homeassistant/armv7-hassio-supervisor with version 2021.05.4
21-06-03 15:41:27 INFO (SyncWorker_0) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network
21-06-03 15:41:28 INFO (SyncWorker_0) [supervisor.docker.interface] Cleanup images: ['homeassistant/armv7-hassio-supervisor:2021.04.3']
21-06-03 15:41:30 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.INITIALIZE
21-06-03 15:41:30 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-03 15:41:30 INFO (MainThread) [__main__] Setting up Supervisor
21-06-03 15:41:31 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
21-06-03 15:41:31 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
21-06-03 15:41:32 INFO (MainThread) [supervisor.host.info] Updating local host information
21-06-03 15:41:32 INFO (MainThread) [supervisor.host.services] Updating service information
21-06-03 15:41:32 INFO (MainThread) [supervisor.host.network] Updating local network information
21-06-03 15:41:34 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-06-03 15:41:34 INFO (MainThread) [supervisor.host] Host information reload completed
21-06-03 15:41:34 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
21-06-03 15:41:34 INFO (MainThread) [supervisor.host.services] Reloading local service hassos-apparmor.service
21-06-03 15:41:34 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/armv7-hassio-dns with version 2021.04.0
21-06-03 15:41:35 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
21-06-03 15:41:35 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/armv7-hassio-audio with version 2021.04.0
21-06-03 15:41:35 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/armv7-hassio-cli with version 2021.05.1
21-06-03 15:41:35 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/armv7-hassio-observer with version 2020.10.1
21-06-03 15:41:35 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/armv7-hassio-multicast with version 2021.04.0
21-06-03 15:41:35 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-06-03 15:41:37 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/raspberrypi3-homeassistant with version 2021.5.4
21-06-03 15:41:37 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 28 Home Assistant secrets
21-06-03 15:41:37 INFO (MainThread) [supervisor.hassos] Detect Home Assistant Operating System 5.13 / BootSlot B
21-06-03 15:41:39 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
21-06-03 15:41:39 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
21-06-03 15:41:42 INFO (MainThread) [supervisor.store] Loading add-ons from store: 63 all - 63 new - 0 remove
21-06-03 15:41:42 INFO (MainThread) [supervisor.addons] Found 4 installed add-ons
21-06-03 15:41:42 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/armv7-addon-samba with version 9.3.1
21-06-03 15:41:42 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to homeassistant/armv7-addon-configurator with version 5.3.0
21-06-03 15:41:42 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/armv7-addon-duckdns with version 1.12.5
21-06-03 15:41:42 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to homeassistant/armv7-addon-check_config with version 3.7.1
21-06-03 15:41:42 INFO (MainThread) [supervisor.snapshots] Found 29 snapshot files
21-06-03 15:41:42 INFO (MainThread) [supervisor.discovery] Loaded 0 messages
21-06-03 15:41:42 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
21-06-03 15:41:42 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
21-06-03 15:41:42 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-06-03 15:41:42 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-06-03 15:41:43 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-03 15:41:43 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
21-06-03 15:41:43 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-06-03 15:41:43 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-03 15:41:43 INFO (MainThread) [__main__] Running Supervisor
21-06-03 15:41:43 INFO (MainThread) [supervisor.hassos] Rauc: B - marked slot kernel.1 as good
21-06-03 15:41:43 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
21-06-03 15:41:43 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 0 add-ons
21-06-03 15:41:43 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 2 add-ons
21-06-03 15:41:43 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_core_samba application
21-06-03 15:41:47 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on homeassistant/armv7-addon-samba with version 9.3.1
21-06-03 15:41:47 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_core_duckdns application
21-06-03 15:41:49 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/armv7-addon-duckdns with version 1.12.5
justc-envdir: fatal: unable to justc_envdir: Bad message
justc-envdir: fatal: unable to justc_envdir: Bad message
justc-envdir: fatal: unable to justc_envdir: Bad message

And the last rows are repeated until the end of the shown log.

CarlosGS · June 25, 2021, 10:37am

I have the same problem. The error stops only when disabling the NGINX plugin.

21-06-25 10:29:36 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:37 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:39 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:39 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:42 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:42 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:44 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:44 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]
21-06-25 10:29:47 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64961 ssl:default [Connect call failed ('172.30.32.1', 64961)]

My HTTP configuration:

  use_x_forwarded_for: true
  trusted_proxies:
    - 172.0.0.0/8

Started with one of the recent updates (june 2021).

Edit: It was resolved with a new update.

OmerAn · October 15, 2021, 8:43am

@CarlosGS Did you solve the problem? I am also facing the same problem.

jumo · November 19, 2021, 8:14am

same problem on supervised installation.
I tried

killing docker images,
wiping out the databases,
deactivating wireguard addon,
deactivating cameras streams,
rebooting.

It appears solved now. I’ll restart those elements one by one trying to find the culprit.

Spritzup · January 12, 2022, 5:26pm

I fixed the problem, but I believe it speaks to be a bigger issue with the Home Assistant install (or more likely, I’m out to lunch). After much searching around, and trying various fixes, the only thing that 100% fixed the issue was to add the following to the firewall rules →

-A INPUT -d 172.16.0.0/12 -j ACCEPT
-A INPUT -s 172.16.0.0/12 -j ACCEPT

Since adding this, the error has entirely disappeared and I’ve had no ill effects. The con is that it’s erased on a system restart and it once again needs to be added manually. In a nutshell, it appears that for some reason, thet internal firewall is blocking some traffic between containers. I’m not sure of the logic in doing that, especially for “approved” addons, but their must be a reason. That said, it is causing issues, so maybe it needs to be revisited?

Anyways, I hope this helps someone

~Spritz

fidelver · March 7, 2022, 2:41pm

I only noticed because my MQTT refused any connections.
Thanks to the hints above, I just had to restart the container for supervisor. It then restarted a few times because it auto-updated itself. And then I restarted the addons through the UI

to see all containers on the shell:
docker ps
then find the name of the container which has an image that is named similarly to “homeassistant/armv7-hassio-supervisor” and restart it with
docker restart 77edf8e460ff

this worked for me

livius44 · May 27, 2022, 3:51am

Very annoying issue. My fix was the following: SSH into pi4 and:
sudo docker ps -a (to see containers and type of ha install, in my case aarch64)

docker pull homeassistant/aarch64-hassio-supervisor:latest
sudo reboot now
ha core rebuild
ha supervisor repair
ha supervisor update

UI ha reboot

Hope this helps!

vdiogo · July 8, 2022, 12:48pm

You’re a life saver mate! Worked like a charm

moznik · July 8, 2022, 6:27pm

Thanks!!! That did it for me!

AgentP38 · July 10, 2022, 10:16am

Hi all,

i have the same problem. I have a hassio installation.

For me it is not possible to run docker pull comand…

What can I do?

paboman · January 13, 2023, 4:00pm

Hi, I have the same problem but I am running HA on OVA Virtual machine on a synology nas.

I am getting command not found for sudo docker ps -a in SSH terminal

any advice ? many thx

21494 · January 17, 2023, 9:49pm

I use an RPi3 and I have problems with home assistant restarting every hour irregularly. I think that the supervisor does not detect it and some watchdog trigger that restarts it. This leaves the service unavailable for a long time. I don’t know if it is a problem of hardware resources even if the load of the processor or RAM is not at 100%. Maybe it can be solved by increasing the watchdog timer for slow systems, but I don’t know how to do it.
Erros in supervisor are similar to this:
Error on call https://172.30.32.1:8123/api/states/binary_sensor.snapshots_stale: Cannot connect to host 172.30.32.1:8123

dany547 · January 30, 2023, 11:02am

There are a number of fixes for this:

first try to restart all HASS components from docker
restart your router and the machine that is hosting HASS
stop supervisor then recreate the image using the latest one
stop Home Assistant and restart Supervisior then start Home Assistant

costinr · April 17, 2023, 6:45am

Hi,

Same situation here, (error on call https://172.30.32.1:8123 - HA inaccessible nor via browser or telnet)
I’ve found this error via with “su logs” command.

It seems nothing from above advises applies to an OVA (virtualbox) installation, as I’m stuck with CLI commands inside HA console.

There is no obvious error when the virtual machine starts.

Any other steps/solutions?

Thank you,