We built and app in react frontend, java spring backend and unity webgl. When users join, a group, they are suppose to show up in my list of users in React and connect audio/video. But sometimes, some users can’t connect and we’re having a hard time figuring out why…
OpenVidu is deployed in my frontend react (debating if it would be better in backend Java spring boot?).
Are there any features in OpenVidu pro 2 that can help us debug these connectivity issues? The logs in the OpenVidu Compute Engine (OpsAgent) are just massive and hard to follow.
[WARN] 2025-02-19 22:01:05,657 [SessionHandler-v2rj4fve2g4skv5le2o2meeafd-e17-t0] io.openvidu.server.rpc.RpcHandler - Participant con_MW6S4LuYwI with IP 173.4.4.52 and platform Chrome 132.0.0.0 on Chrome OS 64-bit has an older version of op>
of openvidu-browser SDK (2.30.0) for this OpenVidu deployment (2.31.0). These versions are still compatible with each other, but client SDK must be updated as soon as possible to 2.31.x. This client using openvidu-browser 2.30.0 will become incompatible with the next release of openvidu-server
[ERROR] 2025-02-19 22:01:50,078 [http-nio-0.0.0.0-5443-exec-10] io.openvidu.server.rpc.RpcHandler - Transport exception for WebSocket session: 7qfvd - Exception: null
[WARN] 2025-02-19 22:01:54,887 [SessionHandler-10t1el2122aflcaajkh7bj4l4u-e27-t0] io.openvidu.server.rpc.RpcNotificationService - Removing ghost participant with participant private id 7qfvd
[WARN] 2025-02-19 22:01:54,887 [SessionHandler-10t1el2122aflcaajkh7bj4l4u-e27-t0] io.openvidu.server.rpc.RpcNotificationService - Notification ‘participantJoined’ couldn’t be sent to participant with privateId 7qfvd: The WebSocket session [4] has been closed and no method (apart from close()) may be called on a closed session
ERROR] 2025-02-19 22:01:55,572 [SessionHandler-10t1el2122aflcaajkh7bj4l4u-e27-t0] io.openvidu.server.kurento.core.KurentoSessionManager - PARTICIPANT con_Hp5Eamlw46: Error subscribing to con_IQI6lw6I57
io.openvidu.client.OpenViduException: User 'con_IQI6lw6I57 not found in session ‘d8zlsh-1739952000000-1’. Code: 102
at io.openvidu.server.kurento.core.KurentoSessionManager.subscribe(KurentoSessionManager.java:656)
at io.openvidu.server.rpc.RpcHandler.receiveVideoFrom(RpcHandler.java:425)
at io.openvidu.server.rpc.RpcHandler.handleRequest(RpcHandler.java:149)
at org.kurento.jsonrpc.internal.JsonRpcHandlerManager.handleRequest(JsonRpcHandlerManager.java:142)
at org.kurento.jsonrpc.internal.server.ProtocolManager$3.run(ProtocolManager.java:218)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
WARN] 2025-02-19 22:02:00,079 [jsonrpcTaskScheduler-1] io.openvidu.server.rpc.RpcHandler - Evicting participant with private id 7qfvd because a transport error took place and its websocket connection is now closed
[WARN] 2025-02-19 22:02:00,079 [jsonrpcTaskScheduler-1] io.openvidu.server.rpc.RpcHandler - Unable to evict: No participant with private id ‘7qfvd’ was found. Code: 102
Our logs are massive but these are the ones we were able to extract.
Just to ensure it is not an ICE connectivity issue, try to connect with Firefox, and after a failure with the tab of the OpenVidu Session opened, create a new browser tab to about:webrtc. There you can inspect if there is any kind of problem related with ICE connectivity.
I don’t have anything from the browser as this is hard to reproduce. It happens very randomly to random users. We’ve tried to replicate it often but haven’t been able to reproduce successfully.
I have a possible cause, but I can’t confirm without browser logs.
When an OpenVidu session is created and the last participant leaves, the session is closed automatically. If another user, who had previously connected, tries to join with a previous created token, they might encounter this issue. Does this apply to your situation?
To prevent this, ensure that a session is created and a token is generated every time a user attempts to join. The problem might occur if users are trying to connect right after the session has ended.
If this is your problem, It is not an issue by itself, it’s simply how OpenVidu v2 is designed. A session remains open until someone joins. Once the first participant enters, the session will close as soon as the last participant leaves.
But I can’t be sure 100% with only those logs, maybe some logs from the browser can help a bit.