mhertz has retired from maintaining ltConfig, and I have taken over. I've added a profile that contains my settings covered in the ltconfig settings explanations in this forum section ([TUNING] ltConfig Settings and Explanations - https://forum.deluge-torrent.org/viewtopic.php?t=56921) and released ...

This is likely because you are not announcing to all the tiers and trackers contained within the torrent file, and rather just the primary - which does not aggregate the entire public tracker list, you can download ltConfig from my repository https://github.com/zakkarry/deluge-ltconfig/releases/tag/...

i turned it off, (https only) and added exceptions, i also think perhaps there might be something in about:config i changed with betterfox settings.

⚠ HTTP warning: Firefox's HTTPS-Only Mode blocks plain HTTP by default. Add an exception in about:preferences#privacy → HTTPS-Only Mode → Manage Exceptions.

Deluge Remote Modern
1.5.11

For some reason I can't get both https and http working in firefox, however Chrome is working fine.

The old .zip you sent me or whatever, that works.

Socks5 does not let incoming connections in most situations/implementations and because of this torrenting is unconnectable and you also miss out on connecting to certain seeds.

The proper setup is a VPN with port forwarding.

Check out the plugins - specifically https://forum.deluge-torrent.org/viewtopic.php?t=56921 I took over the fork of ltConfig - there is a setting in it where it with announce to all tiers and trackers, check both of them and it will use all the trackers. https://i.ibb.co/vCc1xmSz/pythonw-ko-Qawc-N8-...

It sounds like you might be using public trackers who regularly feed you outdated peers lists to inflate their seeding counts and upon updating the tracker you are fed a new list, or perhaps the DHT table as a source. Public torrents are typically inflated many times over for seed count and this is ...

There are scripts built into certain Deluge Docker containers, such as binhex's, that handle this, which you can then use the thin-client to connect to (as Docker does not natively provide the GUI), or you can write your own script to do so if you have coding experience. "listen_interface"...