go2rtc binds to localhost only while go2rtc client tries to connect to the docker container host IP

[linkages]

The problem

After upgrading to homeassistant 2024.11.0, I noticed in my logs a bunch of go2rtc errors.
After reading about the new go2rtc integration I believe the problem is that go2rtc is being started with its api port bound to localhost:11984 instead of the *:11984 or the IP of the machine.

When I run the go2rtc integration with debug_ui set to true it does listen on *:11984

What version of Home Assistant Core has the issue?

core-2024.11.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

go2rtc

Link to integration documentation on our website

https://www.home-assistant.io/integrations/go2rtc/

Diagnostics information

This is what lsof of the go2rtc process looks like when run in debug_ui mode:

[root@ha-1 ~]# lsof -p 291042
COMMAND    PID USER  FD      TYPE   DEVICE SIZE/OFF     NODE NAME
go2rtc  291042 root cwd       DIR    254,2     4096       28 /config
go2rtc  291042 root rtd       DIR     0,57     4096   121208 /
go2rtc  291042 root txt       REG     0,57  5695036   121168 /bin/go2rtc
go2rtc  291042 root   0r      CHR      1,3      0t0       56 /dev/null
go2rtc  291042 root   1w     FIFO     0,15      0t0 15182024 pipe
go2rtc  291042 root   2w     FIFO     0,15      0t0 15182024 pipe
go2rtc  291042 root   3u  a_inode     0,16        0       89 [eventpoll:4,5,6,7,9]
go2rtc  291042 root   4u  a_inode     0,16        0       89 [eventfd:12]
go2rtc  291042 root   5u     IPv4 15182873      0t0      TCP localhost:18554 (LISTEN)
go2rtc  291042 root   6u     IPv6 15182880      0t0      TCP *:18555 (LISTEN)
go2rtc  291042 root   7u     IPv6 15180767      0t0      TCP *:11984 (LISTEN)
go2rtc  291042 root   9u     IPv6 15182032      0t0      TCP localhost:11984->localhost:53988 (ESTABLISHED)

while this is what it looks like with debug_ui turned off:

[root@ha-1 ~]# lsof -p 291681
COMMAND    PID USER  FD      TYPE   DEVICE SIZE/OFF     NODE NAME
go2rtc  291681 root cwd       DIR    254,2     4096       28 /config
go2rtc  291681 root rtd       DIR     0,57     4096   121208 /
go2rtc  291681 root txt       REG     0,57  5695036   121168 /bin/go2rtc
go2rtc  291681 root   0r      CHR      1,3      0t0       56 /dev/null
go2rtc  291681 root   1w     FIFO     0,15      0t0 15184858 pipe
go2rtc  291681 root   2w     FIFO     0,15      0t0 15184858 pipe
go2rtc  291681 root   3u  a_inode     0,16        0       89 [eventpoll:4,5,6,8]
go2rtc  291681 root   4u  a_inode     0,16        0       89 [eventfd:10]
go2rtc  291681 root   5u     IPv4 15183775      0t0      TCP localhost:18554 (LISTEN)
go2rtc  291681 root   6u     IPv6 15183782      0t0      TCP *:18555 (LISTEN)
go2rtc  291681 root   8u     IPv4 15184866      0t0      TCP localhost:11984 (LISTEN)

This is running the latest home assistant container.

Here is my docker-compose.yaml file:

services:
  homeassistant:
    container_name: homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
      - /home/eli/src/ha/config:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    environment:
      - TZ=EST5EDT
    privileged: true
    network_mode: host

It is running as a privileged container with its network set to host mode.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Here is a snippet from "docker compose logs" that shows the connection errors

The docker container host IP is 192.168.1.33


homeassistant  | 2024-11-08 11:03:13.539 WARNING (MainThread) [homeassistant.components.go2rtc] Could not start go2rtc server
homeassistant  | Traceback (most recent call last):
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1091, in _wrap_create_connection
homeassistant  |     sock = await aiohappyeyeballs.start_connection(
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohappyeyeballs/impl.py", line 104, in start_connection
homeassistant  |     raise first_exception
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohappyeyeballs/impl.py", line 82, in start_connection
homeassistant  |     sock = await _connect_sock(
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohappyeyeballs/impl.py", line 174, in _connect_sock
homeassistant  |     await loop.sock_connect(sock, address)
homeassistant  |   File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 641, in sock_connect
homeassistant  |     return await fut
homeassistant  |            ^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 681, in _sock_connect_cb
homeassistant  |     raise OSError(err, f'Connect call failed {address}')
homeassistant  | ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.1.33', 11984)
homeassistant  |
homeassistant  | The above exception was the direct cause of the following exception:
homeassistant  |
homeassistant  | Traceback (most recent call last):
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 55, in request
homeassistant  |     resp = await self._session.request(method, url, **kwargs)
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 663, in _request
homeassistant  |     conn = await self._connector.connect(
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 563, in connect
homeassistant  |     proto = await self._create_connection(req, traces, timeout)
homeassistant  |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1032, in _create_connection
homeassistant  |     _, proto = await self._create_direct_connection(req, traces, timeout)
homeassistant  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1366, in _create_direct_connection
homeassistant  |     raise last_exc
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1335, in _create_direct_connection
homeassistant  |     transp, proto = await self._wrap_create_connection(
homeassistant  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1106, in _wrap_create_connection
homeassistant  |     raise client_error(req.connection_key, exc) from exc
homeassistant  | aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host localhost:11984 ssl:default [Connect call failed ('192.168.1.33', 11984)]
homeassistant  |
homeassistant  | The above exception was the direct cause of the following exception:
homeassistant  |
homeassistant  | Traceback (most recent call last):
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/go2rtc_client/exceptions.py", line 56, in _func
homeassistant  |     return await func(*args, **kwargs)
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 74, in get_info
homeassistant  |     resp = await self._client.request("GET", self.PATH)
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 58, in request
homeassistant  |     raise ClientError(msg) from err
homeassistant  | aiohttp.client_exceptions.ClientError: Server communication failure: Cannot connect to host localhost:11984 ssl:default [Connect call failed ('192.168.1.33', 11984)]
homeassistant  |
homeassistant  | The above exception was the direct cause of the following exception:
homeassistant  |
homeassistant  | Traceback (most recent call last):
homeassistant  |   File "/usr/src/homeassistant/homeassistant/components/go2rtc/__init__.py", line 118, in async_setup
homeassistant  |     await server.start()
homeassistant  |   File "/usr/src/homeassistant/homeassistant/components/go2rtc/server.py", line 97, in start
homeassistant  |     await self._start()
homeassistant  |   File "/usr/src/homeassistant/homeassistant/components/go2rtc/server.py", line 136, in _start
homeassistant  |     await client.validate_server_version()
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/go2rtc_client/exceptions.py", line 56, in _func
homeassistant  |     return await func(*args, **kwargs)
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 150, in validate_server_version
homeassistant  |     application_info = await self.application.get_info()
homeassistant  |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/local/lib/python3.12/site-packages/go2rtc_client/exceptions.py", line 66, in _func
homeassistant  |     raise Go2RtcClientError from exc
homeassistant  | go2rtc_client.exceptions.Go2RtcClientError

### Additional information

_No response_

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (go2rtc) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of go2rtc can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign go2rtc Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

go2rtc documentation
go2rtc source
_{^{(message by IssueLinks)}}

[edenhaus]

Please share which errors you got.

We use localhost only on purpose as the API is used only by HA itself. No need to expose it publicly and we locked it to localhost for security reasons.

Only for debugging we allow accessing for any ip with the big warning that no auth is in place.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[dominiclesinski]

came here via a google search of my logfile message, hope this helps to resolve this:

`Logger: homeassistant.components.go2rtc
Source: components/go2rtc/init.py:129
integration: go2rtc (documentation, issues)
First occurred: 11:19:22 AM (1 occurrences)
Last logged: 11:19:22 AM

Could not start go2rtc server
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1109, in _wrap_create_connection
sock = await aiohappyeyeballs.start_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohappyeyeballs/impl.py", line 104, in start_connection
raise first_exception
File "/usr/local/lib/python3.12/site-packages/aiohappyeyeballs/impl.py", line 82, in start_connection
sock = await _connect_sock(
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohappyeyeballs/impl.py", line 174, in _connect_sock
await loop.sock_connect(sock, address)
File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 641, in sock_connect
return await fut
^^^^^^^^^
File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 681, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('::1', 11984, 0, 0)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 55, in request
resp = await self._session.request(method, url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 663, in _request
conn = await self._connector.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 538, in connect
proto = await self._create_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1050, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1384, in _create_direct_connection
raise last_exc
File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1353, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1124, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host localhost:11984 ssl:default [Connect call failed ('::1', 11984, 0, 0)]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/go2rtc_client/exceptions.py", line 56, in _func
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 74, in get_info
resp = await self._client.request("GET", self.PATH)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 58, in request
raise ClientError(msg) from err
aiohttp.client_exceptions.ClientError: Server communication failure: Cannot connect to host localhost:11984 ssl:default [Connect call failed ('::1', 11984, 0, 0)]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/go2rtc/init.py", line 129, in async_setup
await server.start()
File "/usr/src/homeassistant/homeassistant/components/go2rtc/server.py", line 98, in start
await self._start()
File "/usr/src/homeassistant/homeassistant/components/go2rtc/server.py", line 137, in _start
await client.validate_server_version()
File "/usr/local/lib/python3.12/site-packages/go2rtc_client/exceptions.py", line 56, in _func
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/go2rtc_client/rest.py", line 150, in validate_server_version
application_info = await self.application.get_info()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/go2rtc_client/exceptions.py", line 66, in _func
raise Go2RtcClientError from exc
go2rtc_client.exceptions.Go2RtcClientError`

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.