Sravan/BizGaze_Remote
0
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fix(sfu): upgrade LiveKit server v1.7 -> v1.9 to match client SDK 2.20

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Sravan
2026-07-07 12:33:11 +05:30
parent 496eba3c17
commit 37c8929c5e
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker-compose.yml
+4 -1
View File
@@ -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