Deluge

Hi,

Please tick the option in queue "do not count slow torrents".

please report it through the store, I cannot see how it can be legit. I'll do the same

Thx!

Not to my knowledge. Hit and run comes from Tracker update, no issue on the tracker? Is your HW sufficent enough to hold all tracker update sent?
In the tracker tab, error, nothing?

Maybe the number of torrent loaded. Taking my example I've limited HW resources on my server (RPI) and cannot go above a fixed amount of torrent. This is due to the RPC protocol and timeout associated. Is the logging enabled on the server daemon? If nothing obvious SSH the server and use deluge-cons...

What's the type of hardware/OS of the server and how many torrents loaded?
Is the web access possible? if not may your remove the offending one through the command line?

it depends about the way the D/L is blocked. Maybe the protocol is not allowed or only 80/443 ports are working. There is many thing that can be done to avoid such traffic and each situation is local specific.

The queue has several option that may help
"queue new torrents to top" or maybe better "do not count slow torrents". This is available in the GTK GUI but I'm sure the core.cof can be altered to enable them too.

Hi,

What about running Deluge & Deluge-web as a service ? So the RDP session is out of the problem
https://deluge.readthedocs.io/en/latest ... rvice.html

Hi, Well big question. The answer depends of many factors like the your line capacity, your router (ISP or your own), etc. Taking my example I can kill my line if I set too many connections per torrent. That said have you already checked the plugin LTconfig? There are a lot of thing you can use ther...

thx for sharing it