This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

is there way to ask a RemoteTrack (or publication) if it’s current unsubscribed or do i need to use the callback?

This message was deleted.

Hi folks. I don't believe I've encountered this situation before, but on livekit-server v0.15.2, Join() requests to the room i'm using for testing are failing, and in the server logs I can see this, followed by a stack trace:

2022-01-20T18:51:49.111Z INFO livekit service/rtcservice.go:174 new client WS connected {"room": "test-device-foo", "participant": "signal-proxy-test-client", "connID": "signal-proxy-test-client", "roomID": "RM_TRa7WaXsmytf"}
2022-01-20T18:52:12.454Z DEBUG livekit logger/logger.go:22 starting RTC session {"room": "test-device-foo", "nodeID": "ND_vXL9gexQ", "participant": "signal-proxy-test-client", "sdk": "GO", "sdkVersion": "0.6.4", "protocol": 3}
2022-01-20T18:52:12.454Z INFO livekit service/rtcservice.go:193 source closed connection {"room": "test-device-foo", "participant": "signal-proxy-test-client", "connID": "signal-proxy-test-client"}
2022-01-20T18:52:12.454Z INFO livekit service/rtcservice.go:155 server closing WS connection {"room": "test-device-foo", "participant": "signal-proxy-test-client", "connID": "signal-proxy-test-client"}
2022-01-20T18:52:12.455Z ERROR livekit service/roommanager.go:264 could not join room {"room": "test-device-foo", "participant": "signal-proxy-test-client", "pID": "PA_WFdBZchK5QDp", "error": "room has already closed"}

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello again! 😀

This message was deleted.

This message was deleted.

Hello again!

Nevermind. 🙃 😅

Hello everyone, i am having an issue deploying livekit server to kubernetes, when i get the logs on the livekit pod i can see the connection, user and room but when i use the livekit tester it gives the result as shown on the image below. it seems like the tcp port at 7881 and the udp port at 7882 always

refuse the connection

. I am running livekit on kubernetes using aws eks and alb load balancer, i have expose the 7881 and 7882 , 50000 - 60000 ports on all my security group just to fix this. am i doing something wrong?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.