Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

How are you running it with Docker? Are you using --net=host or 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)

Do you have any port forwarding setup, or a firewall like iptables?

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.

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.

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.