bittorrent-tracker

I solved this issue by implementing a webtorrent tracker[1] client. Signalling server is still needed, but with this approach any webtorrent tracker can act as one. [1]: https://github.com/webtorrent/bittorrent-tracker

How about webtorrent's tracker? There is no Docker file but it should be doable https://github.com/webtorrent/bittorrent-tracker

Webtorrent Use a free signalling server from the webtorrent community. You can skip the torrent part of the implementation and just use the signalling, it's awesome. You can use a libraries like: https://github.com/webtorrent/bittorrent-tracker https://github.com/subins2000/p2pt to get started. For me, I found the protocol is simple enough where I just use small vanilla javascipt implementation to talk to the websocket servers to generate the signalling messages. I wish more people knew about this and realize how easy it can be to bring WebRTC to their applications. List of some free webtorrent trackers: wss://tracker.openwebtorrent.com wss://tracker.files.fm:7073 wss://tracker.webtorrent.dev ---> Usage stats for the last one: https://tracker.webtorrent.dev Some free stun servers for NAT traversal: stun:stun.cloudflare.com stun

You may browse the github issues. Both ipfs and webtorrent have the same core issues: Below are some examples https://github.com/webtorrent/webtorrent/issues/1721 https://github.com/webtorrent/webtorrent/issues/903 https://github.com/webtorrent/bittorrent-tracker/issues/199

Maintainer of WebTorrent here: the problem is on how WebRTC works and its various settings. Using a good STUN servers with your own tracker server should be the best solution. Using TURN servers also helps peers connect, but then it's no longer real P2P. Current work is being dedicated to updating the code base to ES6 and soon to ES7, which will improve many things and force recent versions of Node/Browsers to be used. See https://github.com/webtorrent/bittorrent-tracker/issues/199