1.7.3 not working with Mac OS X 10.6 (10A432)

[rgw]

Any torrent I open with Transmission will never pick up any peers. I've tried with the firewall off to no avail. I've tried with the firewall and Transmission allowing incoming connection, still no dice. Has anyone encountered this problem and are their any work-arounds?


Information about my 10.6 install:
- Using a White Macbook (2007)
- Installed 10.6 on a disk partition separate from my 10.5 install
- Transmission 1.7.3 still makes connections to peers on my 10.5 install (same computer, same network, etc, etc...just a different system folder).

[rgw]

I can confirm that the torrent in question will connect to peers using the "Bit Torrent OS X" client (ugh!) on OS X 10.6.

[John Clay]

Please try a nightly build, or the recently released 1.74 beta 1 (via the auto-update, with betas enabled)

[rgw]

I downloaded the latest nightly. Unfortunately, this didn't seem to do the trick. I still get 0 of 0 peers on Transmission, but the same torrent will download from Bittorrent OS X

[Wowzera]

I've already reported that bug long ago to the Transmission developers, they didn't care so much about it, but now that everyone will move soon to Snow Leopard we'll see lot of bug reports if it's not solved yet
I'm using uTorrent beta with SL and it's working flawless.

[shadybrady]

I can confirm this. I've used the nightly build as well and this is all off a fresh install to my macbook. I hope you guys can fix this - you've had the best product I can find.

[ScottyDelicious]

This was driving me nuts too! I could get torrents to download via uTorrent, but Transmission showed 0 peers. I updated to the latest (as of Aug 29th) nightly build from http://transmission.xpjets.com/ and everything is working swimmingly now.

Thanks Transmission team!

[barnib97]

When I installed Snow Leopard (Clean Install, Retail) I backed everything up to an external drive. If Transmission is running off of the external drive, everything's great; if it's running off the disk Snow Leopard is installed on, no peers ever show up.

[averseus]

When I installed Snow Leopard (Clean Install, Retail) I backed everything up to an external drive. If Transmission is running off of the external drive, everything's great; if it's running off the disk Snow Leopard is installed on, no peers ever show up.

I've had the same experience with the newest version available as of 2009/09/01 at 11:25pm (betas included), which is version 1.74+ (9009), after upgrading to Mac OS X 10.6.

After starting Transmission after the upgrade, a tracker I use a lot told me that my torrent client's incoming port was firewalled or otherwise blocked, even after upgrading to 1.74+ (9009), which would explain the lack of peers. In my case I did occasionally get a peer, but far, far fewer than normal*, and none for long periods of time. I had Transmission.app in the usual /Applications on my now-Snow-Leopard system disk, and of course I checked the firewall settings on my router and OS, which were all what they were and should be.

When I read barnib97's post above I moved Transmission.app to the external drive where I store my torrents and downloaded files (so the application and data are all on the same drive in my present working setup), and after restarting, this tracker I mentioned no longer says my incoming port was blocked, and I now have a normal number of peers for the time of day on this day.

I hope it helps the developers and others to know that more than one of us here have experienced this problem and have experienced relief from this workaround.


*as I seed 24/7 I definitely know what to expect in terms of peer connections on any given day and time.

[averseus]

When I installed Snow Leopard (Clean Install, Retail) I backed everything up to an external drive. If Transmission is running off of the external drive, everything's great; if it's running off the disk Snow Leopard is installed on, no peers ever show up.

When I read barnib97's post above I moved Transmission.app to the external drive where I store my torrents and downloaded files (so the application and data are all on the same drive in my present working setup), and after restarting, this tracker I mentioned no longer says my incoming port was blocked, and I now have a normal number of peers for the time of day on this day.

After I needed to restart Transmission a few times in rapid succession to make it recognize that I had replaced the content for a paused transfer, I had this problem again. I resolved it by setting Transmission to another port, and reconfiguring my firewall for the new port. Does anyone yet know what is going on with this?

[averseus]

I'm back today to say that now I cannot unblock my port as far as the Ez-Torrent tracker package is concerned. I have changed my port several times, both first on the firewall and then on the client and vice versa, with system restarts in between, to no avail. It does not seem like this topic is getting much attention these days, but I would appreciate any help with this problem that may be offered.

[mejustme]

Yeah, same me. It is not working. T just sits there. How about a fix.

[Wowzera]

Yeah, same me. It is not working. T just sits there. How about a fix.

What about 1.75? It works now here. I'd the same issue. The tracker never got updated with the client.

[mejustme]

@Wowzera, ok, yes. I deleted, downloaded, ran, and it worked. Thanks for that.