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

Can't seed torrent #813

Closed
pietrovismara opened this issue May 22, 2016 · 6 comments
Closed

Can't seed torrent #813

pietrovismara opened this issue May 22, 2016 · 6 comments

Comments

@pietrovismara
Copy link

@pietrovismara pietrovismara commented May 22, 2016

  • WebTorrent version: 0.93.3
  • Node.js version: 5.10.1

I'm having a problem with a webtorrent based client, and a bittorrent-tracker tracker.

I have this options for seed:

const seedOptions = {
    announceList: [
        [
            `udp://${config.tracker.address}:${config.tracker.port}/announce`, 
             `http://${config.tracker.address}:${config.tracker.port}/announce`,
            `wss://${config.tracker.address}:${config.tracker.port}/announce`
        ]
    ]
};

And i seed like this:

client.seed(path, seedOptions, (torrent) => {
            // Creating a torrent file
            fs.writeFile(`${torrent.name}.torrent`, torrent.torrentFile, function () {
                console.log("written");
            });
});

My tracker answer says:

got start message from ip:port
got complete message from ip:port

If i try to load the generated torrent into Transmission or any torrent client, i see no active seeders and download doesn't start.

Am i missing something?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented May 23, 2016

udp:// and wss:// trackers do not have a /announce at the end of the URL. Can you try again after removing that?

Also, can you post the results of these commands:

npm install parse-torrent -g
parse-torrent /path/to/your/file.torrent
@pietrovismara

This comment has been minimized.

Copy link
Author

@pietrovismara pietrovismara commented May 23, 2016

I made various test, i think the problem is because i didn't forwarded the ports.
After forwarding the correct port, seeding is working.
I saw an issue on this project for nat upnp support, do you plan to implement it any soon?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented May 23, 2016

It's on the list, but there's lots to do.

On Mon, May 23, 2016 at 03:04 Pietro Paolo Vismara notifications@github.com
wrote:

I made various test, i think the problem is because i didn't forwarded the
ports.
After forwarding the correct port, seeding is working.
I saw an issue on this project for nat upnp support, do you plan to
implement it any soon?


You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#813 (comment)

@pietrovismara

This comment has been minimized.

Copy link
Author

@pietrovismara pietrovismara commented May 23, 2016

Well, i spent various hours yesterday trying to find a working solution for nodejs, but all existing modules are old and not mantained, and no one could work with my router.
Anyway i'm working on a project which uses Webtorrent as the core feature, so if i will work out some solution on my own, i'll let you know, who knows if i can make a good pull request and help this awesome project.
Closing, thank you for your time.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented May 23, 2016

@pietrovismara Awesome, sounds good

@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 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
2 participants
You can’t perform that action at this time.