Deluge Forum

Hey All,

I've recently switched between a few clients, coming from uTorrent as my primary.

Could be growing pains or learning pains but, I cannot get any of the torrents to seed.

Things I've done:
* allowed in router
* allowed in firewall
* made sufficient "queueing" adjustments (no torrents are queued)
* set up ports and checked them and allowed them for in and out traffic within the router and firewall

Updates:
* I havent updated to the most recent as, I cannot find where/how I am meant to be getting that done from.

I have been reading several threads both in here and in other places but, they mosty all suggest I do things I have already done...

Any help would be magnificent.

Cheers.

Oh... In case someone asks.

Bandwidth info, top to bottom.
Global:
200
50
-1
-1
50
20

Per Torrent:
50
50
-1
-1

Queue:
20
3
17

Hi,

You are in the right path, but just as a reminder there is two possible way to make a torrent client seeding: the UPNP and fixed port.
The UPNP is supposed to seamlessly open the incoming port on the firewall and most of the time it works. But there is a lot of security issue with it and I strongly recommend to disable it on your ISP router.

The fixed port way asks more steps, a lot already done it seems
- Deluge: disable UPNP and fix an incoming port, better above 50000. you can select a range too but only one port at a time will be used. The range is mainly in case you have another application already using the port Deluge wants to pickup. Let's define the range 51000-51010. The outgoing port doesn't need to be defined, outgoing connection are not limited on windows and ISP router
- Windows: fix the IP of the computer. You can do it manually of with a an IP to MAC reservation on your router. The goal is to have the same IP for the computer running Deluge whatever the way
- Windows: on the Windows firewall, create a new incoming rules with the range defined above (51000-51010).
- ISP router: create a port forwarding rules to forward the range 51000-51010 to the fixed IP of your computer. This operation is called Port NAT, Port forwarding,... But the meaning is that any request from outside to these port have to be redirected to the fixed IP of your computer.

Once all is done, restart Deluge and make the connectivity test. For variable reasons it may failed so confirm the availability of Deluge incoming port by first open the preferences panel and check the ports it uses. Remember a range was defined so we need to know which one is in use (up to the next restart). Then use for example https://www.yougetsignal.com/tools/open-ports/ to check the availability

shamael wrote:Hi,

You are in the right path, but just as a reminder there is two possible way to make a torrent client seeding: the UPNP and fixed port.
The UPNP is supposed to seamlessly open the incoming port on the firewall and most of the time it works. But there is a lot of security issue with it and I strongly recommend to disable it on your ISP router.

The fixed port way asks more steps, a lot already done it seems
- Deluge: disable UPNP and fix an incoming port, better above 50000. you can select a range too but only one port at a time will be used. The range is mainly in case you have another application already using the port Deluge wants to pickup. Let's define the range 51000-51010. The outgoing port doesn't need to be defined, outgoing connection are not limited on windows and ISP router

Cheers for the reply Shamael,

Disable UPNP -- Most of the write-ups I've read suggest keeping this one open? I will look to make that adjustment soon.

Incoming port range is actually, 9-10 ports. I will select one of those as the incoming, and stick with that. When testing within Deluge, those ports get the green light.

I have actually JUST checked the cange of ports through "CanYouSeeMe" and, not all were available.... for whatever reason. I have JUST chnaged from the range to a singular visable port, and things SEEM to be working much more betterer...

I'll keep an eye on things.

Cheers again.

Disable UPNP: security reason is the best answer. Beside this main reason I think preferable to avoid UPNP doing the thing blindly, it makes the troublehooting a nightmare as you rely on the UPNP of the software used but on the UPNP implementation of your ISP router too. My last one set it OFF by default, finally ...

Incoming port range: Deluge will always use a single port. The range helps if another program using it already. If a single port is set Deluge will not start, if a range is set it will just try the next port of the range and so on. The First port of the range is the one in use if free, this is displayed in the GUI. So it's normal to only see one port opened in the range, the one Deluge picked up at start.

BTW if you are on private trackers (with quota), best is to deselect all the checkboxes next to UPNP. (DHT, etc. ). They all help to share in public mode without credits on your tracker's quota.

I use to test setup by taking some Linux distribution available on Bittorrent network (Ubuntu, mint, check respective official site). The column ratio will quickly shows you if your are good or not from outside w/o interaction with private trcker ration (such torrent are on public tracker, no hurt)

Update -- The seeding only really lasted for about 10 minutes or so. Not for long at all. Now, it is sitting on nothing again.

I truly have no idea what is wrong with this system as it is now

I remember things being far more straight forward and just working seamlessly with the OLD uTorrent client

What a shame...

Maybe nothing, it's always hard to know your true place in the seeder queue. BTW why not updating to 1.3.15 or 2.0.3 version?
An 2.0.3 unofficial release (with very good people) is done on this forum to make it happen, at least the official 1.3.15
It may not change anything but then you're not dealing with old stuff/issue. A variable out of the game at least

shamael wrote:[...]
An 2.0.3 unofficial release (with very good people) is done on this forum to make it happen [...]

That put a smile on my face, thank you my friend, appreciate that!

ICMC, please excuse me for butting in/interrupting your thread.

mhertz wrote:

shamael wrote:[...]
An 2.0.3 unofficial release (with very good people) is done on this forum to make it happen [...]

That put a smile on my face, thank you my friend, appreciate that!

You're famous now, deal with it

Thank everyone for the time taken to try to help me get this junk sorted... I've still had no luck at all.

IF it does start to seed, the max is something like 10-30 kbs

Speed tests give me a solid 19mbps up speed so... the bandwidth is there to use...

JUST updated to the latest offial version -- 3.15... Does not seem to have had any affect.