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

Unsupported tracker protocol #1467

Closed
stilllife00 opened this issue Aug 11, 2018 · 1 comment
Closed

Unsupported tracker protocol #1467

stilllife00 opened this issue Aug 11, 2018 · 1 comment

Comments

@stilllife00
Copy link

@stilllife00 stilllife00 commented Aug 11, 2018

What version of WebTorrent?
0.102.1

What browser and version? (if using WebTorrent in the browser)
Chrome 68

What did you expect to happen?
The torrent starts downloading

What actually happened?
The progress is stuck at 0% and I got many errors in the torrent.on('warning') callback

Error: Unsupported tracker protocol: http://94.228.192.98:80/announce
    at eval (client.js:105)
    at Array.map (<anonymous>)
    at new Client (client.js:89)
    at Discovery._createTracker (index.js:153)
    at new Discovery (index.js:64)
    at Torrent._onListening (torrent.js:335)
    at Torrent._onParsedTorrent (torrent.js:274)
    at eval (torrent.js:234)
    at Item.run (browser.js:153)
    at drainQueue (browser.js:123)
streamer.js:21 Error: Unsupported tracker protocol: http://exodus.desync.com:6969/announce
    at eval (client.js:105)
    at Array.map (<anonymous>)
    at new Client (client.js:89)
    at Discovery._createTracker (index.js:153)
    at new Discovery (index.js:64)
    at Torrent._onListening (torrent.js:335)
    at Torrent._onParsedTorrent (torrent.js:274)
    at eval (torrent.js:234)
    at Item.run (browser.js:153)
    at drainQueue (browser.js:123)
streamer.js:21 Error: Unsupported tracker protocol: udp://coppersurfer.tk:6969/announce
    at eval (client.js:105)
    at Array.map (<anonymous>)
    at new Client (client.js:89)
    at Discovery._createTracker (index.js:153)
    at new Discovery (index.js:64)
    at Torrent._onListening (torrent.js:335)
    at Torrent._onParsedTorrent (torrent.js:274)
    at eval (torrent.js:234)
    at Item.run (browser.js:153)
    at drainQueue (browser.js:123)

Note that the same magnet file works like a charm in the Desktop APP

magnet:?xt=urn:btih:6CC239FE3D6620758ABA38AC4A68AB43955A621C&dn=The+100+S01E01+HDTV+x264-2HD&tr=udp%3A%2F%2Ftracker.istole.it%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr=udp%3A%2F%2Fopen.demonii.com%3A1337%2Fannounce&tr=udp%3A%2F%2Fexodus.desync.com%3A6969%2Fannounce&tr=http%3A%2F%2Fexodus.desync.com%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.secureboxes.net%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.nwps.ws%3A6969%2Fannounce&tr=http%3A%2F%2F94.228.192.98%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.zer0day.to%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fcoppersurfer.tk%3A6969%2Fannounce
@KayleePop

This comment has been minimized.

Copy link
Contributor

@KayleePop KayleePop commented Aug 11, 2018

Those messages are because only websocket trackers work in the browser (not udp or http). You need at least one to connect to other peers in the browser.

Webtorrent-desktop can handle those types of trackers just fine though, so that's why it works there.

I think it's OK for you to use these public trackers.

  • wss://tracker.btorrent.xyz
  • wss://tracker.openwebtorrent.com
  • wss://tracker.fastcast.nz

Just add them to the magnet link like this

&tr=wss://tracker.btorrent.xyz&tr=wss://tracker.openwebtorrent.com etc

You don't have to remove the others, they just won't work in the browser, and they'll still give you the annoying errors. They won't break anything though.

 

I still don't think it will work though, because there has to be at least one client seeding the torrent for you to be able to download it, and that client has to be compatible with webtorrent (webtorrent-desktop, webtorrent in browser, or vuze)

They also have to be using one of the same trackers as you I think, so if you're just trying to download a normal torrent in the browser, it likely won't work. (you can try after adding the websocket trackers though)

More info here https://webtorrent.io/faq

@lock lock bot locked as resolved and limited conversation to collaborators Nov 9, 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.