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

Problem seeding using tcp from the server side #460

Closed
thehobbit85 opened this issue Oct 11, 2015 · 13 comments
Closed

Problem seeding using tcp from the server side #460

thehobbit85 opened this issue Oct 11, 2015 · 13 comments
Labels

Comments

@thehobbit85
Copy link

@thehobbit85 thehobbit85 commented Oct 11, 2015

I'm trying to create a simple file seeding using some default trackers but even after the seed has "started" and the callback is being called, when I try to leech the file using the magnet link and uTorrent/Transmission/WebTorrent (Tried all three) the download never starts and it stays stuck on "downloading metadata"

I tried seeding and leeching from a variety of machines (mac, linux and windows) and I just never start downloading.

This is the code I'm running (I'm using webtorrent 0.62.2):

var WebTorrent = require('webtorrent')

var opt = {
  announce: [['udp://tracker.openbittorrent.com:80', 'udp://open.demonii.com:1337', 'udp://tracker.coppersurfer.tk:6969', 'udp://tracker.leechers-paradise.org:6969']]
}

var client = new WebTorrent(opt)
var fileName =  './Screen.png'
client.seed(fileName, opt, function (torrent) {
  console.log(torrent.magnetURI)
})
@eliooses

This comment has been minimized.

Copy link

@eliooses eliooses commented Nov 3, 2015

I think what this issue are the same thing of many others:

udp and dht trackers is not compatible with webtorrent peers seeds.

@thehobbit85

This comment has been minimized.

Copy link
Author

@thehobbit85 thehobbit85 commented Nov 3, 2015

Ok, thats good to know....
And how can that be fixed?
If I run my own tracker (the webtorrent one) can that be solved?

@eliooses

This comment has been minimized.

Copy link

@eliooses eliooses commented Nov 5, 2015

You must keep calm and wait for an update. Are devs works in this, here in /feross/webtorrent/ and other repositories:

https://github.com/jhiesey/webdht

@hualiwang

This comment has been minimized.

Copy link

@hualiwang hualiwang commented Jan 8, 2016

As I think, webrtc can not talk to tcp and udp protocol.

@rom1504

This comment has been minimized.

Copy link
Member

@rom1504 rom1504 commented Jan 8, 2016

it is definitely possible to seed in node and download in uTorrent/Transmission/WebTorrent

if that doesn't work, it's a bug. (But I think it does work)

@madd512

This comment has been minimized.

Copy link

@madd512 madd512 commented Jan 8, 2016

I think you want to be using webtorrent-hybrid if you want compatibility with the bittorrent network

@feross feross added the question label Jan 9, 2016
@hualiwang

This comment has been minimized.

Copy link

@hualiwang hualiwang commented Jan 9, 2016

It will be great if can seed in node and download in utorrent/webtorrent(chrome)
but I tried many times ,never successed.
but as you said , I will try it again .

@solderzzc

This comment has been minimized.

Copy link
Contributor

@solderzzc solderzzc commented Jan 9, 2016

Are you seeding in Nodejs behind NAT?

It will be great if can seed in node and download in

utorrent/webtorrent(chrome)
but I tried many times ,never successed.
but as you said , I will try it again .


Reply to this email directly or view it on GitHub
#460 (comment).

@hualiwang

This comment has been minimized.

Copy link

@hualiwang hualiwang commented Jan 9, 2016

I seeding in nodejs in public IP(digitalocean vps)
I try it again , seeding in nodejs ,and download in chrome . but still failed.
v0.71.3

webtorrent

@solderzzc

This comment has been minimized.

Copy link
Contributor

@solderzzc solderzzc commented Jan 9, 2016

I guess your webtorrent command use different tracker other than
Instance.io.

On Fri, Jan 8, 2016 at 8:10 PM, hualiwang notifications@github.com wrote:

I seeding in nodejs in public IP(digitalocean vps)
[image: webtorrent]
https://cloud.githubusercontent.com/assets/16126643/12214306/bacda042-b6c9-11e5-8f5c-055556c1faa2.jpg

I try it again ,still failed.
v0.71.3


Reply to this email directly or view it on GitHub
#460 (comment).

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Jan 9, 2016

@hualiwang You are seeding in TCP/UDP and trying to download in WebRTC. It just won't work.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jan 9, 2016

The current recommendation is to make sure that you're seeding using webtorrent-hybrid, which can seed to browser peers.

I am going to work on making that work a lot better soon (i.e. it should use Electron), since it's really hard to install right now.

@feross feross closed this Jan 9, 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
8 participants
You can’t perform that action at this time.