Bad Gateway Error 502
Contents |
to the AU edition switch to the INT edition US edition switch to the UK edition switch to the Australia edition switch to the International The Guardian home › tech home election 2016 US world opinion sports soccer bad gateway error 502 citrix tech selected arts lifestyle fashion business travel environment browse all sections close Computing Ask Jack proxy 502 error 502 Bad Gateway error: what to do when you can't get through to a website Viv is trying to reach Freecycle but is
Http Error 502/504 Bad Gateway
getting a 502 Bad Gateway error. If you can't get through to a website, here are five things you can try.... This type of error comes from the server, and usually has nothing to do with your PC
Request Failed Bad Gateway (502)
Jack Schofield Thursday 1 August 2013 11.03 EDT Last modified on Thursday 1 August 2013 11.39 EDT Share on Facebook Share on Twitter Share via Email Share on LinkedIn Share on Google+ Share on WhatsApp Share on Messenger I keep getting an error message, 502 Bad Gateway nginx/0.7.67, when I try to access the Freecycle site. I have rebooted my PC and used 'system restore' several times, but haven't been able to clear it. Do you know how to the server responded with a status of 502 (bad gateway) sort this out? Viv The 'Bad Gateway' error is coming from the server, and usually has nothing to do with your PC. It may just be that the site is overloaded. Often, simply refreshing or reloading the page (Ctrl-F5) will work, but sometimes the problem can persist for days. If so, you could log the time(s) and browser version and submit an error report to the webmaster, because 502 errors can be caused by bugs in the associated PHP programming. In this case, email the admin team at myfreecycleadmin@freecycle.org. If it's an intermittent fault, the simplest option is to wait for 10 minutes and then try again. There are a few things that you can do to try to get through to a site when you get a 502 Bad Gateway error. It's hard to know whether they actually work. It might be that doing them is simply introducing a delay and the site would have worked if you hadn't bothered. Either way, it's useful to have a few things to try when you can't get through to any website. Has it crashed? One of the first things I do when a site isn't responding is to paste its web address or URL (Uniform Resource Locator) into the box at Down for everyone or just me? This will check the site and tell you if it has
Zone Create a Push Zone Upload Data to a Push Zone Delete a Push Zone Push Zone Settings Push Zone Subusers Pull Zone Create a Pull Zone Delete a Pull Zone Purge CDN Cache Pull Zone Settings CNAMES Create a Zonealias Delete
What Does 505 Bad Gateway Mean
a Zonealias Zone Security How to setup Let's Encrypt TLS How to setup Custom error 502 bad gateway blackberry SSL How to order a SSL certificate Secure Token Create a Zonereferrer (Hotlink Protection) Delete a Zonereferrer Debugging CDN Troubleshooting Guide Technical 502 bad gateway nginx Questions CDN Error Codes KeyCDN Log Format KeyCDN Log Forwarding Configure your own Syslog Server Getting Started General Account Management Integration Guides CMS Integration Guides Framework Integration Guides Custom CDN Integration CDN How To's Tutorials Zone https://www.theguardian.com/technology/askjack/2013/aug/01/502-bad-gateway-error Configuration General Settings Push Zone Create a Push Zone Upload Data to a Push Zone Delete a Push Zone Push Zone Settings Push Zone Subusers Pull Zone Create a Pull Zone Delete a Pull Zone Purge CDN Cache Pull Zone Settings CNAMES Create a Zonealias Delete a Zonealias Zone Security How to setup Let's Encrypt TLS How to setup Custom SSL How to order a SSL certificate Secure Token Create a Zonereferrer https://www.keycdn.com/support/502-bad-gateway/ (Hotlink Protection) Delete a Zonereferrer Debugging CDN Troubleshooting Guide Technical Questions CDN Error Codes KeyCDN Log Format KeyCDN Log Forwarding Configure your own Syslog Server Knowledge Base Support/Debugging How to solve 502 Bad Gateway Issues? Updated: July 20, 2016 Comments: 1 What does 502 Bad Gateway mean? A 502 Bad Gateway indicates that the edge server (server acting as a proxy) was not able to get a valid or any response from the origin server (also called upstream server). KeyCDN returns a 500 Origin Not Reachable if a 502 Bad Gateway occurred. What does 502 Bad Gateway mean? What are the reasons for 502 Bad Gateway responses? Domain name not resolvable: The domain name is not resolving to the correct IP or it does not resolve to any IP. It is important to note that DNS changes could take same time until they are global fully propagated and active. This is very dependant on the DNS TTL defined per record. Origin server down: The server is not reachable, either because it is down or there is no connectivity to the server given. Firewall blocks request: A firewall blocks the communication between the edge servers and the origin server. This can also be caused by security plugins of your CMS. Some DDOS protection and mitigation syst
This server received an invalid response from an upstream server it accessed to fulfil the request. This usually does not mean that the upstream server http://www.checkupdown.com/status/E502.html is down (no response to the gateway/proxy), but rather that the upstream server https://www.maxcdn.com/one/tutorial/502-bad-gateway/ and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed. Fixing 502 errors - general This problem is due to poor IP communication between back-end computers, possibly including the Web bad gateway server at the site you are trying to visit. Before analysing this problem, you should clear your browser cache completely. If you are surfing the Web and see this problem for all Web sites you try to visit, then either 1) your ISP has a major equipment failure/overload or 2) there is something wrong with your internal Internet connection e.g. your firewall is not functioning correctly. In bad gateway error the first case, only your ISP can help you. In the second case, you need to fix whatever it is that is preventing you reaching the Internet. If you get this problem for only some of the Web sites you try to visit then it is likely to be a problem at those sites i.e. one of their pieces of equipment is failing/overloaded. Contact the people at those sites. Fixing 502 errors - CheckUpDown Our service monitors your site for HTTP errors like 502. Use of proxies and caching is increasing on the Web. Our CheckUpDown robot will always try to "drill through" to the real computer that actually hosts the Web site, but we do not have complete control over where our HTTP request actually ends up. If only one link in the chain of computers dealing with our HTTP request is broken, then an error such as 502 can easily occur. Please contact us (email preferred) whenever you encounter 502 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of the Web server software so that they can review the flow of IP
Network Status + Development Resources Submit a Demo API Docs Log In Free Test Account Back to MaxCDN Search ... Cancel Menu Browse Articles Browse Articles Pull How to Create a Pull Zone Wordpress Integration Other CMS Custom CDN Integration Pull Zone Settings Pull Zone Security Cache-Busting How to use CDN with Webfonts Push Create a Push Zone Connect to Push Zone Push Zone Settings Reset Push FTP Password Push Zone Security VOD Create a VOD Zone Connect to VOD Zone Get VOD Zone Embed Code Reset VOD FTP Password EdgeRules Edge Rules Recipes EdgeRules Conditionals EdgeRules Purge Cache EdgeRules Priority EdgeRules Status EdgeRules Features EdgeRules Location EdgeRules Match Type Delete an Edge Rule Debugging Troubleshooting the 502 Bad Gateway 403 Forbidden CDN Slowness/Bad Performance Guides What is Anycast? What is a CDN? Change Credit Card details Custom Expiry Headers Custom Error Page Enable GZip Compression Enable SPDY Enabling Two-Factor Authentication Enabling More Locations Fix broken CA chain Use SEO with CDN API Developer Visual Glossary Tutorial Troubleshooting the 502 Bad Gateway Ivan Dabic August 12, 2014 Updated February 9, 2015 The 502 Bad Gateway Error means that that our network is unable to communicate with your server. This tutorial will show you how to troubleshoot that unwanted response. The 502 Bad Gateway response can occur due to one of two reasons: Change of the Origin IP:
If you change hosts, move to a dedicated IP address, start using a Load Balancer, start using CloudFlare, or anything that would cause your origin server's IP address to change, the CDN will stop functioning and you will encounter a 502 Bad Gateway Error. In this case, you need to update the Origin IP in the Pull Zone configuration to match the new IP. Firewall blocking our servers: As a part of a DDoS mitigation process, or as a result of some strict firewall rules, our servers can be blocked from accessing the origin web server. In this case, you just need to whitelist our subnets in your firewall rules. Also, worth mentioning is that some security plugins (for the CMS you use - if you use any) for DDoS mitigation may act the same as firewall is blocking us. What To Do When You Get 502 Error The first thing to do when you get the 502 error is to check your origin IP in the zone management, click on Settings and make sure the IP address is correct. Should it be found incorrect, you need to update the Origin IP in the Pull Zone configuration to match the new IP, purge your zone cache, and try again. This should fix the prob