Posts made by ReliquaryX

Omar Little from The Wire. A shotgun wielding black, gay, out, drug dealer in Baltimore. He is one of my top 5 tv charecters of all-time, all-shows.

Oh… He slapped a contest judge. I thought it was going to be a judge-type judge. That would have been... AWESOME!

Hmm…  In the "Trackers" tab, I see the url for the tracker/announce.  Just to the right of that is the "Status" column, and the message is:  "offline (timed out)"

Then it's counting down from a half-hour, looks like... As soon as it gets to zero, the status is "updating", then back to offline again. 

I have the same problem with BitTorrent 7.7 (it looks like the exact same platform as uTorrent) Does anyone know how far down I have to walk it back?

EDIT: I installed BitTorrent 7.2, and it made no difference. Also the Vuze (azurus) client, AND uTorrent clients… All three show gtru (and ONLY gtru) trackers as "offline". I've been fiddling with this for almost 2 weeks now. The only solution I've found so far is to just use other, lesser sites. 

I've checked the basics, and it looks like everything is set correctly. Indeed, all other torrent sites are working fine on my end, both uploads and down. It's only the gt.ru site. All the gt.ru trackers say…  "offline". I've got mu-torrent version 3.2.1. Does anyone know what could be wrong? Is anyone else with that version having trouble?  Thx!

EDIT: Ok, I've installed the BitTorrent client AND the Vuse (Azurus) clients, and tried downloading from GT.ru  All three say the same thing. GT.ru trackers are offline and timing out. All three clients are able to download from other sites like PirateBay just fine. Is anyone else experiencing this?

I'm using mu-torrent client. All my trackers for GT.ru are showing as timed out. I've rebooted, no change. I saw the site got hacked for a few hours a couple days ago… My trackers for other sites, like piratebay, are fine. Is there an issue on the GT.ru side, or do I need to look at my own self again? Any ideas?

EDIT: I see after reading another post that lots of people with an updated mu-torrent client are having the same problem. Anyone know if it's getting fixed, and by whom?