search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
4.8k stars 959 forks source link

Cannot connect to host 172.30.32.1:8123 (Fails to boot sometimes) #224

Closed Fusseldieb closed 5 years ago

Fusseldieb commented 5 years ago

Hi, I've been experiencing this bug since I first knew Home Assistant (and it's still there with 0.80.3), so I'm not so sure if this can be resolved in HassOS, but following does happen sometimes when I restart Home Assistant:

Sometimes when I restart Home Assistant, it doesn't come up again. The page says Connection Refused and that's it. The first time this happened to me I almost freaked out, but now I know that a simple router restart fixes it. It's strange, Today it happened to me again and I wanted some concrete proof of what is happening so that I can submit this here.

So, the SSH Server still runs normally during this time, so there it is where it errored out: (Log was collected while HA was attempting to restart)

core-ssh:~# hassio su logs
Error decoding json invalid character '\x1b' looking for beginning of value: 18-10-21 06:26:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 06:56:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 07:26:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 07:56:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 08:26:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 08:43:56 INFO (SyncWorker_9) [hassio.docker.interface] Stop homeassistant/armhf-addon-mosquitto Docker application
18-10-21 08:43:57 INFO (SyncWorker_9) [hassio.docker.interface] Clean homeassistant/armhf-addon-mosquitto Docker application
18-10-21 08:44:00 INFO (SyncWorker_19) [hassio.docker.addon] Start Docker add-on homeassistant/armhf-addon-mosquitto with version 2.0
18-10-21 08:44:34 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services access from core_configurator
18-10-21 08:44:34 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/events access from core_configurator
18-10-21 08:44:34 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from core_configurator
18-10-21 08:56:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 09:29:43 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services/homeassistant/restart access from core_configurator
18-10-21 09:29:43 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 09:29:43 INFO (SyncWorker_15) [hassio.docker] Run command 'python3 -m homeassistant -c /config --script check_config' on homeassistant/raspberrypi3-homeassistant
18-10-21 09:30:30 INFO (MainThread) [hassio.homeassistant] Home Assistant config is valid
18-10-21 09:30:30 INFO (SyncWorker_6) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
18-10-21 09:31:02 INFO (SyncWorker_6) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
18-10-21 09:31:03 INFO (SyncWorker_8) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.80.3
18-10-21 09:32:50 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services access from core_configurator
18-10-21 09:32:50 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/services: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
18-10-21 09:32:50 ERROR (MainThread) [hassio.api.proxy] Error on API for request services
18-10-21 09:35:01 INFO (MainThread) [hassio.api.security] /homeassistant/logs access from core_ssh
18-10-21 09:35:13 INFO (MainThread) [hassio.api.security] /supervisor/logs access from core_ssh

Note: The HA log contains no error at all, just normal initialization things as usual. Note 2: A supervisor restart doesn't resolve it, I need to restart the whole router and then restart Home Assistant (again). Idea: Maybe this can be fixed by disabling and re-enabling the ethenet port on the RPi, if that specific error happens, causing the RPi to refresh it's IP, DHCP and whatnot. Would be great if someone could implement this on a newer build. I would for sure test it out.

janningnetworks commented 5 years ago

metoo ;) Did you solve this issue?

Fusseldieb commented 5 years ago

@janningnetworks No, it's quite rare to occurr, so I don't care that much, but I still put this here, so the devs can eventually fix this.

thakkarrahul commented 5 years ago

Hi,

I am having similar issues and have tried the above method but still the same. I am on HASSIO version 0.81.6

Here is the link to forum page where I have explained the issue.

https://community.home-assistant.io/t/hassio-no-web-interface/77208

If you have any solution, please help.

Fusseldieb commented 5 years ago

Bump. Still happening on 0.84.

magin1 commented 5 years ago

Bump. Still happening on 0.85.

TheZoker commented 5 years ago

I have the same issue @pvizeli any idea?

SP410 commented 5 years ago

FYI, I have the issue in running HassIO in Docker on Ubuntu 18.04.1. For me it occurs after performing a snapshot restore...

arissaraiva commented 5 years ago

Hi same issue here openned another thread, I can´t access spotfy, darksky nd cloud all give me API error

bratanon commented 5 years ago

Same for me since 0.85. Running the default Hassio on rpi3

bratanon commented 5 years ago

and same with 0.85.1

Fusseldieb commented 5 years ago

Quick update on my findings: If this happens, reconnecting the LAN interface on my router and then doing a "hassio su reload" over SSH makes it load everything again, so my assumption is right.

Maybe this can be fixed by disabling and re-enabling the ethenet port on the RPi, if that specific error happens, causing the RPi to refresh it's IP, DHCP and whatnot. Would be great if someone could implement this on a newer build.

ahnernoch commented 5 years ago

Same here. Sometimes Web Interface just wont come up.

h4nc commented 5 years ago

same here

My error looks like this: [hassio.api.proxy] Client error on WebSocket API Cannot connect to host "IP" ssl:False [Connection refused].

Strange... I get this error serveral times when I restart homeassistant. I don't get it when I reboot the whole system (hassio). Could someone confirm that?

EDIT: Maybe this is an expected behaviour. When I restart home assistant, hassio wil not be able to reach ha in the time it restart, so it throws that error. When I restart hassio it can't try to reach ha.

Obicom commented 5 years ago

Same issue with new beta 0.87.0b0

1iveowl commented 5 years ago

Same issue w/ 0.87.1

PreferHardware commented 5 years ago

Same here, hassio 8.7.1 on NUC5PPYH with duckdns and ssl:

[homeassistant.components.hassio.handler] Client error on /supervisor/ping request Cannot connect to host 172.30.32.2:80 ssl:None [Connection refused]

The problems started as soon as I moved to ssl, duckdns, etc. No amount of messing around with yaml files made any difference, but a cold reboot magically cleared the errors.

PreferHardware commented 5 years ago

This behaviour could also, repeatably, be triggered by including a discovered media_player (samsungtv) in the yaml. Commenting out the line and rebooting (not simply restarting the containers) was the solution.

h4nc commented 5 years ago

Which line exactly do you mean? Ignore it in autodiscovery?

I indeed also have a samsung tv.

discovery:
  ignore:
PreferHardware commented 5 years ago

I tried adding the Samsung TV to a "Sitting Room" group by simply adding the line:

in groups.yaml. This was the line that caused problems and was the line that I commented out before rebooting.

The process of discovery does not seem to be the problem. The problem only comes when the discovered entity is actually introduced into the yaml.

h4nc commented 5 years ago

Ok, I don't have my media_player's in a group. I'm not sure we have the same issue.

I also noticed that the samsung media player entities are not reliable. Sometimes they show up sometimes not. I think you onle get them when the TV is on when you start home assisant.

So if you restart ha and the tv is off, the entity does not show (I'm not a 100% sure about that, buts that'S my guess).

radionerd1 commented 5 years ago

This is driving me nuts. Why is it trying an IP that is not on my network? ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False

I have scene this for months now, I search forums with no fixes. My private network is 192.168.1.0/24 WTF???

radionerd1 commented 5 years ago

Looks for invalid IP 172.30.32.1:8123, Won't update, rolls back. 


19-03-15 04:42:42 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-03-15 04:42:42 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-03-15 04:42:42 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-03-15 04:42:46 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
19-03-15 04:42:46 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
19-03-15 04:42:46 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.2
19-03-15 04:42:46 INFO (SyncWorker_12) [hassio.docker.interface] Update Docker homeassistant/raspberrypi3-homeassistant:0.89.2 to homeassistant/raspberrypi3-homeassistant:0.88.2
19-03-15 04:42:46 INFO (SyncWorker_12) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.88.2.
TheZoker commented 5 years ago

@radionerd1 The IP 172.30.32.1 belongs to docker: https://community.home-assistant.io/t/mqtt-why-172-30-32-1-gets-connected/46513/2

tyborall commented 5 years ago

Just add

  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - 172.16.0.0/12

under homeassistant:

in your configuration.yaml...

@developers: I think this should be a default in configuration.

DeviousPenguin commented 5 years ago 
- type: trusted_networks
  trusted_networks:
    - 172.16.0.0/12

Will this disable authentication at all? I have my HomeAssistant port exposed to the internet, and I'd like to keep auth enabled.

tyborall commented 5 years ago

Ah sorry, if you use nginx, yes it will. Then just allow that particular host.

DeviousPenguin commented 5 years ago

Ok, thanks, I just wanted to be sure before tinkering with the settings.

I've got it set under trusted_proxies: instead and and it seems to be working OK with NGINX + HA authentication so far.

rover6s commented 5 years ago

I had the same issue and removed all the Add-ons that I had added while learning HA. I had Configurator, Samba, and APPDaemon.

After removing the Add-ons I rebooted the RPi from the Hass.io-->System-->Host System menu and the error is gone. I have added the Configurator back and still no error in the System log. I really need the AppDaemon for the HADashboard so I'll add that back and see what happens.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

cotwild commented 5 years ago

After update to 0.96.3 I cannot access any dev-state, dev-info, etc. - the "developer-tools" link is new but doesn't work... So this is my System log under Hass.io -> System:

19-07-23 06:44:02 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/states/sensor.printer_status: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused] 19-07-23 06:44:02 ERROR (MainThread) [hassio.api.proxy] Error on API for request states/sensor.printer_status 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-07-23 06:44:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-07-23 06:44:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-07-23 06:44:07 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/states/sensor.printer_status: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused] 19-07-23 06:44:07 ERROR (MainThread) [hassio.api.proxy] Error on API for request states/sensor.printer_status 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3

cotwild commented 5 years ago

Stupid me.... Page refresh did the trick! sorry... how could if forget this and try to fix it for that long...

pilot1981 commented 5 years ago

I have hassio 0.96 with same issue...

Fusseldieb commented 5 years ago

The stale bot is probably one of the most useless bots ever. It closes the issue, essentially marking it as solved and therefore it won't appear in open issues anymore, making the devs think this is solved. But it isn't. Can anyone please open this back up, because this is clearly not solved!?

EDIT: I personally think that whole Docker thingy is a mess. One docker container tries to communicate with another, for some reason can't and then messes everything up and leaves tons of people frustrated. Can't we simply integrate the whole Hassio in the OS like normal people? Docker only slows things down, particularly on lower end hardware like the RPi, and on top of that introduces errors that wouldn't even happen without it. Relevant XKCD Python is already relatively slow compared to other languages, and to top it all we add a lot of complexity layers on top. And then we run that on a RPi. And then we have 90+ seconds start up time. And sometimes it won't boot for some reason. Great!

Sorry for the little "outburst", but I think this needs to be said.

Chuchodavids commented 5 years ago

I know this is an old post. But I had this problem with the last HA update. I found a solution: The problem is caused by a conflict in the ports

  1. Stop all your containers except Portainer and HA + HA supervisor
  2. Check if that solved your problem. If so.. continue to point three.
  3. Activate one of your Docker containers and check if the problem persist.
  4. Repeat number three until you find out which one is the container that is conflicting with HA.
  5. When you find it, just stop the container and change the ports in which the container is running.
  6. enjoy.
aatumaykin commented 4 years ago

I have this issue. hassio 0.100.2 - 0.101.2

Tiilin commented 4 years ago

I have the same issue. Hassio 0.101.3

pilot1981 commented 4 years ago

Also me, during reboot action

rant989 commented 4 years ago

I have the same issue. Hassio 0.101.3

sebba12 commented 4 years ago

I have the same issue. Hassio 0.101.3 and not in any versions before.

gdreelin commented 4 years ago

Yep same here just started on version 0.101.3 never seen it before that.

PietroMB commented 4 years ago

I have same issue. Hassio 0.100.2

RichardUUU commented 4 years ago

I have it in Hassio 102.2. Running as a VM with no dockers. Do we need to open a new issue?

dubbfredda commented 4 years ago

I also have the same problem

dubbfredda commented 4 years ago

First I could not update Hassio and when I tried to update a second time it never come back up again after the update. The Homeassistant container is started but can't get any connection with the Hassio frontend. Get following error 19-11-26 20:34:25 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

MalagaInternet commented 4 years ago

+1 Hassio 102.2

thomasfals commented 4 years ago

+1 Hassio 0.102.3

matteos1 commented 4 years ago

i have the same problem 19-11-30 21:47:34 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:47:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:47:39 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:47:39 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:47:44 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:47:44 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:47:44 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:47:49 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:47:49 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:47:49 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:47:54 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:47:54 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:47:54 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:47:59 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:47:59 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:47:59 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:04 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:04 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:04 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:09 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:09 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:09 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:14 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:14 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:14 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:19 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:19 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:19 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:24 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:24 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:24 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:29 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:29 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:29 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:34 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:34 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:34 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:39 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:39 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:44 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:44 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:44 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:49 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:49 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:49 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:54 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:54 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:54 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:48:59 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:48:59 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:48:59 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:04 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:04 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:04 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:09 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:09 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:09 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:14 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:14 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:14 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:19 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:19 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:19 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:24 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:24 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:24 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:29 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:30 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:30 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:35 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:35 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:35 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:40 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:40 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:40 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:45 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:45 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:45 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:50 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:50 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:50 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-11-30 21:49:55 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-11-30 21:49:55 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-11-30 21:49:55 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

anklimov commented 4 years ago

Is some progress to fix the issue? I have same. And have no idea how to recover it, except moving back to OpenHab

pricard32 commented 4 years ago

This is the internal IP of your docker container. I run hassio on a Ubuntu server, but every Hassio installation use docker. Docker need two network, an external (your lan) and a internal (172.30.32.0/23).

I'm not sure why we all seeing this, maybe a docker expert can help us. But in my particular case, exept seeing this, theres no error on my installation.

bschatzow commented 4 years ago

I have this issue when I updated to .103 in Hassio