When you open a website, here’s what happens behind the scenes:<\/p>\n\n\n\n
The browser sends a request to the hosting server. Normally the server will respond with HTTP (HyperText Transfer Protocol) status codes<\/a> and the resources (or page) you requested. But sometimes the server may respond with a 502 error. It typically happens when the server takes a long time to fetch the page. <\/p>\n\n\n\n This delay in response could have occurred because of reasons like a server issue, plugin conflict, DNS, PHP issues, etc. <\/p>\n\n\n\n\t\t The 502 error affects your visitors as they are unable to get the information they came for. As a result, they abandon your website quickly. <\/p>\n\n\n\n Search engines will notice this behavior and soon enough your rankings will drop. Needless to say, this chain of events will cause a significant dip in your revenue collection. <\/p>\n\n\n Now that we’ve talked a bit about what a 502 bad gateway error is in WordPress, let’s look at the most common causes.<\/p>\n\n\n\n The server where your website is hosted could be down. <\/p>\n\n\n\n This is not unusual. <\/p>\n\n\n\n The hosting server could have been taken offline intentionally for maintenance purposes, like updating the server’s security system. <\/p>\n\n\n A hosting server<\/a> is a piece of complex equipment that may be damaged and require replacement or repairs. If your hosting server is undergoing repairs, then you are likely to see a 502 error on your website. <\/p>\n\n\n\n There is a chance that high traffic to your website caused server overload and rendered it unable to respond. <\/p>\n\n\n Themes and plugins<\/a> are what make WordPress so popular. But themes and plugins are also the reason why a website crashes or throws an error sometimes. <\/p>\n\n\n\n We have seen far too many poorly coded themes or plugins overwhelming the server which then throws a 502 error. <\/p>\n\n\n PHP is a programming language. In fact, all plugins and themes contain a bunch of PHP files. When you install or update a plugin or theme, some of these PHP files start running. <\/p>\n\n\n\n PHP code can run for a long time and use a significant chunk of your hosting server’s resources. To prevent abuse of server resources, hosting providers put a cap on how long a PHP code can run. When the code hits the limit, the server throws a 502 error. <\/p>\n\n\n CDN (Content Delivery Network)<\/a> helps make your website faster. Some CDNs, like Cloudflare, focus heavily on security; therefore, they also offer firewall protection. <\/p>\n\n\n\n Since a CDN sits between your hosting server and the browser, any request made on your website will first have to pass through the CDN. <\/p>\n\n\n\n So when you open your website while the CDN server is down, your request will generate a 502 error. <\/p>\n\n\n Occasionally, browsers throw 502 errors too. This typically happens because of a corrupt extension, like ad-blockers<\/a>, corrupt cache, or outdated browser. <\/p>\n\n\n DNS issues are rare. They occur when you switch domain registrars or hosting providers. This can also occur when you are setting up a web application firewall like Cloudflare<\/a> or Sucuri.<\/p>\n\n\n\n Following a migration or firewall installation, you need to change the DNS nameservers and point them to your web host. It can take up to 24 hours for the nameservers to activate. If you open the website during this period, you are going to be welcomed with a 502 error. <\/p>\n\n\n On rare occasions, the 502 error occurs due to hardware or broadband connectivity issues. Most of the time, it’s a temporary glitch. <\/p>\n\n\n\n That’s all, folks!<\/p>\n\n\n Now that you have an idea of what could be causing the “502 bad gateway” error, let’s look at some of the possible solutions.<\/p>\n\n\n\n \u26a0\ufe0f We recommend:<\/strong> Make a backup of your entire website<\/a>. In the following tutorial, you will be dealing with the Quite often we have found that WordPress errors are nothing but a temporary glitch. <\/p>\n\n\n\n So, it’s possible that the error may have been automatically resolved, but you are still seeing it because your browser or WordPress is showing a cached version of your website. Therefore, clear your browser and website cache. And then, refresh the page. <\/p>\n\n\n\n We cover how to clear your browser cache in detail in the following guide<\/a>. When it comes to clearing your website cache, the exact place where you can do that will depend on the caching plugin that you’re using. Read more about this here<\/a>.<\/p>\n\n\n Sometimes, the solution to a seemingly complex issue is as simple as restarting your PC and router to fix it. Try that.<\/p>\n\n\n You can take advantage of the error logs<\/a> to narrow down the issue. All you need to do is enable logging by adding this code to your A file called Check whether your hosting servers are down by using one of these tools: Down or Not<\/a>, or Is It Down Right Now<\/a>, or Down For Everyone or Just Me<\/a>. <\/p>\n\n\n\n The server could have been taken offline for maintenance purposes. In that case, you should have received an email informing you about when the server will be up again. <\/p>\n\n\n\n Even if your hosting servers are up, speak to your hosting provider. Find out whether it’s a server issue and then fix it.<\/p>\n\n\n The truth is, you can’t fix poorly coded plugins and themes because you didn’t build them. What you can do is disable them. But how do you know which ones to disable? <\/p>\n\n\n\n Disable all the plugins and themes one by one. And check your website simultaneously. <\/p>\n\n\n\n When you see that the error is gone, you’d know which plugin or theme caused it. <\/p>\n\n\n\n We strongly recommend that you carry out this exercise on a staging site<\/a> to prevent damaging your live website further. <\/p>\n\n\n Open your website on different browsers. If the error persists then follow the instructions below.<\/p>\n\n\n\n There are three common browser issues that WordPress users typically face. Those are corrupt extensions like ad-blockers, outdated browsers, and corrupt cache. <\/p>\n\n\n\n Update your browser if there’s a newer version available. Also, try disabling ad-blockers and other extensions, one by one. Keep checking your website simultaneously. <\/p>\n\n\n To find out if your CDN server is down, you can check your CDNs status page, like Cloudflare System Status<\/a>. <\/p>\n\n\n\n Alternatively, try these tools: CDNPlanet<\/a> and Downdetector<\/a>.<\/p>\n\n\n\n Even if the CDN is up, it could still be a CDN issue. Try disabling the CDN. If the error vanishes, then talk to the support team, asking them to fix the issue on their end. <\/p>\n\n\n\n Migrated to a new hosting provider or domain registrar<\/a> recently? Then wait up to 24 hours for the DNS issue to be resolved automatically. And while you are at it, flush your DNS cache<\/a>. <\/p>\n\n\n You may think that increasing the PHP timeout limit will solve the issue. But hosting limits are not the problem here. The plugin or theme that demands more resources to process its PHP code is the main culprit. <\/p>\n\n\n\n The PHP limit exists to prevent abuse of your resources. Hence remove plugins and themes that threaten to exhaust your resources. <\/p>\n\n\n On rare occasions, when none of the solutions works, you need to hire professional help. Take a look at our guide on how to hire a WordPress developer<\/a>.<\/p>\n\n\n Fixing some website errors can be annoying and time-consuming. This is why we believe that every WordPress website should take daily backups<\/a> so that whenever you run into an error, you can simply restore your site back to normal. <\/p>\n<\/div>\n\n\n\nImpact of the “502 bad gateway” error <\/h2>\n\n\n\n
Causes of “502 bad gateway” error<\/h2>\n\n\n\n
\n
1. Server issues<\/h3>\n\n\n\n
![\"502](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2021\/06\/bluehost-maintenance-error.png\")
<\/figure><\/div>\n\n\n2. Poorly coded plugins and\/or themes <\/h3>\n\n\n\n
3. PHP timeout issues<\/h3>\n\n\n\n
4. CDN server issue<\/h3>\n\n\n\n
5. Browser issue<\/h3>\n\n\n\n
6. DNS error<\/h3>\n\n\n\n
7. Hardware & connectivity issues<\/h3>\n\n\n\n
How to remove the “502 bad gateway” WordPress error from your website?<\/h2>\n\n\n\n
wp-config<\/code> file which is a core WordPress file. You wouldn’t want to add to your trouble by messing up a core file. Make a backup. If things go south, you can simply restore the backup and start all over again.<\/p>\n\n\n\n\n
1. Clear cache<\/h3>\n\n\n\n
![\"clearing](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2021\/06\/clearing-chrome-cache.png\")
<\/figure><\/div>\n\n2. Fixing hardware & connectivity issues <\/h3>\n\n\n\n
3. Check your error log<\/h3>\n\n\n\n
wp-config.php<\/code> file: <\/p>\n\n\n\ndefine( 'WP_DEBUG', true );\ndefine( 'WP_DEBUG_LOG', true );\ndefine( 'WP_DEBUG_DISPLAY', false );<\/code><\/pre>\n\n\n![\"inserting](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2021\/06\/editing-wpconfig-file.png\")
<\/figure><\/div>\n\n\ndebug.log<\/code> will appear in your wp-content<\/code> directory. Open it, and it should tell you what’s causing the 502 Bad Gateway error.<\/p>\n\n\n4. Fixing server issues<\/h3>\n\n\n\n
5. Fixing poorly coded plugins and themes <\/h3>\n\n\n\n
6. Fixing browser issue<\/h3>\n\n\n\n
7. Fixing CDN server issue<\/h3>\n\n\n\n
![\"option](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2021\/06\/remove-site-from-cloudflare.png\")
<\/figure><\/div>\n\n\n8. Fixing DNS issue<\/h3>\n\n\n\n
9. Fixing PHP timeout issues <\/h3>\n\n\n\n
If the “502 bad gateway” WordPress error still persists<\/h2>\n\n\n\n
Conclusion<\/h2>\n\n\n\n