Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't fetch peers: ICE (always) failed #467

Closed
gustavomrfz opened this issue Oct 24, 2015 · 2 comments
Closed

Can't fetch peers: ICE (always) failed #467

gustavomrfz opened this issue Oct 24, 2015 · 2 comments

Comments

@gustavomrfz
Copy link

@gustavomrfz gustavomrfz commented Oct 24, 2015

Hi,

I'm making a browser application with webtorrent module and bittorrent-tracker via web socket to sharing audio files and append them to a playlist. File sharing works fine inside a local area network, but the peers aren't fetched when they are behind a NAT. When I analyze traffic with Wireshark and about:webrtc, STUN servers return the remote private and public IP addresses with their UDP ports, but ICE process always fail. Application is using google STUN servers, but this behaviour exists with any server.

I'm using a global announce for tracker in client script. I launch the tracker with bin/cmd.js script. The tracker receive start message from peers, but never start really.

What could be happening? Must I set some options in the client script? Somes changes in bittorrent-tracker are needed?

Thank you in advance.

@gustavomrfz gustavomrfz changed the title Can't fetch peers: Ice (always) failed Can't fetch peers: ICE (always) failed Oct 24, 2015
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Feb 11, 2016

Sounds like you have a really restrictive NAT. You can specify a TURN server for these situtations, but the transfer won't be P2P anymore.

var WebTorrent = require('webtorrent')
var client = new WebTorrent({
  rtcConfig: { /* fill this in with your server details */ }
})

More info here: http://www.html5rocks.com/en/tutorials/webrtc/basics/

@feross feross closed this Feb 11, 2016
@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.