From f1da04eb274fefe39bd11be7254b2314d7d5bab1 Mon Sep 17 00:00:00 2001 From: briquet Date: Wed, 16 Sep 2026 08:39:40 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=A7(podman)=20pin=20the=20livekit=20rt?= =?UTF-8?q?c=20section=20for=20local=20usage?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pin the LiveKit rtc section: the browser reaches the server through podman's published ports on loopback while egress and the agents reach it over the podman network, and those two have no address in common. `advertise_internal_ip` keeps the container's own interface address as a host candidate alongside the node_ip one, so LiveKit offers both and ICE picks whichever works. Without it egress only ever sees 127.0.0.1, which is the egress container itself, and its peer connection timeouts `use_external_ip` is turned off since it would advertise the STUN-discovered public IP, which no local peer can hairpin to. --- docker/livekit/config/livekit-server.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docker/livekit/config/livekit-server.yaml b/docker/livekit/config/livekit-server.yaml index e3c77d69f..d4be8e8a9 100644 --- a/docker/livekit/config/livekit-server.yaml +++ b/docker/livekit/config/livekit-server.yaml @@ -21,3 +21,10 @@ turn: - 192.168.0.0/16 - 172.16.0.0/12 +rtc: + node_ip: 127.0.0.1 + advertise_internal_ip: true + udp_port: 7882 + tcp_port: 7881 + use_external_ip: false +