2.3 Connection failed error

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 12:25 pm

Hi, I downloaded 2.3 today, and I get a "Connection failed" notice next to almost every torrent. That was 13 our of 15 torrents.

This also happened with the beta. When I revert back to 2.22 (12099) I don't get the error. My port is open. I've never had this problem until I installed the 2.3 beta, and it persists with the final release. I haven't changed any settings from the 2.22 version, and that continues to work fine. So now I'm back on 2.22.

This problem was both on my G4MDD running Leopard and my Intel iMac running Snow Leopard.

Any ideas?

Thanks

Post by **livings124** » Tue May 17, 2011 12:33 pm

Did you post a bug report when this happened with the beta?

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 2:03 pm

No, I didn't. I should have, but then I can't imagine I'm the only one that had an issue with it. I figured it was a beta release, and that was the reason. As I mentioned, even the current version doesn't work on two different Macs.

Post by **livings124** » Tue May 17, 2011 2:28 pm

Sigh...why do we even have beta releases?

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 3:12 pm

livings124 wrote:Sigh...why do we even have beta releases?

Do you not test them yourselves? It now affects the final release. I can't imagine I'm the only person with this issue. No one else has reported it?

That's why I'm reporting it now.

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 4:06 pm

They all seem to have a number of trackers associated with them, when you look at the trackers pane of the torrent info.

It's very possible they haven't whitelisted it (which was something I was unaware of), but if that's the case, it's not whitelisted with any of the trackers listed.

Maybe we just need to wait for them to do so?

Post by **livings124** » Tue May 17, 2011 4:40 pm

DavidRavenMoon wrote:
livings124 wrote:Sigh...why do we even have beta releases?
Do you not test them yourselves? It now affects the final release. I can't imagine I'm the only person with this issue. No one else has reported it?

That's why I'm reporting it now.

Correct - no one else has reported this. We have beta releases to have users test them in scenarios that we can not. Why would we have beta releases if we were not expecting feedback?

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 5:09 pm

Of course that's what beta releases are for, and I've even been a beta tester in the past. I think the issue with that I that the automatic update feature just goes ahead and tells you there is a new release, even if it's beta, and it even wanted me to install the Intel only version on my G4. It might be batter to op into a beta program, because then you will have people who are committed to test and report. I had just moved from my G4 to my iMac, so I had a lot of stuff to do to get the computers set up.

At that moment I really didn't have the time to test beta software, or to file bug reports. So when it wasn't working, I just reinstalled the previous version. Before doing so I checked my settings, etc., and everything looked normal.

This morning I installed the new version and got the same series of yellow warning triangles saying the connections failed. I double clicked on one of the downloads, and looked through the tracker list, and they all said connection failed. One or two downloads seemed to have been working, or at least they didn't have the warning sign. With the beta none of them were connecting.

I'm more than happy to send you any additional info. I can install the new version again if needed.

Post by **livings124** » Tue May 17, 2011 5:28 pm

The beta program is opt-in. It is off by default and is enabled in the General Preference pane.

Showing the update on PPC is something we couldn't avoid - Sparkle offers no way to differentiate based on CPU.

Post by **Jordan** » Tue May 17, 2011 5:37 pm

No, nobody else has reported this (yet).

Could you mail me the URL for a public torrent that's demonstrating this behavior? My mail is jordan at tra[this domain]ionbt.com

siliconjones · Post by **siliconjones** » Tue May 17, 2011 7:13 pm

I too am receiving the same error.

Tracker returned error: Connection Failed.

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 8:00 pm

So I reinstalled 2.3, and now it's working. It's been about an hour so far. What would usually happen is it would work for a few minutes and then give the Connection Failed notice.

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 9:18 pm

OK so it's been running continuously all this time. I checked it about 20 minutes ago, and it had a bunch of yellow warnings. I just left it going. Now there is only one out of 16 transfers.

So it must be a transient error that fixes itself. Maybe it's being too sensitive to the tracker's condition, and the last version just didn't report it?

Oh and it's a great program.

DavidRavenMoon · Post by **DavidRavenMoon** » Tue May 17, 2011 9:44 pm

Now they are all connected.

siliconjones · Post by **siliconjones** » Wed May 18, 2011 12:34 am

Connection still failed on all my active transfers after upgrading. Thoughts?

Transmission

2.3 Connection failed error

2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error

Re: 2.3 Connection failed error