Transmissions stopped downloading for a specific tracker.

[robocopswitch]

Recently one of my favorite tracker changed IP's, and I believe since then I have been unable to download anything. I don't get any errors (or tracker errors) and different trackers work perfect. When I start a torrent from this tracker, seeds and peers stay zero. When I ping the tracker I can reach it fine, the IP resolves to the correct IP. Even stranger, when I run uTorrent on my worksttion and start a torrent from the tracker it downloads instantly, no problems whatsoever.

I'm assuming something's wrong with my Transmission installation, I've updated from 1.75 to 1.80-1 but no luck. Transmission is running on Linux on a Synology NAS, but that shouldn't be any problem. I don't get it, it was all working fine and then it just stopped.

Does anyone know whats wrong? I've tried everything!

(transmission 1.7.x and 1.8.x are allowed clients on the tracker)

[robocopswitch]

I updated to 1.83 and the same problem persisted. Downgraded to 1.76 again because 1.8x keeps crashing on my ARM based Synology box, still no downloads from this tracker...

Edit: forgot to add to report the same tracker also refuses to download in rtorrent on the same pc, so it's probably something in the system and not transmission-related.

[matinee]

Hi, have you been able to resolve this issue? I face the exact problem. I have 1.83 installed on my NMT and was working perfectly till recently. The same client downloads from other trackers except just one. Any help would be highly appreciated!! Thanks in advance...

[matinee]

Hi, have you been able to resolve this issue? I face the exact problem. I have 1.83 installed on my NMT and was working perfectly till recently. The same client downloads from other trackers except just one. Any help would be highly appreciated!! Thanks in advance...

Are the announces successful? Is v1.83 whitelisted by this tracker?

http://trac.transmissionbt.com/wiki/SlowSpeeds

Yes. I did check the tracker's website and they do allow v1.83. A short while ago, I even did a complete reinstall of the NMT Apps on the device and installed v1.76 this time. However, I still get the same issues - other private and public trackers perform as they should, whereas a particular tracker from where I download the majority of my TV shows does not show details of Seeds and Peers. It just has question marks (?) preceding them. A colleague of mine uses the same v1.83 and the same tracker without any problems! You think a complete formatting of the HDD might help? Thanks!

[matinee]

If this is a private tracker, is your ratio at an acceptable level? I don't think HDD formatting enters into the equation. Check the Inspector announce and info tabs.

Thanks. I do have a healthy ratio. I also re-announced a couple of time, with no visible errors or remarks. I am just running out of ideas, and still keen on enabling access to this private tracker....

[Lutin]

Hi, have you been able to resolve this issue? I face the exact problem. I have 1.83 installed on my NMT and was working perfectly till recently. The same client downloads from other trackers except just one. Any help would be highly appreciated!! Thanks in advance...

I have the same problem. Whatever I take from BS is not downloaded. What I do is I repair permissions, restart, and it works again. Weird.

[the_oni]

am facing the same problem at seedbox server the version of transmission they used is 1.76 please i hope u can solve this problem

[Altair]

Recently (around Feb. 10th) I noticed that some ISP or Tier 1 carrier started to block bittorrent announces to certain trackers (f.e. Linuxtracker.org, but private ones are effected too) by sending forged RST packages. Ping, traceroute and browsing the website of this trackers worked fine. But as soon as the client sends it's torrent specific data with a PSH (like client ID, torrent hash etc.), it receives a RST package supposedly send by the tracker. So maybe anybody having this strange problems should check if that's the case on their machine (or more specifically, their uplink). Unfortunately checking is more of a thing for the tec-savy, a good tutorial can be found at the EFF:

Detecting packet injection: a guide to observing packet spoofing by ISPs

This is rather new and, unlike the EFF exposed Comcast traffic shaping, targets Peer-Tracker communcation instead of Peer-Peer communication.

Edit: As of Feb. 24th, the problem seems to be gone (at least on my line).