Deluge Forum

Hello, I'm having a strange problem.I get the "No incoming connections" message on the bottom of the screen.However, the torrents seem to download, although they seem suspiciously slow.When I tried the "Test Active Port" in "Preferences" , I get a yellow exclamation mark.Has this happened to anyone else?

emiliorodo wrote:Hello, I'm having a strange problem.I get the "No incoming connections" message on the bottom of the screen.However, the torrents seem to download, although they seem suspiciously slow.When I tried the "Test Active Port" in "Preferences" , I get a yellow exclamation mark.Has this happened to anyone else?

You need to forward your active listen port in your router.

andar wrote:You need to forward your active listen port in your router.

Why would I have to do that? I thought Deluge supports uPnP, doesn't it? Or is that not what Preferences/Network/Network Extras/UPnP means? My router does support uPnP, yet I am getting the same ("No incoming connections") issue...

Any ideas what I am doing wrong?

Deluge does support UPnP, however it doesn't mean it works with all routers. What router do you have?
Manually forwarding your port is normally the easiest option unless you're prepared to compile deluge with UPnP debugging enabled.

johnnyg wrote:Deluge does support UPnP, however it doesn't mean it works with all routers. What router do you have?

SMCWGBR14-N by SMC (http://www.smc.com/index.cfm?event=view ... 8&pid=1634). So far I've had no UPnP-related issues with this router, and I've been running other BT clients as well (e.g. uTorrent). I'd be amazed if it were the router's fault.

At any rate, I see there's been a new firmware release for my router; will flash that up and report back. My gut feeling is that I should not expect a different result though.

Manually forwarding your port is normally the easiest option unless you're prepared to compile deluge with UPnP debugging enabled.

That, unfortunately, doesn't work for random ports. I like the random ports feature.

Aqualung wrote:At any rate, I see there's been a new firmware release for my router; will flash that up and report back. My gut feeling is that I should not expect a different result though

Just as I thought, no change after flashing the router.

Any other SMCWGBR14-N user out there experiencing non-functional UPnP?

Again, I am running Deluge 1.0.5, so it may very well be that 1.1.0 (final) fixes that. Will try v. 1.1.0 later, once I get to compile/build it for my headless device.

I'm having the same problem with my router setup. I can't get any incoming connections despite forwarding the active port on my routers. Now granted my network setup is a little nonstandard as I have 2 routers to forward through instead of the usual one. They are a WRT610N and a WRT54GL. The really strange thing is that Transmission has no problems setting up a connection through both routers using UPNP. Any help resolving this issue would be much appreciated.

Aqualung wrote:

Aqualung wrote:... it may very well be that 1.1.0 (final) fixes that. Will try v. 1.1.0 later, once I get to compile/build it for my headless device.

Nope, Deluge 1.1.0 doesn't fix that.

I have the same issue where I get "No Incoming Connections" and using UPnP for port forwarding with random ports. Everything seems to work properly if the port is manually specified. However, when using random port, only the TCP protocol is forwarded, not the UDP.

I'm using DD-WRT firmware for my router.

I've attached a screenshot of DD-WRT that shows this behavior.

The first two Deluge entries are when I manually specified port 49422. As you can see, both TCP / UDP are defined.

However, the other two entries are when I had Deluge randomized the port, which you can see only TCP is defined.

So I'm assuming the solution is to get the UDP port announced to the router.

Upon playing with around with it more...

If I make define a different port, say from 42425 to 42425 (so the same port), DD-WRT will only make TCP entry, but it's weird that the Test Active Port will show a green check mark.

So I'm not quite sure what is going on. It definitely has something to do with using randomized ports though.