Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign uptorrent.addPeer() disconnects soon after handshake #1333
Closed
Labels
Comments
This comment has been minimized.
This comment has been minimized.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have already set up
simple-peerinstances using Socket.IO. My plan was to add these viatorrent.addPeer()to remove the incredibly long delay (possibly due to bad tracker configuration) that my tracker server is taking to establish a connection between two peers.This approach sometimes works for the first few seconds of the torrent's video, but then the leecher receives a close event and does not receive or play the video anymore.
A test page can be found at: https://twoseven.xyz:8405/
I have also attached the relevant code of the client below.
What version of WebTorrent?
v0.98.24
What operating system and Node.js version?
Ubuntu 16.04
NodeJS v8.6.0
What browser and version? (if using WebTorrent in the browser)
Chrome v64.0.3282.186
What did you expect to happen?
The entire torrent is shared successfully via the manually added peer
What actually happened?
The torrent is not being transferred using the manually added peer. Occasionally, a part of the torrent is transferred before a
closeevent is emitted by the manually addedsimple-peer.Using
localStorage.debug="webtorrent,webtorrent:torrent,webtorrent:peer,simple-peer", I got the following:On the other client, I get:
Client