Jump to content

issue with status of tracker


xvinx87

Recommended Posts

Same problem for me.

Sometime µtorrent tells me the Tracker is timed out and offline, but when i check it with a webbrowser or another client the tracker works perfect.

Updating the Tracker doesent change anything, only restarting µtorrent solves the problem.

This issue is very bad when you download form an Anti Leech Tracker, because your up/downs want be counted, and some Tracker-Admins could think that you try to cheat and ban you from the Tracker.

I think until this problem is solved i will use Azureus.

µtorrent is great, but i wont risk getting kicked from my favorit ALT-Tracker.

@the developer: Please first solve this problem, and then concentrate on DHT.

DHT is a function that many ALT-Tracker Admins hate, and forbid to use this feature on their trackers.

Link to comment
Share on other sites

http://forum.utorrent.com/viewtopic.php?p=12939#12939

The problem can be fixed by double clicking on the torrent in question in your list. This will bring up the list of trackers being used. Remove the spaces before the HTTP:// of the tracker URL. That is what causes this bug. Now that someone (me) has found the cause of the bug. Maybe the developer can now fix it.

Link to comment
Share on other sites

For those who can't connect to the tracker (Offline and timeout errors) even though they know it's online...

The problem can be fixed by double clicking on the torrent in question in your list. This will bring up the list of trackers being used. Remove the spaces before the HTTP:// of the tracker URL. That is what causes this bug. Now that someone (me) has found the cause of the bug. Maybe the developer can now fix it.

This isn't for the gzip error, though.

Link to comment
Share on other sites

http://forum.utorrent.com/viewtopic.php?p=12939#12939

The problem can be fixed by double clicking on the torrent in question in your list. This will bring up the list of trackers being used. Remove the spaces before the HTTP:// of the tracker URL. That is what causes this bug. Now that someone (me) has found the cause of the bug. Maybe the developer can now fix it.

There are no spaces before HTTP:// the problem is something else.

Link to comment
Share on other sites

[link removed (private tracker, no account availability, no way to determine content hosted, so I'm erring on the safe side)]

You have to have an account (for free).

The message is "Tracker sending invalid data". With other torrent clients is OK. Could be gzip, I don't know for sure...

EDIT: you should just PM ludde the links

Link to comment
Share on other sites

  • 4 months later...
Oh, okay. :P Do torrent clients even advertise gzip support (like a browser)? I haven't really captured the packets sent to a tracker, so I wouldn't know.

I'm honestly not sure offhand if all clients do or not as only a couple were used during initial testing when I'd coded the first version of the tracker. Some did, while others didn't. So, I made sure that if it couldn't be determined that the requester could accept compressed output, it would be sent uncompressed.. It's the best thing to do for cross-client compatibility. I haven't had any reports relating to compression errors since.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...