Jump to content

Outbound HTTP Error 502 on some regions.


Phate Shepherd
 Share

You are about to reply to a thread that has been inactive for 1319 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

I'm encountering a few customers that are getting http error 502 when product communicates with my server. This started after changing where the DNS pointed from one server to another commercial hosting service. All logs are clean on the host, so I don't know where the communication is breaking down. In one instance, the person having the problem got their region restarted and the problem went away. Two others restarted or had their regions restarted, but it didn't fix it. I don't know yet if they are on full or homestead regions, and if that would change the results. (Maybe restarting a homestead doesn't restart the proxy?)

 

The body of the 502 error:

<html>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</meta>
<title>ERROR: The requested URL could not be retrieved</title>
<body id="ERR_READ_ERROR">
<div id="titles">
<h1>ERROR</h1>
<h2>Read Error</h2>
</div>

<p><b>Read Error</b></p>

<!-- ERR_READ_ERROR -->
</body></html>

 

 

Link to comment
Share on other sites

20 minutes ago, Oz Linden said:

This is most likely DNS caches not updating to your new server uniformly; it should correct itself in time.

That's the thing... it's been 5 days, and the TTL on the DNS records were set to an hour LONG before the change... and even if it was pointing to the old server, it is still up, so it would service the call.

One of the people having the issue restarted their region and it went away. I've got a ticket open to have it checked out on the region Carbonara before it restarts and possibly fixes itself. There is something going on here that isn't DNS caching related.

OHH, and another domain on the same server that hasn't changed in many years also gives the same 502 error on the troublesome regions.

Edited by Phate Shepherd
Link to comment
Share on other sites

For those googling in the future for the cause of http 502 errors in their scripts, it was finally determined to be a firewall issue at the hosting company. After they found and removed the IP address of that particular simulator from their firewall, the error went away. Many thanks to Maestro.

Edited by Phate Shepherd
  • Thanks 1
Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 1319 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...