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

not able to download using S3 torrent #1474

Open
srmitharwal opened this issue Aug 17, 2018 · 7 comments
Open

not able to download using S3 torrent #1474

srmitharwal opened this issue Aug 17, 2018 · 7 comments

Comments

@srmitharwal
Copy link

@srmitharwal srmitharwal commented Aug 17, 2018

What version of WebTorrent?

0.102.1
What operating system and Node.js version?

Ubuntu 17.04 Server, Nodejs 10.8.0

What did you expect to happen?
I want to download the file using s3 torrent .

What actually happened?
I am trying to download the files which are in Amazon S3 using web torrent client. I am able to successfully generate torrents for them but not able to download. File is getting download by using same S3 torrent if I use some other torrent client.

@srmitharwal srmitharwal changed the title no able to download using S3 torrent not able to download using S3 torrent Aug 17, 2018
@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Aug 24, 2018

@srmitharwal

This comment has been minimized.

Copy link
Author

@srmitharwal srmitharwal commented Aug 24, 2018

Yes, I am using the same approach. I went through the #979 but as mentioned in the amazon BitTorrent doc, we do not need to seed our public file. Amazon takes care of that , we just have to generate torrent and we can download it using any torrent client. I used peerflix to download the file, its working fine. I went through the webtorrent code, I figured out that it is able to identity the peers but not able to set up tcp connection. WebTorrent client is sending SYC to AWS but it is not receiving SYN-ACK from AWS.

@stale

This comment has been minimized.

Copy link

@stale stale bot commented Nov 22, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Nov 22, 2018
@stale stale bot closed this Nov 29, 2018
@mistersdevelopment

This comment has been minimized.

Copy link

@mistersdevelopment mistersdevelopment commented Jan 21, 2019

I have tried webtorrent-cli (1.12.3 (0.103.0)) and webtorrent-hybrid's CLI (1.12.3 (0.103.0)) and both were unable to download a file from S3. I'm not sure why #979 is locked and closed since the issue is not resolved. Deluge was able to download the file from S3 correctly.

@DiegoRBaquero DiegoRBaquero reopened this Jan 21, 2019
@stale stale bot removed the stale label Jan 21, 2019
@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Jan 21, 2019

Can anyone post an S3 torrent link? The torrent metadata points to the S3 file as a webseed?

@mistersdevelopment

This comment has been minimized.

Copy link

@mistersdevelopment mistersdevelopment commented Jan 22, 2019

Here is an example link: https://aft-vbi-pds.s3.amazonaws.com/LICENSE?torrent. This is a license in a public data set in S3 (https://registry.opendata.aws/amazon-bin-imagery/). You can see the non-torrent version here: https://aft-vbi-pds.s3.amazonaws.com/LICENSE.

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Jan 22, 2019

Torrent only has their tracker server announce and the file name. So the problem, as @srmitharwal said, it's connecting to the TCP peer they provide.

If anyone would like to attempt to fix this, I'll review the PR.

This is something that won't work on the browser. But it'd be interesting to check if the original file is CORS enabled and use the link as a webseed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.