After upgrading Transmission, port is permanently closed

[tasmand@gmail.com]

Same thing has happened to me as well. I am dead in the water no matter what torrent manager i use. I have tried them all and since i downloaded 1.42 all of my ports are closed on every torrent manager. I have heard that people have gone back to 1.40 and 1.41 and everything is working fine. I have tried that as well but to no avail. Can someone please help me. I am using 10.4.11 if that helps.

[Jordan]

Same thing has happened to me as well. I am dead in the water no matter what torrent manager i use. I have tried them all and since i downloaded 1.42 all of my ports are closed on every torrent manager. I have heard that people have gone back to 1.40 and 1.41 and everything is working fine. I have tried that as well but to no avail. Can someone please help me. I am using 10.4.11 if that helps.

I am beginning to think people are posting in this thread after reading the subject header and nothing else.

http://trac.transmissionbt.com/wiki/PortClosed

[flamesong]

I came by this thread because I too am experiencing a permanent 'Port is closed' message.

I am pretty familiar with my router and other network settings and having been through the Port Closed page on the wiki I can say with certainty that I have followed the instructions to the letter but still get the 'Port is closed' message.

I then tried the link to www.canyouseeme.org and tried the current Transmission port and got the following:

Error: I could not see your service on 81.77.XXX.XX on port (51413)
Reason: Connection timed out

I tried several alternative port numbers and each got the same message.

When I started checking the common ports, 21, 25, 80, 110, I still got the same error - yet I use ftp, e-mail and the web constantly without any problems whatsoever.

I wouldn't like to point the finger but it seems that if Transmission is using this site to check if ports are open - as suggested on the wiki page - then the error may somewhere in that vicinity.

[Morpheus]

Hi

So I am now also having the incredibly slow speed problem (0.3k) , but at least its better than the nothing I had before. Port still closed, tried all options blah blah.
BTW: Instead of just responding by linking the same old wiki, which everyone have tried with no success, maybe someone should realize that there is a problem here, maybe not the software but somethings up....

[Morpheus]

Success!

I have just downloaded the new update 1.50b3 and there is a huge speed improvement. Sooooo, guess it WAS the software after all. Maybe it would be a good idea to put a little more time into updates instead of releasing one every week.

Thanks!

[livings124]

I have just downloaded the new update 1.50b3 and there is a huge speed improvement. Sooooo, guess it WAS the software after all. Maybe it would be a good idea to put a little more time into updates instead of releasing one every week.

Way to be a troll. A guess there's an insult no matter what we do.

[flamesong]

EDIT: Please see P.S. at end of post.

I'd like to get my 2 cents worth in on this one, if I may. I can give you a couple of reasons why a port check by a site like canyouseeme.org might fail even tho' the port is in fact open.
#1 If you have 'Stealth mode' enabled in your Firewall, the pinging by 'canyouseeme.org' might be interpreted as an attack and, therefore blocked.
#2 NortonAV likewise may block such pinging probes, considering them an attack. (This one, I have personally confirmed by tracing the IP address NAV noted back to 'canyouseeme.org'.)

Such blockages are usually sporadic, thus contributing to the confusion. Bottom line:If you have portforwarded your router and firewall correctly and data packets are getting through, then IMHO, port must be open.

P.S. Despite all this, if you are still getting d/l from 0 of 0 peers after a successful tracker announce to an active torrent, check to see if your router has a low/high setting in it's firewall...LOW setting must be used for peers to connect!

Today, without making any adjustments to anything, I have 'Port is open' and http://www.canyouseeme.org says:

'Success: I can see your service on 84.66.XX.XX on port (51413)
Your ISP is not blocking port 51413

Transmission is downloading at an average of about 110k.

I use NetBarrier with the firewall off and configured to give alerts whenever there is anything untoward happening. The OS X firewall is disabled and the firewall in my router is set at its lowest level - everything which can be disabled is disabled.

[gamov]

Hello there.
This is my first post.

I've been using Transmission for a long time now. The last few times I used Transmission, I also noticed that the Network tab of the preferences reports the incoming port as closed. My download speed has also started to drop significantly and sometimes stall.



Today, I fired uTorrent to compare and, hold & behold, uTorrent reports its random generated Incoming port opened. For the same torrent, uTorrent screams compared to Transmission so I guess there is a problem with the port setup.
I believe this issue is older than October '08

I hope there is a easy fix for this problem since I love Transmission...

Regards,
Gam

PS: I'm on OS X 10.5.6

[essiw]

gamov which version of transmission are you using?

[gamov]

gamov which version of transmission are you using?

Hello essiw,
Last night, I tried both 1.42 and 1.5b4

Regards,
gamov

[monkeylove]

I have the same problem: Transmission 2.50 running in a NAS and accessed from a Win 7 64-bit desktop using Transmission Remote v3.24 build 3.

I also installed uTorrent in the desktop to check.

uPnP is on for the router, port forwarding for both Transmission BT and uTorrent, and random ports are used.

I am using a cable modem with a web proxy assigned by the ISP.

Here's what I got:

www.canyouseeme.org times out or reports that ports are closed, whether for Transmission or uTorrent.

Transmission reports that its port is closed.

When I telnet to the NAS and enter

netstat -nat | grep LISTEN

it lists the port assigned to Transmission, so I'm guessing that the port is open.

uTorrent reports (using the setup guide in the software) that its port is open. When I transmit using uTorrent, the indicator in the status bar shows a green check mark.

Download speeds for Transmission and uTorrent appear to be normal, except that for Transmission the speed tends to go up and down, while for uTorrent the speed looks more consistent.

I used static IP addresses, no random ports, and manual port forwarding in the router and the results are the same.

There's another line from the same ISP available nearby with another Windows PC and router connected to it, and I get the same "port closed" message for Transmission for Windows installed in the PC. uTorrent installed in the same PC shows through its setup guide that its port is open.

I haven't tried this with another broadband line (like a DSL or wi-fi) but I'm guessing that there's something about the web proxy in the ISP that blocks CanYouSeeMe or the Transmission port checker, even as netstat or nmap running from the device where the torrent client is installed shows that the port is open. It doesn't block the port checker for uTorrent, though.