This is dependent on the TTL, or time to live, defined per record. It is important to note that DNS changes could take same time until they are global fully propagated and active.

Domain name not resolvable: The domain name is not resolving to the correct IP or it does not resolve to any IP.

Three main culprits cause 502 Bad Gateway responses. What are the reasons for 502 Bad Gateway responses? The most common cause of this issue is an incorrect or outdated DNS record.

In other words, something went wrong while the server was trying to relay information to another server (usually an upstream server). Usually, a 502 Bad Gateway error code is accompanied by a message letting you know that a 'bad gateway' exists. To better understand how Ke圜DN handles certain error codes, check out our CDN Error Codes page. If one of Ke圜DN's edge servers receives a 502 Bad Gateway response from your origin server, Ke圜DN will return a 500 Origin Not Reachable page. This can occur for a few reasons, which we'll discuss below. What does 502 Bad Gateway mean?Ī 502 Bad Gateway indicates that the edge server (server acting as a proxy) could not get a valid or any response from the origin server (also called the upstream server).

In this article, we'll take a look at what a 502 Bad Gateway error code is and how you can go about solving it on your own. While the error can be frustrating, the good news is that it's usually easy to fix. This is especially true if you frequently visit websites known to be unreliable. If you browse the internet long enough, you'll run into a 502 Bad Gateway error code.

Remote for mac wrong host error