WS Connection Closes Automatically
See original GitHub issueHey, I know I’m missing something, but I can’t quite wrap my head around what it is. Right now, the client starts up but then immediately closes right after.
Here’s the logs from livekit-server
:
And here’s my code:
<LiveKitRoom url={url} token={token} connectOptions={{logLevel: LogLevel.debug}} onConnected={room => onConnected(room)} onLeave={() => console.log('leaving the room')}
What am I doing wrong? I should mention that neither the onConnected
or onLeave
functions ever get called.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
websocket closing connection automatically - Stack Overflow
The client is the default websocket implementation in google chrome. Everything is working ok, only if there is no transfer between server and ......
Read more >WebSocket.close() - Web APIs - MDN Web Docs
The WebSocket.close() method closes the WebSocket connection or connection attempt, if any. If the connection is already CLOSED, ...
Read more >JavaScript : websocket closing connection automatically
JavaScript : websocket closing connection automatically [ Gift : Animated Search Engine : https://bit.ly/AnimSearch ] JavaScript : websocket ...
Read more >WebSocket connection closes immediately · Issue #449 - GitHub
I found the issue and it was that when we terminate the connection the code was still normal. Fixed the issue elsewhere.
Read more >Websocket connection closes after about 10s - Google Groups
I'm successfully creating a websocket connection from Chrome to Mongoose, and sending data both ways. After about 10s of inactivity, Mongoose reports that ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hah, I’m glad you figured it out. We should make it more explicit in the docs that ports need to be open on that IP.
Btw, Adalo looks awesome! If you ever want to incorporate video/audio modules into it, we can help 😃
I figured it out. I was using my public IP address instead of my private one when starting docker 🤦♂️