You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While trying to establish a connection between two participants, one failed—and it always fails when this client tries to connect to a video session when other participants are already connected.
If this client connects first, then everything seems to be fine all the time. I assume the bug occurs only when other clients are connected.
Server
Version: v1.5.2
Environment: Self-managed Kubernetes v1.28.4
2x Livekit-server instances with Redis Sentinel
Client
SDK: js/ts
Version: 2.0.3
To Reproduce
Steps to reproduce the behavior:
client with chrome joins the meeting
2nd client tries to join with firefox
1st client sees that 2nd client came in to the meeting but no tracks are published, while 2nd client is still trying to connect
2nd client gets error and is disconnected from the video session
Expected behavior
Clients should be connected all the time
Additional context
Clients who faced the issue used:
1st client: edge with windows (don't know anything else)
2nd client: Firefox Version 123.0 (64-bit) on macOS Sonoma Version 14.2.1 (23C71)
The text was updated successfully, but these errors were encountered:
Yes and no simultaneously - we tried the same and got the same result; I saw participant B as connected, but without the tracks, and after some time (like the 30s), he came alive. Adding logs from the Participant B's perspective
Describe the bug
While trying to establish a connection between two participants, one failed—and it always fails when this client tries to connect to a video session when other participants are already connected.
If this client connects first, then everything seems to be fine all the time. I assume the bug occurs only when other clients are connected.
Server
Client
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Clients should be connected all the time
Logs
console-export.txt
Logs from our Loki - livekit server logs with this
roomID
filtered Explore-logs-2024-03-20 14_03_02.jsonAdditional context
Clients who faced the issue used:
1st client: edge with windows (don't know anything else)
2nd client: Firefox Version 123.0 (64-bit) on macOS Sonoma Version 14.2.1 (23C71)
The text was updated successfully, but these errors were encountered: