-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Disconnected from call" websocket connection failures #1844
Comments
Logs from the client when this happens:
So the websocket connection is failing within ~200ms: almost like the connection is being refused, except the server is saying:
...which implies the client is closing the connection? Or at least that it's certainly establishing a connection that's then getting closed again each time for some reason. |
livekit/client-sdk-js#921 should fix this! |
I just had the same problem (Windows 11, Edge) and a friend (iPhone, Safari). I don't know if it's after the fix has been merged to the version online (should've been merged into main 7 hours ago) |
Not sure what the next steps are here, potentially better errors ( @robintown ?) |
Steps to reproduce
Unknown!
We are seeing both a lot of rageshakes of people getting the 'disconnected from call" screen and occasionally seeing this in our usage where we'll suddenly be kicked to the disconnected for no reason.
This happened to me yesterday and the failure mode was: enter call, other person was in the call but was a grey screen. My mute button was showing I was unmuted but the mute indicator on my local video showed muted. Clicking the mute button did nothing, then after being confused for ~10 seconds, it changed to the disconnected from call screen.
On the livekit server, this manifested as,
INFO livekit service/rtcservice.go:374 exit ws read loop for closed connection {"room": "***", "roomID": "RM_VMPzm5H6xPjb", "participant": "@blush-brilliant-octopus:call.ems.host:XEQOOZWPJC", "pID": "PA_FPtvGSXW8SWM", "remote": false, "connID": "CO_Hn2rKNwoLB5R", "wsError": "websocket: close 1005 (no status)"}
...which suggests a TCP level disconnection of the websocket, I think, if no status was provided.
The client logs are not very helpful, with the client just unpublishing tracks and changing the connection status to disconnected after a while logging nothing.
Why is the websocket connection dying, and why isn't livekit trying to re-establish it?
Outcome
What did you expect?
What happened instead?
Operating system
No response
Browser information
No response
URL for webapp
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: