LiveKit Community

<@U01KZ61GV5Z> starting to see some pretty weird join issues with the latest server

client side is basically running into 2 different issues:

1. Sometimes the socket opens and I get a `Uncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable` error
2. Sometimes the socket will open then immediately close and so there are errors about sending messages down a closed socket. When this happens, I see a message saying `websocket connection closed` and `room event disconnected`

those server logs were dumped after both of those issues happened

and as a note, all of this is in multinode mode

thanks for sharing. I'm seeing the websocket closed issue too on my end. question, are you also seeing Furqan's issue with the second participant not able to publish streams?

well I can't really even get into the call right now to publish so I'm not sure

i can pretty much almost always get into a call

```client.js:19 {RTC_URL: "<wss://gql.livespot.co/v1beta1/relay>"}
index.js:98 GET <https://edge.fullstory.com/s/fs.js> net::ERR_BLOCKED_BY_CLIENT
u @ index.js:98
t @ index.js:355
gi @ react-dom.production.min.js:134
La @ react-dom.production.min.js:176
yo @ react-dom.production.min.js:263
su @ react-dom.production.min.js:246
uu @ react-dom.production.min.js:246
eu @ react-dom.production.min.js:239
Yo @ react-dom.production.min.js:230
Lu @ react-dom.production.min.js:281
(anonymous) @ react-dom.production.min.js:284
nu @ react-dom.production.min.js:240
Qu @ react-dom.production.min.js:284
t.hydrate @ react-dom.production.min.js:290
fe @ index.tsx:440
(anonymous) @ index.tsx:334
s @ runtime.js:63
(anonymous) @ runtime.js:293
(anonymous) @ runtime.js:118
r @ asyncToGenerator.js:3
u @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
ne @ main-4dfabbdb2a50663f6888.js:1
te @ main-4dfabbdb2a50663f6888.js:1
(anonymous) @ index.tsx:320
s @ runtime.js:63
(anonymous) @ runtime.js:293
(anonymous) @ runtime.js:118
r @ asyncToGenerator.js:3
u @ asyncToGenerator.js:25
Promise.then (async)
r @ asyncToGenerator.js:13
u @ asyncToGenerator.js:25
Promise.then (async)
r @ asyncToGenerator.js:13
u @ asyncToGenerator.js:25
Promise.then (async)
r @ asyncToGenerator.js:13
u @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
(anonymous) @ main-4dfabbdb2a50663f6888.js:1
BMP1 @ next.js:5
a @ bootstrap:86
0 @ main-4dfabbdb2a50663f6888.js:1
a @ bootstrap:86
t @ bootstrap:45
r @ bootstrap:32
(anonymous) @ commons.f22812852382ff8022e0.js:1
DevTools failed to load SourceMap: Could not parse content for <https://caves-posthog.zeet.app/static/rrweb.min.js.map>: Unexpected token &lt; in JSON at position 0
instrument.js:109 subscription data updated {session_connection: {…}}
instrument.js:109 connecting to <wss://livespot-livekit-server.zeet.app:443/rtc?access_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ2aWRlbyI6eyJyb29tIjoiYWUxNDc5M2EtYTBmNS00YWRjLTg1YTYtNWQzN2JiNDFlNTM3Iiwicm9vbUpvaW4iOnRydWV9LCJpYXQiOjE2MTIzMDQ2MzksIm5iZiI6MTYxMjMwNDYzOSwiZXhwIjoxNjEyMzE5MDM5LCJpc3MiOiJ0ZXN0IiwianRpIjoiMHhGRkM4MGJkMkE0MTNmMzdFMTI1RDM5QzI4MUNjODVCODhkY2ViRjIwIn0.nWmA_rpcHzcFRjlJRXV0vXIb_JaH0HkOgtf5WCj4HRA>
instrument.js:109 unsupported message {join: {…}, answer: undefined, offer: undefined, trickle: undefined, update: undefined, …}
(anonymous) @ instrument.js:109
console.warn @ _app.tsx:40
overrideMethod @ react_devtools_backend.js:2430
handleSignalResponse @ RTCClient.js:152
r.onmessage @ RTCClient.js:47
instrument.js:109 sending offer RTCSessionDescription {type: "offer", sdp: "v=0
↵o=- 8037664157463726149 2 IN IP4 127.0.0.1
↵s…:0
↵a=sctp-port:5000
↵a=max-message-size:262144
↵"}
instrument.js:109 got ICE candidate from peer {candidate: "candidate:1728288015 1 udp 2130706431 100.96.117.111 8702 typ host", sdpMid: "", sdpMLineIndex: 0, usernameFragment: null}
instrument.js:109 got ICE candidate from peer {candidate: "candidate:4152535316 1 udp 2130706431 100.96.231.25 8417 typ host", sdpMid: "", sdpMLineIndex: 0, usernameFragment: null}
instrument.js:109 RTC connected
instrument.js:109 sending ice candidate RTCIceCandidate {candidate: "candidate:2530088836 1 udp 2122260223 192.168.1.10…eration 0 ufrag 9GZ+ network-id 1 network-cost 10", sdpMid: "0", sdpMLineIndex: 0, foundation: "2530088836", component: "rtp", …}
RTCEngine.js:6 Uncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable
Promise.then (async)
c @ RTCEngine.js:7
(anonymous) @ RTCEngine.js:8
r @ RTCEngine.js:4
client.onAnswer @ RTCEngine.js:93
handleSignalResponse @ RTCClient.js:121
r.onmessage @ RTCClient.js:47
VM2431:1 POST <https://o474346.ingest.sentry.io/api/5512625/store/?sentry_key=8b1d2d154fb2417daf0dbc7b01822d18&amp;sentry_version=7> net::ERR_BLOCKED_BY_CLIENT
(anonymous) @ VM2431:1
(anonymous) @ instrument.js:136
e.&lt;computed&gt;.e.&lt;computed&gt; @ index.js:149
(anonymous) @ fetch.js:55
e @ syncpromise.js:78
t._sendRequest @ fetch.js:53
t.sendEvent @ fetch.js:16
e.sendEvent @ basebackend.js:33
e._sendEvent @ baseclient.js:361
t._sendEvent @ client.js:64
(anonymous) @ baseclient.js:432
onfulfilled @ syncpromise.js:137
(anonymous) @ syncpromise.js:66
_executeHandlers @ syncpromise.js:59
_attachHandler @ syncpromise.js:50
(anonymous) @ syncpromise.js:127
e @ syncpromise.js:78
e.then @ syncpromise.js:126
e._processEvent @ baseclient.js:424
e._captureEvent @ baseclient.js:370
e.captureEvent @ baseclient.js:93
e._invokeClient @ hub.js:348
e.captureEvent @ hub.js:169
callback @ globalhandlers.js:118
_e @ instrument.js:76
me.onunhandledrejection @ instrument.js:482
instrument.js:109 sending ice candidate RTCIceCandidate {candidate: "candidate:3628985204 1 tcp 1518280447 192.168.1.10…eration 0 ufrag 9GZ+ network-id 1 network-cost 10", sdpMid: "0", sdpMLineIndex: 0, foundation: "3628985204", component: "rtp", …}
instrument.js:109 got ICE candidate from peer {candidate: "candidate:630202266 1 udp 1694498815 34.209.81.77 8818 typ srflx raddr 0.0.0.0 rport 8818", sdpMid: "", sdpMLineIndex: 0, usernameFragment: null}
instrument.js:109 got ICE candidate from peer {candidate: "candidate:3328690807 1 udp 1694498815 18.237.92.159 8539 typ srflx raddr 0.0.0.0 rport 8539", sdpMid: "", sdpMLineIndex: 0, usernameFragment: null}
instrument.js:109 ICE connected
instrument.js:109 null null ƒ (e,t){void 0===e&amp;&amp;(e=l),o.disposeRequest(),o.fetch(e,!1,t)}
instrument.js:109 {chat_message_connection: {…}} null ƒ (e,t){void 0===e&amp;&amp;(e=l),o.disposeRequest(),o.fetch(e,!1,t)}
instrument.js:109 subscription data updated {chat_message_connection: {…}}
instrument.js:109 2000-01-19T00:03:37.666Z
instrument.js:109 {id: "-1", message: "", timestamp: Tue Jan 18 2000 19:03:37 GMT-0500 (Eastern Standard Time), user: {…}}
instrument.js:109 Fetched new messages:  {chat_message_connection: {…}}
instrument.js:109 {audioEnabled: true, videoEnabled: true}
instrument.js:109 created tracks (2) [o, o]
instrument.js:109 publisingTracks (2) [o, o]
instrument.js:109 publish but publishing already
instrument.js:109 publish but publishing already
instrument.js:109 requesting negotiation
instrument.js:109 missing track resolver for  154131ca-f8ed-46e9-b7d8-39d154ce311f
(anonymous) @ instrument.js:109
console.error @ _app.tsx:46
overrideMethod @ react_devtools_backend.js:2430
client.onLocalTrackPublished @ RTCEngine.js:122
handleSignalResponse @ RTCClient.js:143
r.onmessage @ RTCClient.js:47
instrument.js:109 missing track resolver for  1fc22897-9523-44cf-8571-49e50b6e6b76
(anonymous) @ instrument.js:109
console.error @ _app.tsx:46
overrideMethod @ react_devtools_backend.js:2430
client.onLocalTrackPublished @ RTCEngine.js:122
handleSignalResponse @ RTCClient.js:143
r.onmessage @ RTCClient.js:47
2instrument.js:109 starting to negotiate stable
instrument.js:109 sending offer RTCSessionDescription {type: "offer", sdp: "v=0
↵o=- 8037664157463726149 3 IN IP4 127.0.0.1
↵s…1511 label:1fc22897-9523-44cf-8571-49e50b6e6b76
↵"}
instrument.js:109 sending ice candidate RTCIceCandidate {candidate: "candidate:2530088836 1 udp 2122260223 192.168.1.10…eration 0 ufrag 9GZ+ network-id 1 network-cost 10", sdpMid: "1", sdpMLineIndex: 1, foundation: "2530088836", component: "rtp", …}
instrument.js:109 sending ice candidate RTCIceCandidate {candidate: "candidate:2530088836 1 udp 2122260223 192.168.1.10…eration 0 ufrag 9GZ+ network-id 1 network-cost 10", sdpMid: "2", sdpMLineIndex: 2, foundation: "2530088836", component: "rtp", …}
instrument.js:109 sending offer RTCSessionDescription {type: "offer", sdp: "v=0
↵o=- 8037664157463726149 4 IN IP4 127.0.0.1
↵s…1511 label:1fc22897-9523-44cf-8571-49e50b6e6b76
↵"}
instrument.js:109 sending ice candidate RTCIceCandidate {candidate: "candidate:3628985204 1 tcp 1518280447 192.168.1.10…eration 0 ufrag 9GZ+ network-id 1 network-cost 10", sdpMid: "1", sdpMLineIndex: 1, foundation: "3628985204", component: "rtp", …}
instrument.js:109 sending ice candidate RTCIceCandidate {candidate: "candidate:3628985204 1 tcp 1518280447 192.168.1.10…eration 0 ufrag 9GZ+ network-id 1 network-cost 10", sdpMid: "2", sdpMLineIndex: 2, foundation: "3628985204", component: "rtp", …}
RTCEngine.js:6 Uncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable
Promise.then (async)
c @ RTCEngine.js:7
(anonymous) @ RTCEngine.js:8
r @ RTCEngine.js:4
client.onAnswer @ RTCEngine.js:93
handleSignalResponse @ RTCClient.js:121
r.onmessage @ RTCClient.js:47
VM2431:1 POST <https://o474346.ingest.sentry.io/api/5512625/store/?sentry_key=8b1d2d154fb2417daf0dbc7b01822d18&amp;sentry_version=7> net::ERR_BLOCKED_BY_CLIENT
(anonymous) @ VM2431:1
(anonymous) @ instrument.js:136
e.&lt;computed&gt;.e.&lt;computed&gt; @ index.js:149
(anonymous) @ fetch.js:55
e @ syncpromise.js:78
t._sendRequest @ fetch.js:53
t.sendEvent @ fetch.js:16
e.sendEvent @ basebackend.js:33
e._sendEvent @ baseclient.js:361
t._sendEvent @ client.js:64
(anonymous) @ baseclient.js:432
onfulfilled @ syncpromise.js:137
(anonymous) @ syncpromise.js:66
_executeHandlers @ syncpromise.js:59
_attachHandler @ syncpromise.js:50
(anonymous) @ syncpromise.js:127
e @ syncpromise.js:78
e.then @ syncpromise.js:126
e._processEvent @ baseclient.js:424
e._captureEvent @ baseclient.js:370
e.captureEvent @ baseclient.js:93
e._invokeClient @ hub.js:348
e.captureEvent @ hub.js:169
callback @ globalhandlers.js:118
_e @ instrument.js:76
me.onunhandledrejection @ instrument.js:482
instrument.js:109 Video element getting destroyed
instrument.js:109 hanging up: sessionId, publishingTracks, localParticipant ae14793a-a0f5-4adc-85a6-5d37bb41e537 (2) [o, o] v {_events: {…}, _eventsCount: 0, _maxListeners: undefined, sid: "PA_ZDcSTKzyBRugyxPNaVHN9c", identity: "0xFFC80bd2A413f37E125D39C281Cc85B88dcebF20", …}
instrument.js:109 unpublishTrack unpublishing track o {_events: {…}, _eventsCount: 2, _maxListeners: undefined, kind: "audio", name: "", …}
instrument.js:109 unpublishTrack: removing the track from 2 senders o {_events: {…}, _eventsCount: 2, _maxListeners: undefined, kind: "audio", name: "", …}
instrument.js:109 unpublishTrack unpublishing track o {_events: {…}, _eventsCount: 2, _maxListeners: undefined, kind: "video", name: "FaceTime HD Camera", …}
instrument.js:109 unpublishTrack: removing the track from 2 senders o {_events: {…}, _eventsCount: 2, _maxListeners: undefined, kind: "video", name: "FaceTime HD Camera", …}
instrument.js:109 requesting negotiation
instrument.js:109 {audioEnabled: true, videoEnabled: true}
instrument.js:109 created tracks (2) [o, o]
instrument.js:109 publisingTracks (2) [o, o]
instrument.js:109 Video element getting destroyed
instrument.js:109 publish but publishing already
instrument.js:109 publish but publishing already```

Version 88.0.4324.96 (Official Build) (arm64)

hmm.. something really strange in your logs:
```unsupported message {join: {…}```

this indicates that the internal state is messed up...

yeah, can you share the code you are using to connect?

```                const r = await Livekit.connect(
                    {
                        host: RTC_HOST as string,
                        port: parseInt(RTC_PORT as string, 10),
                        secure: RTC_SECURE === 'true',
                    },
                    token,
                    {
                        logLevel: LogLevel.debug,
                    },
                );```

the log seems to indicate that `Room.connect` had been called multiple times

we save it as a ref and use it for other actions later like publish

those server logs are for multiple connect attempts

as in I refreshed the page multiple times to reproduce the issues

yeah.. when you refresh.. it should've been created from scratch

I just added a log message for when we call connect

alright, sounds good.. I added a piece of code to block it from reconnecting.. in case that's related

i'll push it just in case something odd is going on

the real error of why it failed.. is where the client wasn't expecting an offer... when it works you should see something like: `_app.tsx?8548:34 received server answer answer have-local-offer`

this was in the logs furqan shared.. in a different instance.. he's running a later build of client than you are.. built from git

it's fine for now.. once we are stable, it'll be better to stick to release versions

do you auto publish right when the connect is established?

issue 1 is occurring for me almost every time I try to join a room

no, we `connect`  then user needs to click a button to `publish`

how should we hook into the websocket closing?

WS closing is a bug I can reproduce when clients connect

so if the peer connection is the source of truth for connection status, how should we handle the websocket disconnecting? Can livekit supply an option for reconnecting + a callback for when it happens (in case the consumer wants to do something different when socket closes)

maybe some consumers won't want to reconnect automatically

curious why you want it to be an option though

I think PeerConnection should be the source of truth.. but maybe a configurable # of retries?