2.3 Connection failed error
-
- Posts: 3
- Joined: Tue May 17, 2011 7:11 pm
Re: 2.3 Connection failed error
2.3.1 ftw. thanks!!! love transmission btw.
-
- Posts: 9
- Joined: Tue May 17, 2011 12:09 pm
Re: 2.3 Connection failed error
I noticed that as I quit it and relaunched it (because I was switching between the two versions) it would stay connected longer and longer. Now it's fine.siliconjones wrote:Connection still failed on all my active transfers after upgrading. Thoughts?
So maybe launch it a few more times.
Re: 2.3 Connection failed error
I'm getting the same error on 2.3.1. Has anyone got any advice on how to correct it please?
Re: 2.3 Connection failed error
2.31 began to write this under almost all torrents:
"Tracker returned error: Tracker gave HTTP responce code 502 (Bad Gateway)" or "Tracker returned error: Tracker gave HTTP responce code 0 (No Response)". Even while downloading, but then there is no upload.
Almost all are torrents are from "example.com". The problem is not with ISP (I've changed 3 different) - same problem everywhere.
No crashes. No freeze.
"Tracker returned error: Tracker gave HTTP responce code 502 (Bad Gateway)" or "Tracker returned error: Tracker gave HTTP responce code 0 (No Response)". Even while downloading, but then there is no upload.
Almost all are torrents are from "example.com". The problem is not with ISP (I've changed 3 different) - same problem everywhere.
No crashes. No freeze.
Re: 2.3 Connection failed error
Sounds like that tracker might be down
Re: 2.3 Connection failed error
Well, as much as I love Transmission, it's useless to me at the moment because of the "Tracker returned error" problem. The problem has actually escalated in v2.31 - where previously it continued to download the torrent even while still displaying the error message - now, it doesn't even allow the torrent metadata to be loaded, meaning the torrent download never starts.
I've tried other torrent apps and they work with the torrents that Transmission rejects as being an error. So, as much as it pains me, I'm off to use uTorrent and BitTorrent to grab my downloads
I've tried other torrent apps and they work with the torrents that Transmission rejects as being an error. So, as much as it pains me, I'm off to use uTorrent and BitTorrent to grab my downloads

Re: 2.3 Connection failed error
I have exactly the same problem : since version 2.3 My uploads and my downloads remain at 0, whereas my port si always open.
Reversing to 2.2 version works.
But erasing version 2.3 and installing it again doesn't.
So I'm remaining stuck with 2.2.
I had exactly the same problem with 2.30 previous version, I thought 2.31 had fixed the problem. I tried without Micro Transport Protocol but it didn't change anything.
Are we so few with this problem ?
Update : I tried to lessen the global maximum connections to 100 and 40 for new transfers and it worked. I had previously 200 and 60 as recommended
Reversing to 2.2 version works.
But erasing version 2.3 and installing it again doesn't.
So I'm remaining stuck with 2.2.
I had exactly the same problem with 2.30 previous version, I thought 2.31 had fixed the problem. I tried without Micro Transport Protocol but it didn't change anything.
Are we so few with this problem ?
Update : I tried to lessen the global maximum connections to 100 and 40 for new transfers and it worked. I had previously 200 and 60 as recommended
Re: 2.3 Connection failed error
Same problem today, without changing anything.
I think I'll back up to 2.22 version definitely.
I'm on Snow Leopard last version (10.6.7) on an Imac Intel Core 2 Duo 3,06 Ghz with 4 Go of RAM DDR3
I think I'll back up to 2.22 version definitely.

I'm on Snow Leopard last version (10.6.7) on an Imac Intel Core 2 Duo 3,06 Ghz with 4 Go of RAM DDR3
Re: 2.3 Connection failed error
Wait, I am having the same errors as well. I do not understand what the solution seems to be here though.
All of my torrents save two or three, had yellow warnings about not being able to connect with the trackers I had. Even the rocksolid ones like genesis, exodus, nemesis, etc. And I am all of a sudden experiencing a gruelling 2.3 Kbps upload speed to my leechers. With the previous version (2.22) I was able to seed at 80 kbps and have all of my trackers working. I don't want to consider utorrent b/c I like how native transmission is. Should I just ignore the warnings? Will there be another update soon? And should I file a bug report?? 


Re: 2.3 Connection failed error
Endavent wrote:Same problem today, without changing anything.
I think I'll back up to 2.22 version definitely.![]()
I'm on Snow Leopard last version (10.6.7) on an Imac Intel Core 2 Duo 3,06 Ghz with 4 Go of RAM DDR3
Hey how can you back up to 2.22 without losing all your torrents and such???
Re: 2.3 Connection failed error
I have exactly the same problem, Out of 21 torrents 13 show "Connection Failed", 4 show "Error 404, not found". On Mac OS X 10.6.7 and Tranmission 2.31 (12441)
Re: 2.3 Connection failed error
1. Are these single-tracker or multi-tracker torrents that get the "connection failed" error?
2. If you look at the tracker lists in the Trackers tab of the torrent dialog, is it the same tracker each time that says "connection failed"?
2. If you look at the tracker lists in the Trackers tab of the torrent dialog, is it the same tracker each time that says "connection failed"?
Re: 2.3 Connection failed error
I have reverted to Transmission 2.22 (12099) and everything runs fine, no connection failed, no error 404. The "Connection Failed" errors are all multi-tracker torrents
Re: 2.3 Connection failed error
And, was there a pattern about which trackers returned the error?
I'm not seeing this issue in 2.31 and am trying to figure out what I need to do to reproduce this error for myself.
I'm not seeing this issue in 2.31 and am trying to figure out what I need to do to reproduce this error for myself.
Re: 2.3 Connection failed error
Can I send you privately screenshots of the trackers, I could not see a pattern. I can reload 2.31