Used to sail the high seas in the days of TPB and Demonoid (when they were still good). Started again recently with a servarr stack with Deluge on docker but didn’t realize it wasn’t seeding properly and now my torrentleech ratio is in grave danger.
What might I be missing in my network config? Docker has all ports exposed and Deluge has uPnP enabled. Downloads work just fine and torrents periodically connect to peers but nothing ever actually uploads.
You must log in or register to comment.
How are you running it with Docker? Are you using
--net=hostor manually binding the ports in question?A couple things I would check:
- Check Deluge’s error logs: https://dev.deluge-torrent.org/wiki/Faq#EnableDelugeLogging
- Check Deluge for what ports it is configured to use then:
- See if that port is bound (on Linux you can use
sudo lsof -i:<portnumber>) - See if there is any traffic running over that port (tcpdump or ngrep)
- See if that port is bound (on Linux you can use
Do you have any port forwarding setup, or a firewall like iptables?
Right out the gate I want to express gratitude- over on reddit the expected response to my question would probably be something along the lines of “google it yourself” or “if you don’t already know how, you shouldn’t try to learn”. It’s nice to see that this place lives up to the label of “community” 😁
Unfortunately, wasn’t able to glean anything from the logs but your port binding stuff did prompt me to try host mode networking instead of individual bindings (previously was doing the expose ports randomly option through portainer). This didn’t have an immediate positive effect but it may have suggested that my issue is even dumber than originally anticipated- I think the files downloaded so far fit two categories that contribute to my low ratio: obscure stuff that nobody else wants and big freeleech stuff with so many seeds that nobody gets down to my box in the pile. This I confirmed by grabbing a high leech/low seed file from a public tracker and noting traffic on completion.
Upload still seems slow even with the public test so that may still need investigation but if I can find some stuff that people are actually downloading, I might still be able to pull my ratio out of the dumpster (hopefully before getting booted 🤞)
Probably stating the obvious, but keep the obscure stuff around! You might not get upload immediately but the longer you seed it, the more chance someone else who wants it will come along and you get some of the upload. the most real upload I’ve ever gotten on TL (talking 1.2/1.5/1.9 ratio, absolutely insane ratio to have on a home network for a TL torrent imo) was from submitting a reseed request for several super obscure boxsets that had other leechers and no seeders.
but do watch out for downloading any more non-freeleech stuff from TL if your ratio is already poor, as that’ll dig you into a bigger hole than just letting what you’ve already grabbed seed.
Are you getting upload on public torrents with a large number of leechers, like YTS or similar? I’d test that first.
If you are getting upload on a large public torrent, then it’s because TorrentLeech is really hard to get real upload on; your best bet is to seed your TL torrents as long as possible (ideally forever) and build your ratio by buying upload from the points store.
If you’re not able to upload to public torrents then yeah it’s probably a setup issue.
This seems to be the thing. Thank you!
Glad I could help! Most of my TL ratio comes from the seeding time point system, but all of the torrents I have real ratio on are freeleech TV boxsets (which I find TL is pretty generous about providing). Seeding large-file-size torrents gives a bonus to the points generated, so if you have the space and find yourself gaining points too slowly to bring your ratio where you want it, I’d recco nabbing a few of those boxsets to seed long term as well.
Definitely gonna have to lean on that myself as well. Already looking at a few of the big freeleech farms- I don’t have infinite space but there’s always room for a couple hundred gigs of Studio Ghibli lol
The main thing you need to double-check & possibly fix is to make sure you are fully connectable (port forwarded). So for example you should check your torrent client’s incoming connection port with a external 3rd party website e.g. https://www.canyouseeme.org/, https://www.yougetsignal.com/tools/open-ports/, etc. If the test fails then you’ll need to set up a port forward in your network router and check that other software isn’t interfering (firewall, anti virus/malware software, etc.).
There are other things you can look into though being fully connectable is the most important one.
The internal forums in TL also discuss this stuff.
I’ve been having slow upload with Deluge 2.1, but I always attributed that to my new vpn provider potentially throttling certain traffic. It didn’t quite occur to me that a Deluge configuration could be a culprit as it cooperated in the past.
To your knowledge, does Deluge use any uncommon network ports for torrent upload? I’ll have to look into this in any case.
If Deluge us anything like Qbittorrent, you set the upload port manually by default.
Both torrent clients will try to automatically create a port forward via UPnP / NAT-PMP but that only works on networks that have that enabled. Otherwise yes the port forward must be manually created.
All mine were default afaik. Ended up primarily being low traffic torrents but I’ll continue to investigate to make sure there aren’t any other bottlenecks
