Not connected on 4.0_5

[aliekiddo]

What is the issue?

I have had Transmission plugin running on a TrueNAS Core server for many many years and it has been able to download and seed without any specific port forwarding set up on my Openwrt router.

I recently updated Transmission to 4.0.5_1 and nothing was able to connect, the port checker says 51413 is closed.

I tried setting up port forwarding in my Openwrt router, still the same result. I tried installing a UPnP add on, still the same result.

I rolled back to v 3.00 and I can connect again.

CanYouSeeMe.org still says "Error: I could not see your service on (my IP) on port (51413) Reason: Connection timed out"

I don't know if this is a router setup problem that has 'just worked anyway' up until v 4.0, a problem created by a change to v 4.0, an ISP (Hyperoptic) 'they've recently changed something' problem or something related to my TrueNAS Core on Adguard Home setup.

Which application of Transmission?

transmission-daemon

Which version of Transmission?

4.0.5_1

[Pentaphon]

Why keep using the same port? We've already proposed randomizing the port for new installs so you should start doing that yourself. I believe there's a UPNP issue on 4.0.5 so I recommend staying with 3.0 if it works and just wait until 4.1.0 to try a new version.

[aliekiddo]

Because that's the default and it worked.

[tearfur]

Any chance you can show us some logs, the logs related to your problem should be from port-forwarding.cc, they look something like this:

[2024-05-26 02:13:45.202] inf port-forwarding.cc:219 State changed from 'Not forwarded' to 'Starting' (port-forwarding.cc:219)
[2024-05-26 02:15:53.203] inf port-forwarding.cc:219 State changed from 'Starting' to 'Not forwarded' (port-forwarding.cc:219)