Error Number 502
Contents |
the UK edition switch to the US edition switch to the AU edition International switch to the UK edition switch to the US edition switch to the Australia edition The Guardian home › tech home UK world sport football opinion culture business lifestyle fashion environment tech 502 bad gateway nginx selected travel browse all sections close Computing Ask Jack 502 Bad Gateway error: what to do when 502 bad gateway meaning you can't get through to a website Viv is trying to reach Freecycle but is getting a 502 Bad Gateway error. If you can't get
502 Bad Gateway Fix
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 Jack Schofield Thursday 1 August 2013 16.03 BST Last modified on Thursday 1 August
502 Bad Gateway Nginx Means
2013 16.39 BST 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 sort this out? Viv The 'Bad Gateway' error is coming from the server, and usually has nothing to 502 bad gateway php 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 crashed, in which case, nobody else can get through either. In some cases, you might still be able to get the information you need, either by using the version cached by a search engine such as Go
the UK edition switch to the US edition switch to the AU edition International switch to the UK edition switch to the US edition switch to the Australia edition The Guardian home › tech home UK world sport football opinion culture business lifestyle fashion environment tech selected travel browse all
502 Bad Gateway Nginx/1.4.6 (ubuntu)
sections close Computing Ask Jack 502 Bad Gateway error: what to do when you can't get through 504 bad gateway to a website Viv is trying to reach Freecycle but is getting a 502 Bad Gateway error. If you can't get through to a website, here error 502 gmail are five things you can try.... This type of error comes from the server, and usually has nothing to do with your PC Jack Schofield Thursday 1 August 2013 16.03 BST Last modified on Thursday 1 August 2013 16.39 BST Share on Facebook Share https://www.theguardian.com/technology/askjack/2013/aug/01/502-bad-gateway-error 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 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 https://www.theguardian.com/technology/askjack/2013/aug/01/502-bad-gateway-error 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 crashed, in which case, nobody else can get through either. In some cases, you might still be able to get the information you need, either by using the version cached by a search engine such as Google (click the down-arrow next to the web address), or by using a copy of the site archived at the Wayba
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 https://www.keycdn.com/support/502-bad-gateway/ 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 (Hotlink Protection) Delete a Zonereferrer Debugging CDN Troubleshooting Guide Technical Questions CDN Error Codes KeyCDN Log Format KeyCDN Log Forwarding bad gateway 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 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 502 bad gateway 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 (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 c