I have an issue here with Transmission (even with older versions like 2.9.2).
So, first of all, the port shows always as "Closed". But here's the thing...it doesn't show up the clients connected in the router interface. It doesn't show up anywhere. So, it looks like it's not even opening those ports. At least they don't show up as open (under UPnP clients).
UPnP is enabled, port is the default one. And if I don't use UPnP and try to set Port Forwarding manually, I get this error.
It does the same thing with any other port, as long as it's also set up in Transmission. Also, just to clarify, there is no other setting for that port, on my router. So...whatever the router is detecting...is not actually displayed on its interface. It's not like I'm trying to duplicate an existing rule I created earlier. From a UI standpoint, there is no other setting previously added. And trying to add it for the first time, results in that error.
However, with another bittorrent app (qBittorrent in this case), I do get the clients showing up in the router's interface.
And the download speeds are also a lot better.
Point is, with qBittorrent, and the ports showing as in my screenshot above, I get faaar, far better speeds, downloading the exact same thing. Just for comparison, 50-60Mb/s vs 1.5Mb/s with Transmission. So it's a HUGE difference.
So, right now, looks like an app issue to me. Looks like the app is listening to the port (I ran lsof -i :[portNumber] and the port shows up as "LISTEN", but there is no "ESTABLISHED" connection during download), so, I think it might not be connecting through it). It probably does connect somehow, cause I can download...but the speeds are not great, as I mentioned above.
I also want to mention that I tested:
curl -4 https://portcheck.transmissionbt.com/PortNumber; echo
and
curl -6 https://portcheck.transmissionbt.com/PortNumber; echo
and they both return 0.
CanYouSeeMe.org shows: Error: I could not see your service on [IP] on port (51413) Reason: Connection timed out
But again, since it works fine with other apps, I think the problem is likely somewhere else.
I feel like this might be a combination of app issue and network setup.
For reference, my setup looks like this: ISP > ONT > My Router (tp-link C80 in case it makes a difference) > PC/laptop etc.
I tested multiple versions, and this also occurs with previous OSes as well. So, I think it's probably just an unusual setup that hasn't been taken into account yet.
I tested with Firewall turned OFF, just to have one less point of failure and be able to work only with router issues, not combinations of router and firewall.
I also tested the exact same app on another WiFi network, on another ISP, with a different setup (only ONT, which also doubles as wifi router) and the issue did NOT occur. Port showed up as Open, and everything ok.
I also read about other people's experiences and tested the theory of the IPv6 being the cause of this. However, I have IPv6 already disabled in my router. And even with it enabled, it doesn't make any difference to the issue.
So yeah....I know probably most people won't have this issue, if they're just using the default router/ONT, and it could also be ISP dependent. Mine is using PPPoE, just as a reference, the other one was not (not sure what exactly is it using, but it's not PPPoE).
Anyway, I wrote a lot, and I apologise for this. But I've had this issue for a looong time and never had the time to test different scenarios until recently. So I hope that helps.
If you have any questions or things you want me to try, please, let me know. I'd be glad to help, however I can.
Hey guys,
I have an issue here with Transmission (even with older versions like 2.9.2). So, first of all, the port shows always as "Closed". But here's the thing...it doesn't show up the clients connected in the router interface. It doesn't show up anywhere. So, it looks like it's not even opening those ports. At least they don't show up as open (under UPnP clients).
UPnP is enabled, port is the default one. And if I don't use UPnP and try to set Port Forwarding manually, I get this error.
It does the same thing with any other port, as long as it's also set up in Transmission. Also, just to clarify, there is no other setting for that port, on my router. So...whatever the router is detecting...is not actually displayed on its interface. It's not like I'm trying to duplicate an existing rule I created earlier. From a UI standpoint, there is no other setting previously added. And trying to add it for the first time, results in that error.
However, with another bittorrent app (qBittorrent in this case), I do get the clients showing up in the router's interface.
And the download speeds are also a lot better.
Point is, with qBittorrent, and the ports showing as in my screenshot above, I get faaar, far better speeds, downloading the exact same thing. Just for comparison, 50-60Mb/s vs 1.5Mb/s with Transmission. So it's a HUGE difference.
So, right now, looks like an app issue to me. Looks like the app is listening to the port (I ran
lsof -i :[portNumber]and the port shows up as "LISTEN", but there is no "ESTABLISHED" connection during download), so, I think it might not be connecting through it). It probably does connect somehow, cause I can download...but the speeds are not great, as I mentioned above.I also want to mention that I tested:
curl -4 https://portcheck.transmissionbt.com/PortNumber; echoandcurl -6 https://portcheck.transmissionbt.com/PortNumber; echoand they both return0.CanYouSeeMe.org shows: Error: I could not see your service on [IP] on port (51413) Reason: Connection timed out
But again, since it works fine with other apps, I think the problem is likely somewhere else.
I feel like this might be a combination of app issue and network setup. For reference, my setup looks like this: ISP > ONT > My Router (tp-link C80 in case it makes a difference) > PC/laptop etc.
I tested multiple versions, and this also occurs with previous OSes as well. So, I think it's probably just an unusual setup that hasn't been taken into account yet. I tested with Firewall turned OFF, just to have one less point of failure and be able to work only with router issues, not combinations of router and firewall.
I also tested the exact same app on another WiFi network, on another ISP, with a different setup (only ONT, which also doubles as wifi router) and the issue did NOT occur. Port showed up as Open, and everything ok.
I also read about other people's experiences and tested the theory of the IPv6 being the cause of this. However, I have IPv6 already disabled in my router. And even with it enabled, it doesn't make any difference to the issue.
So yeah....I know probably most people won't have this issue, if they're just using the default router/ONT, and it could also be ISP dependent. Mine is using PPPoE, just as a reference, the other one was not (not sure what exactly is it using, but it's not PPPoE).
Anyway, I wrote a lot, and I apologise for this. But I've had this issue for a looong time and never had the time to test different scenarios until recently. So I hope that helps.
If you have any questions or things you want me to try, please, let me know. I'd be glad to help, however I can.