"peer-port" in settings.json file differs from the one being showed in Web client or transmission-remote GUI

[Lucho-U]

What is the issue?

I'm running latest version 4.0.0 of Transmission in a QNAP NAS, downloaded from here:
https://www.myqnap.org/product/transmissionbt-4/

I'm connecting to the transmission-daemon in my PC using either the Web client or transmission-remote GUI.

For some reason, the "peer-port" that I have directly configured in settings.json file does not match what is being showed in Web client or transmission-remote GUI. I'm adding screenshots.

Thank you.

Which application of Transmission?

transmission-daemon

Which version of Transmission?

4.0.0

[BowlesCR]

Any chance you changed the port at runtime? The settings.json doesn't get written out until you shutdown the daemon, so it might have stale values in it while the daemon is running.

[Lucho-U]

Any chance you changed the port at runtime? The settings.json doesn't get written out until you shutdown the daemon, so it might have stale values in it while the daemon is running.

Hi @BowlesCR I have tried to change the port 44743 back to 44741 through Web client and remote GUI and then saved, but if I go back to see if it got changed, the port is again at 44743. Just to double check I have stopped the daemon in my NAS and it still has the port 44741 in settings.json, then I have started the daemon again and connected through Web client/Transmission Remote GUI, but I see the same behavior, port 44743 is being showed there and 44741 in settings.json. It's like the port in settings.json is being added +2

Are you running Transmission 4.0?

[Lucho-U]

OK, I think I got this. There is some kind of interference between manual port forwarding in router and "port-forwarding-enabled = true" in settings.json

The thing is that I was doing manual port forwarding in my router for port 44741 and at the same time I had "port-forwarding-enabled = true" in settings.json, this setting enables upnp to router for port 44741. Apparently since transmission daemon was unable to upnp port 44741 because it was already manually port forwarded in router, it was doing upnp on the fly for a different random port, in this case 44743. Does this make sense, is this expected behavior? This is somehow different than the behavior I saw in Transmission 3.0.

Finally what I did was to set "port-forwarding-enabled = false" in settings.json and do manual port forwarding in router. Now settings.json, Web client and transmission remote GUI are showing the same port (44741).