connection problem about peerjs

[SahilAggarwal2004]

This is an issue I am facing too. But this doesn't happen always, it happens only in some situations as mentioned by you. This didn't used to happen earlier, I guess this is some bug introduced by mistake either in peerjs library or webrtc in general, or possibly it may be because of this.

[jonasgloning]

I believe @SahilAggarwal2004 is correct; this issue could be related to TURN. When two Peers are behind a strict firewall or NAT, they can't communicate with each other directly and require a server to relay their data. Up until a few weeks ago, we maintained a free TURN server on a best-effort basis to prevent these connections from failing. However, since we had to discontinue this service, these specific connections will fail unless a TURN server URL is configured on the client. In the linked post there’s both a service and a software for self-hosting mentioned. Please try them out, and if there are still problems with a working TURN setup, we can investigate further.

[SahilAggarwal2004]

I believe @SahilAggarwal2004 is correct; this issue could be related to TURN.

When two Peers are behind a strict firewall or NAT, they can't communicate with each other directly and require a server to relay their data. Up until a few weeks ago, we maintained a free TURN server on a best-effort basis to prevent these connections from failing. However, since we had to discontinue this service, these specific connections will fail unless a TURN server URL is configured on the client.

In the linked post there’s both a service and a software for self-hosting mentioned. Please try them out, and if there are still problems with a working TURN setup, we can investigate further.

If I add the turn server configuration using the config property, will it replace the default configuration or append the config in default configuration?