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

How start seed torrents throught webttorrent-tracker #1133

Closed
dxpsite opened this issue May 25, 2017 · 2 comments
Closed

How start seed torrents throught webttorrent-tracker #1133

dxpsite opened this issue May 25, 2017 · 2 comments

Comments

@dxpsite
Copy link

@dxpsite dxpsite commented May 25, 2017

It is necessary to understand the sequence of actions for distributing torrents through the webtorrent-tracker.
For example: the tracker is running on port 8111, create the torrent with the create-torrent command with the --announce parameter
create-torrent --urlList 'https://myhost.com/converted.mp4' converted.mp4 > converted.torrent'.
Torrent file created..
Then start seed this new torrent file with command:
webtorrent seed https://myhost.com/converted.mp4.torrent --announce http://myhost.com:8111/announce
and got error (or not):

verifying existing torrent data...

torrent downloaded successfully from 1/3 peers in 0s!

webtorrent is exiting...

How the webseed works fine. But the number of peers does not increase with the increase in seeders - shows 1 peer - webseed only(.
What did I miss here?

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented May 26, 2017

  • Which type of tracker are you running? ws and/or tcp and/or udp?
  • From which type of peers are you seeding? webtorrent (nodejs, so tcp and udp) or webtorrent-hybrid (tcp, udp AND webrtc)
  • From which type of peers are you downloading? webtorrent (nodejs, so tcp and udp) or webtorrent-hybrid (tcp, udp AND webrtc) or browser (webrtc only)
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Apr 24, 2018

This issue appears stale since it has been open for a while with no activity. I'm going to close it for now. If this is still issue, please feel free to leave a comment or open a new issue.

@feross feross closed this Apr 24, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 23, 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
3 participants
You can’t perform that action at this time.