Incoming ports keep on changing

[donut23]

I have set up deluge to run on a debian machine using deluged and the web ui (following this guide https://deluge.readthedocs.io/en/latest ... rvice.html).

I've set the incoming and outgoing ports to not be random, manually setting them. Now here's the weird part.

Let's say I've set the port to 64885 (incoming and outgoing). It starts on that port on the machine. I can see via telnet that the port is being used by deluge. I have port forwarding set up on my router that routes an external port that that port. They are the same port from start to finish, 64885.

The weird part is that the tracker I'm using never sees that port. It always sees the port "plus a number." It just increments. So it's never seen 64885, but it does see 64886, 64887, 64888, and so on. It seems like it's just incrementing ports. All while the port on the linux machine has stayed the same. This means I need to keep on updating the port forwarding for things to work.

Anyone have any ideas on why the port seen by the tracker is not the same as set by deluge on the linux box? (again, it's the same port that is forwarded from the router right to the linux machine).

Thanks!

[ambipro]

You generally do not need to set the outgoing port at all, leaving that random is generally fine unless you have a very specific network setup that blocks traffic outgoing and requires configuration.

As far as setting the incoming, that would be the port that requires forwarding in your router and that peers connect to download from you.

Setting incoming and outgoing as the same is not a thing.

Basically, set incoming to the port you want, and outgoing to random (assuming you dont have specific reasons you would need otherwise) do not set them to the same thing though. This is likely why you're seeing this behavior.

[donut23]

Thanks for the reply!

I've changed the settings to be a random outgoing port.

Unfortunately, that doesn't seem to work. Deluge is still listening on 64885 but the tracker sees the incoming port being advertised as 64888.

After changing settings, I've fully restarted the service and also have tried rebooting the machine hasn't helped either.

Port forwarding hasn't changed and is still set up correctly (can see it coming through the original port).

[ambipro]

I'm not really sure what would be causing this, it sounds like you should maybe check the console/logs for what port is being reported by the daemon on startup.

Does test active port return a checkmark? If so, then the tracker is wrong and Deluge is fine.