@bernard so u were running 2 torrents from a real client and then removed one of the completed ones. U then put that torrent on RM.
since u were using uT 2.0.3 in RM were u using the same real client? and did u match the settings?
Printable View
@bernard so u were running 2 torrents from a real client and then removed one of the completed ones. U then put that torrent on RM.
since u were using uT 2.0.3 in RM were u using the same real client? and did u match the settings?
Yes, both the emulation and the real client were the same. I don't understand what match the settings means... sorry but i'm quite noobish..
Then its possible that as anon has already said that ur 2day old acc was disabled to to suspicious high upload
or u had not used the memory reader, but if u did use memory reader "correctly" then it must have been the above
I guess it was due to "insane upload stupidness" since I used memory reader correctly.
Code:Host: announce.asiandvdclub.org
User-Agent: uTorrent/2040(21586)
Accept-Encoding: gzip
[04:29:07] Waiting for tracker response...
[04:29:07] Receiving...
[04:30:09] Received tracker response, length = 345
[04:30:09] End of HTTP response.
[04:30:09] ----------- Tracker Response --------
[04:30:09] HTTP/1.1 504 Gateway Time-out
Server: nginx/0.7.65
Date: Sun, 12 Sep 2010 13:30:24 GMT
Content-Type: text/html
Content-Length: 183
Connection: keep-alive
[04:30:09] *** Failed to decode tracker response :
[04:30:09] <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/0.7.65</center>
</body>
</html>
If you provided some details somebody would be able to help you.
And stop making useless posts in defferent threads! There is 'Thanks' button to say Thank you.
==================
EDIT: sorry, wrong quote indeed. I meant to quote the post with RM not working on ADC...
5xx errors mean server error, not related with ratiomaster
In this case:
Quote:
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_Error
I think many other people got the same error in the RM, yet normal clients work just fine.
I've noticed that sometimes rm provides a strange memory reader results with special characters at the end of "key" field:
http://img825.imageshack.us/img825/5415/30347861.jpg
just afraid to use it with such a key...
That's a very rare issue. A normal uTorrent key is 8 characters long. Don't use glitched keys at all - restart uT until you get a good one.
When it was happening before, the restarting of RM usually fixed the 'key'. However, this morning after installation of latest XP updates (maybe just a coincidence) restarting PC, this happened again, and restarting of RM did not help. I will try your advise, anon. Thank you!
This happens to me a lot on Win 7 64bits, and never ever happened while using Windows XP sp2/3. It might be a coincidence though, since now I use uT 2.x and always used uT 1.8.x while I was on XP.