submitted 1 year ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 1 points 1 year ago

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.

[-] [email protected] 1 points 1 year ago

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

[-] [email protected] 1 points 1 year ago

If Deluge us anything like Qbittorrent, you set the upload port manually by default.

[-] [email protected] 1 points 1 year ago

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.