LiveKit Community

Where exactly are you seeing this? ie what connection is timing out?

And I’m only assuming it’s because of the device change but I’m not sure.

Oh, you’re seeing this in users who reconnect

in the logs around the same time I’ve found this
```INFO	livekit	rtc/participant_signal.go:187	could not send message to participant	
{
    "room": "260551fe-777a-4046-876f-f23eef8b0b64",
    "roomID": "RM_jF6hZXvg8H7y",
    "participant": "dd44a41e-8d75-41f4-8c1f-2b19d9263f4d",
    "pID": "PA_hUkwX6xcYSKx",
    "remote": false,
    "message": "*livekit.SignalResponse_Leave",
    "error": "channel closed"
}```

huh, weird. What SDK are these clients on?

so it’s the same user, two different devices, both devices using the React SDK — are the users connecting with the same token? if they’re not using the same token, are both tokens generated with the same `identity`?

<@U02EJ2AP755> which version of the server are you running.. and are you running in with redis or without?

<@U02MC5V3C2H> they are using the same identity, but they are closing one window before opening another.

<@U01KZ61GV5Z> we’re running without redis (should we?) and we were running 1.3.1 but just upgraded to 1.3.3 tonight. The problem was on 1.3.1, we haven’t had it on 1.3.3 so far.

yeah, I think the issue you've hit is <https://github.com/livekit/livekit/pull/1237|this>. it's fixed in 1.3.3. thank you for confirming that.

thanks <@U01KZ61GV5Z> that’s fantastic!