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

No Seeding at all. #6853

Open
absolutep opened this issue Apr 8, 2022 · 7 comments
Open

No Seeding at all. #6853

absolutep opened this issue Apr 8, 2022 · 7 comments
Milestone

Comments

@absolutep
Copy link

Describe the bug

Since past two weeks, seeding has significantly deteriorated.

It doesn't matter if you become a exit node or not. It doesn't matter if you are anonymous or non-anonymous.

Before that the problem was #6801

To Reproduce

Download any newly released or old torrent.
Seeding will only happen till download is going on and then it stops altogether. Even though, seeders & leecher number regularly update.

Expected behavior

Tribler should be able to seed any & all torrents in non-anonymous mode.

Screenshots

Untitled

Desktop (please complete the following information):

  • OS: Windows 10 - up-to-date
  • Tribler's version 7.11.0

Additional context

I think Tribler is still suffering from the lack of exit nodes as well as the issue of torrent clients rejecting requests (from Tribler exit node) due to DHT calls coming from single source or port etc.. Both of which has been discussed in length by Tribler team.

Even in non-anonymous mode when it is supposed to work as a normal torrent client I am facing such issue.

As a possible solution, I am requesting Tribler team to look into either #6743 or #6737 - to check if they are viable & applicable solutions to solve seeding issue or not.

@DominikNovosel
Copy link

Ditto. This is what my token balance looks like after downloading some stuff and letting it seed overnight undisturbed:
image
It's not great, to say the least.

@absolutep
Copy link
Author

a reminder for tribler team

@drew2a
Copy link
Contributor

drew2a commented Jul 4, 2022

@absolutep thank you for opening an issue.

We didn't do anything related to seeding (except #6736) so, seeding should not be affected by changes from the source code.

I tried to download Ubuntu and it works perfectly (Tribler has been run from the main branch):

image

Could it be something related to your local settings?

@Solomon1732
Copy link
Contributor

Solomon1732 commented May 14, 2023

For some reason mine doesn't seed as well. I'm using a fresh install of 7.12.1 on Windows 10.
Edit: I've been running it for days.
image

The only setting I changed (as far as I remember) is to activate minimize to tray. Here are my settings:
image
image
image
image
image
image
image

@synctext
Copy link
Member

synctext commented Nov 20, 2023

Sorry for the long wait! We're re-visiting all known old bugs and will spend multiple months fixing them all. Critical issue is always reproducing them. If we manage to re-produce the issue, it will be solved 🐛

@absolutep That is very insightful statistics! Your report from on 8 Apr 2022 shows only 1 active seeding swarm, the remainder is idle. Are you seeding over 10 or 15+ swarms? Did things get better with the latest 7.13 release? We have a fresh 7.13.1 for you soon to try.

@Solomon1732 You issue seems to be different. In anonymous mode you only seed using a novel "end-to-end" encrypted protocol, with Tor-like anonymizing proxies. Only Tribler clients support this. So you will only able to seed to other Tribler client. Only 50.000 or so are active currently. Please keep it up and help spread this new protocol 🥇

Copy link

This issue has not seen activity for 60 days. It is now marked as stale. Please provide additional information or this issue may be closed in the future. We value your contribution and would love to hear more!

@qstokkink
Copy link
Contributor

I tried to find more information and I found that there has been a discussion on our upstream dependency libtorrent that addresses this issue: arvidn/libtorrent#6512 (including part of the Tribler team). The issue is still open though.

Provided that I interpreted the issue correctly, it seems like upgrading to the libtorrent 2.x series will fix this issue.

@qstokkink qstokkink added this to the 8.1.0 milestone Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

6 participants