502 Bad Gateway mistake: what you should do whenever you can not make it through to a site
This sort of mistake originates from the host, and in most cases has nothing in connection with your computer
We keep getting a mistake message, 502 Bad Gateway nginx/0.7.67, whenever I you will need to access the Freecycle web web site. We have rebooted my PC and used ‘system restore’ many times, but have not had the oppertunity to clear it. Are you aware how exactly to sort this away?
The ‘Bad Gateway’ mistake is originating through the host, and often has nothing in connection with your computer. It may you need to be that your website is overloaded. Frequently, just refreshing or reloading the web page (Ctrl-F5) will continue to work, but often the nagging problem can continue for several days. If that’s the case, you can log the time(s) and browser version and submit a mistake are accountable to the website owner, because 502 mistakes is due to pests in the PHP that is associated development.