Cannot seed torrent created from folder with webtorrent cli about webtorrent-cli HOT 6 CLOSED

So, there's a bit of a misunderstanding of the commands here. webtorrent create /my/path will create a torrent file for the contents of /my/path. That part is correct.

But when you use webtorrent seed /my/path2, you're actually creating a torrent for /my/path2 and seeding the files there. So you don't want to run webtorrent seed somefile.torrent as then you'll be seeding the torrent file itself.

Your webtorrent seed ~/Downloads/test_dataset command is the right one to use.

But you have another problem, which is that you used --private when you created the initial torrent file, but not when you were seeding, so you ended up creating a different torrent file. You need to use consistent flags. I recommend not using --private as that just prevents the use of the DHT to find peers, which is not what you want.

Hope this helps!

from webtorrent-cli.

from webtorrent-cli.

@rom1504 no I'm not sure it does what I want. There weren't many notes that I could find explaining what it does and googling various combinations of "private torrent file" weren't what I was looking for.

from webtorrent-cli.

from webtorrent-cli.

not seed publicly yet, only to those whom I gave the torrent. I guess it might mean only use private trackers or something?

Would that flag have caused the behavior I saw?

from webtorrent-cli.

Hello. This instruction does not work for me as for the author, even without --private in the latest version.

And also the code below does not work ... instant.io does not see the link.

const WebTorrent = require('webtorrent-hybrid')

const client = new WebTorrent()
const filePath = __filename

console.log('filePath:', filePath)

client.seed(filePath, torrent => {
console.log('torrentId (info hash):', torrent.infoHash)
// console.log('torrentId (magnet link):', torrent.magnetURI)
})

from webtorrent-cli.