Deluge Forum

Heya!

So I just setup my server on Ubuntu Server 18.04.4 LTS and installed Deluge 1.3.15. After a while and a few reboots I noticed that Deluge made at least 10 port-forwarding rules on different ports, here is an example:

Deluge 1.3.15 at 192.168.1.24:33239 33239 33239 TCP 33239 33239 192.168.1.24 ppp0.1 disabled
Deluge 1.3.15 at 192.168.1.24:33239 33239 33239 UDP 33239 33239 192.168.1.24 ppp0.1 disabled

I deleted all the rules made by Deluge and unchecked the boxes in WebUi prefrences that say "Use Random Ports" and I changed the ranges to 0-0. Than I rebooted again and tried to download some torrents. While they were downloading I checked the forwarding rules and again there were 2 new ones (one for TCP and one for UDP), I deleted them both while my torrents were downloading to see if they are even needed and they weren't. I refreshed the port forwarding page mutliple times to see if Deluge created some more and it didn't so I guess Deluge doesn't need them?

So how do I stop Deluge from creating more ports? Are they even needed? Im new to all this so any input would be appreciated-

Disable upnp/natpnp. If you untick random incoming port, then add a single port in both range fields, or a range if wanted, but not 0-0. If disabling upnp/natpnp then you need manually forward port for incoming connection if wanting incoming connections working, unless using VPN with port-forwarding, or no router.

mhertz wrote:Disable upnp/natpnp. If you untick random incoming port, then add a single port in both range fields, or a range if wanted, but not 0-0. If disabling upnp/natpnp then you need manually forward port for incoming connection if wanting incoming connections working, unless using VPN with port-forwarding, or no router.

Thanks thats just what I needed. Can I just ask why deluge creates port forwarding rules? Right now I set it up as you told me and deleted all port forwarding rules and it works fine without them.

You're welcome mate

Pretty much all torrent-clients(except rtorrent and a few select others probably) has upnp enabled which sets portforwarding up for you automatically, so you get better connectivity in the torrent swarm(as you then have incoming connections also, instead of only outgoing ones). It can sometimes duplicate the port-forwards and if the port change then new rules made etc. So either you disable upnp/natpnp and set up portforwarding yourself in router or you let upnp/natpnp do it. If deleting the rules upnp/natpnp makes and not setting them up manually, as you did before, then you will have less connectivity, but if e.g downloading popular torrents then it will still work fine, and there mostly is for improving upload connectivity(it effects download speed too if the torrent is less popular or have bad seed-to-peer ratio, as when you get throttled/punished for not uploading so much, and if not a bunch of available seeds then will affect you more there, but will still work(you're rotated-in regardless(unthrottled) just under-prioritized compared to other more uploading peers) , just slower). You can read up on portforwarding, incoming connections and uploading with some quick googling if interested.

Thank you for taking the time to explain it so well! I'll test it with less popular torrents than and see if I need to add the rule or not. Thanks again for your time!

You're of course very welcome mate