Error: Ice connection failed. Running my own STUN/TURN server

I am running my own stun and turn server and I am getting the ERROR: Ice connection failed but I am getting it in a different spot than other issues…

I started with the examples and incrementally modded them along the way to fit into my react app.

1. offer is generated, copied into external chat app and sent to peer
2. peer copies offer and answer signal is generated.
3. a few seconds later the peer connection fails with the error…

Error: Ice connection failed.
    at r._onIceStateChange (index.js:492)
    at RTCPeerConnection.t._pc.oniceconnectionstatechange (index.js:91)

this happens before the answer is sent back to the origin…If I look at the webrtc-internals in chrome I can see that iceconncectionstatechange has failed, but I don’t know how to go about getting a more detailed error. In my coturn logs I can see both users are sending requests and being authenticated, so IDK…

any ideas?

[jeffwillette]

ok, yeah I wasn’t suggesting it would be documented here, but I was just saying that I couldn’t find it googling on any front. The only reason I knew about it was a low ranked answer on stack overflow that passingly mentioned it.

For anyone that finds this, I’ve opened a chrome bug

and here is the stack overflow post that mentions the timeout

[t-mullen]

I’ve hit it in the past. The problem with documenting that in simple-peer is that it’s Chrome specific and is actually a recent change. I believe it used to be that if signalling objects were stale the connection would fail naturally rather than some arbitrary timeout.