This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

WHAT IS 502 BAD GATEWAY

  • 6 vastausta
  • 26 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja cor-el

more options

I HAVE RESET FIREFOX AND IT STILL NOT WORKING. I KEEP GETTING 502 BAD GATEWAY, WHAT DOES THIS MEAN.

I HAVE RESET FIREFOX AND IT STILL NOT WORKING. I KEEP GETTING 502 BAD GATEWAY, WHAT DOES THIS MEAN.

Kaikki vastaukset (6)

more options

Most of the time this is a problem on the sites end. One way to tell is try it one more time in Firefox then try it in anther browser. If it does not work in ether then it is not a problem with the browser.

more options

My town got hit by a tornado and a lot of lines are down could this be why I keep getting the message 502 bad gateway.

more options

The 502 Bad Gateway error is an HTTP status code that means that one server received an invalid response from another server that it was accessing while attempting to load the web page or fill another request by the browser.

Try loading the URL again by pressing F5 on your keyboard, or by clicking the refresh/reload button.

While the 502 Bad Gateway error is usually indicating a networking error outside of your control, it could be extremely temporary. Trying the page again will often be successful.

Ways you can fix

1. Start a new browser session by closing all open browser windows and then opening a new one. Then try opening the webpage again.

2. It's possible that the 502 error you received was due to an issue on your computer that occurred sometime during this use of your browser. A simple restart of the browser program itself could solve the problem.

3. Clear your browser's cache. Outdated or corrupted files that are being stored by your browser could be causing 502 Bad Gateway issues.

4. Removing those cached files and trying the page again will solve the problem if this is the cause.

Hope this helps!

more options

It could be. as CoryGoulding said, it means one server along the way could not get in contact with the next. At lest that is what it is most of the time.

more options

I also got the 502-error when accessing http://www.microsoft.com or http://msdn.microsoft.com.

i tracked down the error to a wrong preference:

in prefs.js there was an entry intl.accept_languages including two UTF-BOM bytes somwhere in the list. i removed them and now it's working again.

don't know where it came from all of a sudden. probaly a buggy extension. just put that info here for the records.

more options

You can also try to lower the maximum number of connections.

  • about:config page: network.http.max-connections

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.