Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error: Ice connection failed.
See original GitHub issueThe test suite is failing with Error: Ice connection failed.. I’ve also noticed this error in the WebTorrent Desktop telemetry logs, and it’s now one of the top errors.
We should figure out what’s going on.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Simple-peer WebRTC Error: Ice connection failed
I can not make the Simple-Peer NPM library to connect between two computers in two different networks in Browser.
Read more >Error: Ice connection failed #202 - feross/simple-peer - GitHub
This error is caused by a failure to find a viable network route through ICE. The following steps will help you debug common...
Read more >WebRTC 'ICE connection failed' even with proper ICE ... - Reddit
Good day! I am having trouble establishing a non-local network WebRTC connection. There are no issues making a connection in the same ...
Read more >ICE restarts - Medium
The failed state is a little more permanent, you need to do an ICE restart to get out of it. Typically, when the...
Read more >Ice connection Failed - Google Groups
The ICE agent has finished gathering candidates when users are in Same Internet connection, But if Users are in different Internet Connection Ice...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@surprisetalk Please see the investigation into this error I did in #202. There are multiple reasons for this error (mostly network related.)
The reconnectTimer option was removed in a past PR since we changed how we handle ice timeouts. You shouldn’t have the issue I’m talking about here in a new version of simple-peer.
I’ve noticed that the ICE status will briefly change to “disconnected” on Chrome. Adding a short reconnect timer (~100ms) has significantly reduced these errors for me. Maybe we should change the default timer?