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 updoes client.add seed after completion? #638
Closed
Labels
Comments
This comment has been minimized.
This comment has been minimized.
|
I assume you're using WebTorrent in Node.js. WebTorrent currently doesn't support the traditional methods of NAT hole punching (UPnP and NAT-PMP) that most torrent clients support. There's an issue about this here: #195. This might explain why peers outside your local network are unable to connect to your client. As a workaround, you can set up Port Forwarding on your router. |
This comment has been minimized.
This comment has been minimized.
|
This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
client.adddoes is not seeding after the torrent is done. It does show up as a Peer, but none of the other peers seem to be able to connect to it.Do I have to do anything special after the torrent is done or should I begin an explicit
client.seedafter the torrent is done? Does DHT need to be set to true?