From 37c8929c5ef66b7b07312af8fc4f798004df0d76 Mon Sep 17 00:00:00 2001 From: sravan Date: Tue, 7 Jul 2026 12:33:11 +0530 Subject: [PATCH] fix(sfu): upgrade LiveKit server v1.7 -> v1.9 to match client SDK 2.20 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The bundled livekit-client@2.20 uses signaling protocol 17 and the /rtc/v1 path, which the v1.7 server didn't implement (404). The client fell back to the legacy path, leaving the track publisher in a bad state so mic/cam publishing failed with 'InvalidAccessError: The sender was not created by this peer connection' — surfaced to users as a misleading 'permission required' toast. v1.9 supports protocol 17. Co-Authored-By: Claude Opus 4.8 --- docker-compose.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index 1d81cd2..0a8b6f1 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -30,7 +30,10 @@ services: # wss://livekit.bizgaze.com -> livekit:7880 (signaling); media flows over the published UDP/TCP # ports below, NOT through NPM. Single-node (no Redis) — consistent with the app's single-instance rule. livekit: - image: livekit/livekit-server:v1.7 + # v1.8+ implements the /rtc/v1 signaling path (protocol 17) that the bundled + # livekit-client@2.20 uses. On the older v1.7 the client fell back to the legacy path and + # track publishing broke (mic/cam wouldn't turn on). Keep this within one minor of the client. + image: livekit/livekit-server:v1.9 container_name: bizgaze-livekit restart: unless-stopped # Dormant by default: a normal `docker compose up -d` / deploy.sh does NOT start it. Enable SFU