502 Error code

glenn524

Is there any way to prevent getting the 502 error code? I assume I lose any seed point while the torrent is showing this?

Pawpcorn

Are you seeing this error code in your web browser or in your torrent program?

If it's in your browser only, it wouldn't affect any torrent data traffic credit.

I've never heard of anyone seeing this error in their torrent client program…

http://www.theguardian.com/technology/askjack/2013/aug/01/502-bad-gateway-error

Take care,
Pawpcorn

1hotstud 0

I see it in my torrent program all the time
Tracker returned error: Tracker gave HTTP response code 502 (Bad Gateway)

If there's any way I can avoid it I'd love to know how
(Using Transmission 2.84 on a Mac)

youngla

I also see this error code routinely. When I first started with this site a few years ago, I noticed that torrent lines would turn red instead of the normal green. (Using utorrent 3.3.2 build 30303) I selected the "tracker status" column to display and those red lines have a HTTP Error 502 status. If push comes to shove and I need or just want to I right click the error line and select Update Tracker to force a retry.
IF it does not change back to green in a few second if not immediately, then my first presumption is that the tracker is busy busy and leave the poor thing alone. ;D
However, when I am starting a download and I get the 502 while it is searching for peers, I will try again rather than wait for the default (appears to be 30 mins) countdown for a retry.

From a client perspective, I believe that reducing the number of active seeding torrents does help. AND remember that for an individual torrent, the client will retry the connection after the timeout countdown had completed.
From a tracker perspective, taint much we end users can do. Aside from hardware / software issues, the load is the load, it ebbs and flows with time.

While I do not know the tracker software personally, empirically, it looks like if many requests that come from an individual client, past a certain number those request get pushed to the bottom of the request queue so all clients can get a fair shake at the tracker. (IMHO)