Http error 499
-
has anyone ever come across this? this is happening to a tracker from another site.
so far the only "solllution" I've found is to download some unknown softward from an unknown company from an unknown site…
thanks
-
HTTP 499 means that the client (your computer) closed the connection before the server answered the request. In most cases, this is caused when there is a relay that the connection must pass through that fails the connection, triggering an HTTP 504 (Gateway Timeout) occurs when trying to answer your request. This occurs when using some form of a proxy or hide-behind system for anonymity on the internet. What happens is your computer actually connects to the proxy that the real server hides behind, and instead of an HTTP 502 (Bad Gateway), it results in an HTTP 504 (Gateway Timeout). When the gateway times out, so does your computer's timeframe for receiving a response, thus triggering an HTTP 499 on your end as your computer terminates the connection before the proxy can respond with the real server's response, instead of the proxy issuing an HTTP 502…..
Simply put, the tracker side configuration is f***ed
-
499 is not an official HTTP status code so it can be implemented to mean various things by different developers. MrMazda isn't wrong, but it only applies if the tracker your using is hosted on an nginx web server or behind an nginx reverse proxy which is possible, another possibility is that the site is being blocked by your anti-virus, Kaspersky is known to use the 499 status code that way, so try disabling your anti-virus.
You could do a couple of tests which would give you a better idea of what's going on,
1. in your torrent client, when you click announce, how long does it take to come back with the 499 error, if it takes a little while, probably 30-90 seconds it's probably what MrMazda said, if it's very quick then it's more likely to be AV.
2. take the tracker announce url from your torrent client and paste it into your web browser, it should also get the 499 error, if AV is blocking it you will probably get a page telling you how you can fix it, if it's nginx, it wil probably have the error then below that nginx and a version number. -
shez, thank you for mentioning the AV. it turned out that was it. I changed how it was allowed to connect in my kaspersky, and that has solved the problem.
still don't know where the error occured, a change at the site or an update to the AV.
-
probably an auto update on your AV
