@millions-hair-24956 } 2025-03-01T071604.615Z DEBUG livekit.transport rtc/transport.go:606 ice gathering state change {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx", "participant": "test-10", "pID": "PA_q6NJHCdyV3yL", "remote": false, "transport": "PUBLISHER", "state": "closed"} 2025-03-01T071604.615Z DEBUG livekit.transport rtc/transport.go:637 ice connection state change {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx", "participant": "test-10", "pID": "PA_q6NJHCdyV3yL", "remote": false, "transport": "PUBLISHER", "state": "closed"} 2025-03-01T071604.615Z DEBUG livekit.transport rtc/transport.go:648 peer connection state change {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx", "participant": "test-10", "pID": "PA_q6NJHCdyV3yL", "remote": false, "transport": "PUBLISHER", "state": "closed"} 2025-03-01T071604.615Z DEBUG livekit.transport rtc/transport.go:606 ice gathering state change {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx", "participant": "test-10", "pID": "PA_q6NJHCdyV3yL", "remote": false, "transport": "SUBSCRIBER", "state": "closed"} 2025-03-01T071604.616Z DEBUG livekit.transport rtc/transport.go:648 peer connection state change {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx", "participant": "test-10", "pID": "PA_q6NJHCdyV3yL", "remote": false, "transport": "SUBSCRIBER", "state": "closed"} 2025-03-01T071604.615Z DEBUG livekit.transport rtc/transport.go:637 ice connection state change {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx", "participant": "test-10", "pID": "PA_q6NJHCdyV3yL", "remote": false, "transport": "SUBSCRIBER", "state": "closed"} 2025-03-01T071624.856Z INFO livekit.room rtc/room.go:911 closing room {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx"} 2025-03-01T071624.857Z INFO livekit service/roommanager.go:168 deleting room state {"room": "test-10"} 2025-03-01T071624.858Z INFO livekit.room service/roommanager.go:626 room closed {"room": "test-10", "roomID": "RM_F7M2UEPWmBKx"} Error I get in EKS.

It seems likely that the logs indicate a disconnection issue where the ICE and peer connections for both the publisher and subscriber transports are closed. This could be due to network issues or misconfigurations in your EKS setup. According to LiveKit documentation, disconnections can occur due to network changes or server-initiated actions. To troubleshoot, you might want to check your network settings, ensure that all necessary ports are open, and verify that your ICE servers are correctly configured. Additionally, reviewing the troubleshooting guide for self-hosted LiveKit deployments might provide further insights. Would you like more detailed guidance on specific troubleshooting steps? Sources: - LiveKit documentation - troubleshooting guide 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.