Bittorrent Broken

[arv1]

I am using daily R9013 and every single torrent file returns a "tracker down" message. It began two weeks ago when half the torrents would return a "tracker down" message, now it is every torrent.

Has Shareaza been kicked out of trackers ? is something broken in the software ?

My connection test is all green ok.

Anybody else experiencing the same problem?

[old_death]

Nothing has been reported from other users so far. Could you tell us whether these torrents have a tracker in common? Maybe it's an issue related to the tracker maintenance...

[ailurophobe]

Some trackers do block Shareaza since a long time ago, no idea if the reason is even relevant to current version. Maybe you are downloading something that is on such trackers and as time went by completed all torrents on trackers that worked. It is also possible that have some BT settings in incorrect values that get you personally banned. Trackers often have some kind of forum or channel that has a list of clients banned on the tracker.

btw, IIRC the trackers actually give a meaningful response if your client is blocked, Shareaza just does not forward it to the user and instead incorrectly claims the tracker is down. I think you can get more info in the network log by changing the verbose level. (Haven't used BT in some time so could be wrong.)

[soul1355]

also, just to check, you're not getting all your torrents from the same tracker, right?

[arv1]

It appears to be the same 2 trackers from which i download most files i'm interested in that now reject my client.
Other trackers work.

I simply moved to another torrent site. All is fine now (though i used to love the PB )

[ailurophobe]

Something worth checking: I downloaded a torrent and Shareaza failed at uploading it before it completed. Once it completed and Shareaza auto-seeded it everything worked as it should. If you download enough torrents with the same tracker this might get you banned as a leech before any of the torrents complete and Shareaza starts uploading. This was a one time event and I was not using the latest debug, but... is anyone else seeing this?