<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[502 Error code]]></title><description><![CDATA[<p dir="auto">Is there any way to prevent getting the 502 error code?  I assume I lose any seed point while the torrent is showing this?</p>
]]></description><link>https://community.gaytor.rent/topic/22102/502-error-code</link><generator>RSS for Node</generator><lastBuildDate>Wed, 08 Apr 2026 11:08:57 GMT</lastBuildDate><atom:link href="https://community.gaytor.rent/topic/22102.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 10 Nov 2015 23:27:34 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to 502 Error code on Tue, 12 Apr 2016 21:04:58 GMT]]></title><description><![CDATA[<p dir="auto">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. <br />
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<br />
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.</p>
<p dir="auto">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. <br />
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.</p>
<p dir="auto">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)</p>
]]></description><link>https://community.gaytor.rent/post/171639</link><guid isPermaLink="true">https://community.gaytor.rent/post/171639</guid><dc:creator><![CDATA[youngla]]></dc:creator><pubDate>Tue, 12 Apr 2016 21:04:58 GMT</pubDate></item><item><title><![CDATA[Reply to 502 Error code on Tue, 12 Apr 2016 19:22:43 GMT]]></title><description><![CDATA[<p dir="auto">I see it in my torrent program all the time<br />
<em><strong>Tracker returned error: Tracker gave HTTP response code 502 (Bad Gateway)</strong></em></p>
<p dir="auto">If there's any way I can avoid it I'd love to know how<br />
(Using Transmission 2.84 on a Mac)</p>
]]></description><link>https://community.gaytor.rent/post/171635</link><guid isPermaLink="true">https://community.gaytor.rent/post/171635</guid><dc:creator><![CDATA[1hotstud 0]]></dc:creator><pubDate>Tue, 12 Apr 2016 19:22:43 GMT</pubDate></item><item><title><![CDATA[Reply to 502 Error code on Wed, 11 Nov 2015 09:35:21 GMT]]></title><description><![CDATA[<p dir="auto">Are you seeing this error code in your web browser or in your torrent program?</p>
<p dir="auto">If it's in your browser only, it wouldn't affect any torrent data traffic credit.</p>
<p dir="auto">I've  never heard of anyone seeing this error in their torrent client program…</p>
<p dir="auto"><a href="http://www.theguardian.com/technology/askjack/2013/aug/01/502-bad-gateway-error" rel="nofollow ugc">http://www.theguardian.com/technology/askjack/2013/aug/01/502-bad-gateway-error</a></p>
<p dir="auto">Take care,<br />
Pawpcorn</p>
]]></description><link>https://community.gaytor.rent/post/156379</link><guid isPermaLink="true">https://community.gaytor.rent/post/156379</guid><dc:creator><![CDATA[Pawpcorn]]></dc:creator><pubDate>Wed, 11 Nov 2015 09:35:21 GMT</pubDate></item></channel></rss>