This time, we know the Freecycle site is working, because it's running Nginx (pronounced Engine-X) version 0.7.67 software. 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 Wayback Machine. 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. Either way, it's useful to have a few things to try when you can't get through to any website. It might be that doing them is simply introducing a delay and the site would have worked if you hadn't bothered. It's hard to know whether they actually work. 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. In this case, email the admin team at If it's an intermittent fault, the simplest option is to wait for 10 minutes and then try again. 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. Often, simply refreshing or reloading the page (Ctrl-F5) will work, but sometimes the problem can persist for days. It may just be that the site is overloaded. The 'Bad Gateway' error is coming from the server, and usually has nothing to do with your PC.
0 Comments
Leave a Reply. |