Trying the page again will often be successful.
Then try opening the web page again.
A simple restart of the web client program itself could solve the problem.
Clearing the Cache in Edge.
Clear your web app’s cache.
Outdated or corrupted files that are being stored by your web client could be causing 502 Bad Gateway issues.
Removing those cached files and trying the page again will solve the problem if this is the cause.
Delete your internet tool’s cookies.
For similar reasons as mentioned above with cached files, clearing stored cookies could fix a 502 error.
Start your web client in Safe Mode: We have instructions forFirefox,Chrome, orEdge.
Internet Explorer in Safe Mode.
Try another web client.
Popular browsers include Firefox, Chrome, Edge, Opera, and Safari.
In these cases, a restart would help.
power cycle your networking equipment.
A simple restart of these devices could help.
Check out that link above for more detailed help on restarting your equipment if you need it.
Change your DNS servers, either on your router or on your gear or gear.
Some Bad Gateway errors are brought on by temporary issues with DNS servers.
Contacting the website directly might also be a good idea.
Most websites have social networking accounts they use to help support their services.
Some even have telephone and email contacts.
There areother ways to see if a website is downif social media isn’t helpful.
Contact your internet service provider.
SeeHow to Talk to Tech Supportfor tips on talking to your ISP about this problem.
What Does a 502 Bad Gateway Error Look Like?
Each website can customize the 502 Bad Gateway.
While it’s fairly uncommon, different web serversdo describe this error differently.
What Causes a 502 Bad Gateway Error?
Bad Gateway errors are often because of issues between online servers that you have no control over.
You may have the wrong URL, so try searching for the site from a search engine.
See if the site is working for others; if so, get in touch with the webmaster.
