How to Fix the 502 Bad Gateway Error in WordPress?

How to Fix the 502 Bad Gateway Error in WordPress?

There are several possible solutions to the 502 bad gateway error. All the practical and potential solutions are shown in this article. 

You will have to go through stepwise until you land on the right and effective solution for your error. These solutions will redeem this complex error.

Ready? Let’s begin!

What is the 502 Bad Gateway Error? 

What is a 502 error? When the WordPress hosting server gets an invalid response for the requested page, it triggers the 502 Bad Gateway Error. 

The 502 Bad Gateway Error is quite annoying as it can be caused due to many reasons. That’s why Troubleshooting the 502 Bad Gateway Error can take a long time.  

Depending on your server, 502 Bad Gateway Error may seem different in terms of the error message as multiple reasons cause this error.

When we want to visit a website, our browser sends requests to the server that is hosting that particular site.

 In case everything is working fine, the server sends back the request with the information required by our browser to load the website we desire.

502 Bad Gateway error can hamper your website accessibility. Your website accessibility impacts your traffic as well as sales. Learn how to make your site more accessible.

Now if the server sends back an invalid response to our browser, it would fail to comprehend that information and will move to 502 Bad Gateway Error. It all might seem straightforward, but your browser’s connection from your computer to the server hosting is not that simple.

For example, your browser’s request may get routed through a proxy server before reaching the host server. This makes it tough to identify the issue. 

Moreover, many websites nowadays rely on multiple servers making the issue hard as any of them can cause problems.   

Variations in 502 Bad Gateway Error

Due to variations in browsers, web servers, and OS, a 502 Bad Gateway Error can present itself in several different ways having the same meaning. 

The list below shows the couple of many variations it can show on screen:

  • “502 Bad Gateway”
  • Error 502.”
  • “HTTP Error 502 – Bad Gateway”
  • “502 Service Temporarily Overloaded”
  • “502 Proxy Error”

Another message you might see as “502 server error.”

Causes of 502 Bad Gateway Error

Just like Error 400 or any other Error on the Internet, there can be a lot of factors leading to the errors.

The possible few causes that can indulge you in this tricky problem can be :

  1. Any errors in your database that you might be unaware of. 
  2. A timed-out server that might be currently unavailable, not responding as you intend.
  3. The servers can get overloaded by too many requests that fail to respond to the requests.
  4. Any problem in the reverse proxy server can also be a cause.
  5. Any of your themes or plugins can also cause faulty PHP scripts.

A piece of good news for you is that if the problem is caused on the server end, you wouldn’t have to do a lot. If the servers are causing issues, the hosting server will probably respond and rescue the requested URL.

Get in touch with your host’s support team as you encounter 502 Bad Gateway Error. If you are being let down by the error and nothing works, follow Bet 365‘s footsteps and contact your hosting server right away to nip it in the bud. 

Fixing the 502 Bad Gateway Error

Now we will start different troubleshooting steps to find the problem.

Step 1: Reload Your Website

The server you are accessing may take longer to respond sometimes due to increased traffic or low server resources. In that case, the error may vanish automatically in a while. You should simply reload the page that you are trying to access. 

You will be able to view the page just by reloading if this was the cause. You don’t need to go for further steps if your problem is fixed. However, I suggest that if this is not your first time with this error, keep reading as there is something else that needs fixing.

Step 2: Clear Browser Cache

The browser from the cache could display the error page. You will see the 502 error because the browser is loading the website you requested from the cache.

To get this fixed, Windows/Linux operating system, users can press Ctrl + F5 buttons. At the same time, Mac OS users can refresh the page by pressing CMD + Shift + R  buttons on their keyboards. The cache can be deleted manually as well from the browser settings. 

After clearing the WordPress cache, try reloading the website again. You can also use a different browser to troubleshoot the problem. However, if you see the error on more than one browser, then continue reading. 

To learn more about how to clean cache from any browser, we got something for you.

Step 3: Disable the CDN or Firewall 

The CDN service or the website firewall servers can act as possible for the CDN service or the website firewall servers to act up. To check this, you will have to disable CDN temporarily. 

After disabling, it will remove the additional layer between your browser and the hosting server. The website will now load entirely from your server. If the 502 error were caused by CDN / firewall service, it would get resolved. 

Once the problem is solved, you can enable the CDN again after moving ahead. 

Step 4: Update WordPress Themes and Plugins

If the error still exists, now you need to check your themes and plugins. First of all, deactivate all WordPress plugins via FTP. Now, visit your website to see if the error is gone. If it is, then one of the plugins was causing the issue. 

If deactivating plugins didn’t solve the problem, then you need to check your WordPress theme. Switch your WordPress to the default theme. Then visit your website to see if it’s working. 

Step 5: Check Hosting Server

If the steps mentioned above didn’t remove the error, then it is an issue with the hosting server. All good WordPress hosting companies will quickly fix the problem that is caused due to a server misconfiguration.


As there are quite a few things, you can do to troubleshoot a 502 Gateway Error. This is not on the client-side only, but rather an issue with your host. Third-party plugins and themes with bad code or unoptimized queries are also things to look out for.