Thanks — I reviewed the logs showing the participant moved to DISCONNECTED with disconnectReason "SIGNAL_CLOSE." I’ll explain what that means and share targeted troubleshooting steps. What SIGNAL_CLOSE means • SIGNAL_CLOSE indicates the signaling (WebSocket) connection was closed from the client side or the signaling handshake failed — the server saw the client’s signaling channel terminate rather than a graceful Leave. Likely causes • Client closed the page/app or didn’t call a proper disconnect (abrupt termination). • Network interruption, firewall, or proxy closed the WebSocket mid-handshake. • Client failed to complete the connect handshake (e.g., token expired or invalid). • Client SDK crashed or blocked during connection setup. What you can check right now • Client logs: look for WebSocket close codes, SDK errors around the same timestamp, or uncaught exceptions just before disconnect. • Confirm the client calls Room.disconnect() (or the equivalent) on page unload/backgrounding. • Token/JWT: verify the token was valid at connect time and not near expiry. • Network path: check for proxies/firewalls or intermittent connectivity from the client’s network. • Reproduce: try connecting from a stable network (wired or different Wi‑Fi) and a fresh client instance to see if it’s reproducible. Next diagnostic details that will help me narrow it down • Which client SDK and version are you using (web/Android/iOS) and the exact SDK version? • Client-side logs (WebSocket close code, SDK errors) around 2025-12-23T081748.095Z. • Whether this happens for all users or only specific clients/networks. • Token lifetime / how tokens are minted in your flow. I can then suggest exact fixes (SDK code checks, token changes, or server-side config) based on your answers. Sources: client-sdk-android | livekit/livekit_composite | DeepWiki | Understanding the STATE_MISMATCH Disconnect Reason | Server-side | livekit/livekit_composite | DeepWiki | Connecting to LiveKit | LiveKit docs