Transmission

No.

Robby wrote:No.

Cool.

So between what Robby, you and waldorf have put forth, the "port status" feature of Transmission is merely an automation of checking your port status from an external entity such as the example cited, http://www.canyouseeme.org/.

IOW, if you manually determine that your port status is okay, then there is no effect on the functionality of the bittorrent protocol or Transmission client and any problems thought to have been induced by this malfunction have been reported in this thread are merely coincidental or histrionic.

Makes sense to me. Sounds like EVERYONE CAN RELAX.

Thanks to the contributors of this thread.

Yes, that's how I think it is. If I remember correctly, some developer told me that a while ago when this happened before.

I got this "unable to check port status" message too. It doesn't affect my DL or UL speeds, just annoying

is anyone else on Comcast? Could our ISP's have anything to do with this?

It is merely a check which has to be run from the outside of your local network. The only 'bad' thing about it is that if that site is down, you will get this friendly message.

So, again, the check is completely unrelated to the core of Transmission and is mere informative.

josephayden, no. Your ISP's don't have anything to do with this.

thank you for clarifying good sir

my port is stealth - i'm still trying to figure out the port forwarding thing. But transmission is just saying unable to check its status like everyone is saying...

Then try that site which was mentioned as an alternative.

if you manually determine that your port status is okay, then there is no effect on the functionality of the bittorrent protocol or Transmission client and any problems thought to have been induced by this malfunction have been reported in this thread are merely coincidental or histrionic.

Hmm... that doesn't make any sense to me. Sure problems related to this malfunction could be considered coincidental, but what about the actual "unable to check port status" message. Even if the fact is that Transmission's "port checker", or lack thereof has no effect on your actual connections this doesn't explain why a dozen people reported this error on the same day, why the error occurred, or how to fix it.

jgor wrote:

if you manually determine that your port status is okay, then there is no effect on the functionality of the bittorrent protocol or Transmission client and any problems thought to have been induced by this malfunction have been reported in this thread are merely coincidental or histrionic.

Hmm... that doesn't make any sense to me. Sure problems related to this malfunction could be considered coincidental, but what about the actual "unable to check port status" message. Even if the fact is that Transmission's "port checker", or lack thereof has no effect on your actual connections this doesn't explain why a dozen people reported this error on the same day, why the error occurred, or how to fix it.

Sure it does; the web portal that Transmission uses to check the status (just like the web site mentioned in this thread where you can check your port status manually) is down, so Transmission can't determine the status.

That's the way I understand it now, anyway.

I can reach them manually in a browser, so I wonder if they're blocking Transmission's traffic. If so we could move to a different port checker in the next release.

I noticed last night that my upload speeds were way slower than normal through Transmission. My upload speed would hover around 20 - 30 KB/s when I normally get around 140 KB/s. I had 12 peers downloading from me.

I ran 5 different speed tests, and my upload speeds came back normal. So I checked the Network settings in Transmission, and sure enough "Unable to check port status" came up.

I went to canyouseeme.org and checked the port. My ISP isn't blocking it.

How is it that all of these people are having the exact same problem at the exact same time?

So long story short, I'm having the same problem.

Jov604, how about reading the thread?