Connections don't get established

[dnish]

Hey,
we currently deployed an production app with Trystero . We noticed that about 60% of the connections within a room don't get established. One room has always 2 peers in it. This is what we get when we log the rootSubscribe and selfSubscribe onMessage handlers:

We can see that 2 peers are active, but nothing more happens. The room.onPeerJoin callback is never fired.

To check if there are any WebRTC issues, we've also set iceTransportPolicy: "relay" to force using one of the TURN servers. But even that didn't fix the issue in production, there are still many connections like the one in the picture.

[jeremyckahn]

@dnish have you given the peers some time to connect? I've noticed that peer connections can take a few dozen seconds sometimes. Also browser implementations of WebRTC are still a little flakey depending on a wide variety of reasons.

[dnish]

@jeremyckahn yes, for debugging we set the timeout up to 20 seconds before the client automatically left the room. The failure rate was still at 60%. I'm a little bit confused why both clients seem to be in the room (due to the logs), but are not able to establish a connection. We've tested it with about 50 different users.

[dmotz]

@dnish the first step to debugging would be to setup a TURN server as described in this section of the readme. You can either run your own or try the free instance here. Setting iceTransportPolicy: "relay" won't have any effect on connecting to TURN. If TURN solves your problem, this is a case of network configuration issues where WebRTC unfortunately can't establish a direct connection. If it doesn't solve the issue, try using version 0.20.1 of Trystero and report back if you see different behavior with the same set of devices/networks. This would indicate some regression in the peering logic, so let me know.

[dmotz]

@dnish try with the latest version 0.21.4