This tutorial is about How To Fix ‘502 Bad Gateway Error’ issue. Recently I updated this tutorial and will try my best so that you understand this guide. I hope you guys like this blog, How To Fix ‘502 Bad Gateway Error’ issue. If your answer is yes after reading the article, please share this article with your friends and family to support us.
Table of contents
Check How To Fix ‘502 Bad Gateway Error’ issue
A 502 bad gateway error means that the web server you are connected to is acting as a proxy to forward information from another server, but has received an incorrect response from that other server. The error is called a 502 because this is the HTTP status code that the web server uses to describe this type of error. It is possible that the server is overloaded or there are network problems between the two servers and it is only a temporary problem. It is also possible that there is a misconfigured firewall or a programming error, and the problem will not be fixed until these issues are resolved.
As with 404 errors, website designers can customize the appearance of a 502 error. Therefore, you may see different looking 502 pages on different websites. In the vast majority of cases, this is a server-side error that you can’t do anything about. Sometimes it’s a temporary bug, but sometimes it’s not. Still, there are a few things you can try on your own.
Fix ‘502 Bad Gateway Error’ issue
Refresh the page
The first solution is quite simple: wait a minute or two and refresh the page you’re on. In many cases, the error comes from a sudden increase in traffic. So a simple page refresh will usually do the trick. For a shortcut, Windows users can press F5 or CTRL + F5, while Mac users can press CMD + R.
You can also try to check if the website is offline using an online tool, such as Website Planet or Host Tracker. This will help identify if a server or client side issue is causing the error.
Clear browser cache
If the error persists, there is a possibility that your browser’s cache has saved outdated and corrupted files. In this case, clearing the browser cache can fix an HTTP 502 Bad Gateway error.
Please note that clearing the cache may risk losing important browser data, including bookmarks and settings preferences. To avoid this, simply export your data from the browser and import it later.
Try in incognito mode
Accessing the website using incognito mode is also a good idea as it helps determine if you are getting the http 502 error message due to a browser-related issue. To open an incognito window, click the three dots button on your browser screen and select New incognito window.
If the error does not occur in incognito mode, the issue may be caused by a browser extension. With that in mind, try disabling your plugins or extensions gradually. Once you remove the one causing the error, you should be able to access the website.
If disabling extensions doesn’t help, try opening a different browser. For example, if you are currently on Google Chrome, try using Mozilla Firefox. When the page loads normally in the new browser, your old browser may be causing the error. To resolve the issue, try removing and reinstalling your faulty browser.
Flush DNS
The 502 Bad Gateway error can also occur due to DNS issues such as bad IP addresses and unresponsive DNS servers. In this case, flushing your DNS cache may be the answer. This method works similarly to clearing your browser’s cache. It will remove the bad files from your DNS server.
Temporarily changing your DNS servers is another step you can take. By default, your DNS servers are assigned by your ISP. However, you can always change it to a third party server, like Google Public DNS.
Try on another device
If none of the above solutions fixed the HTTP 502 error, try the connection on another computer or mobile device, preferably connected to a different network.
Try restarting your PC and other network equipment. To do so, shut down your computer and unplug your wireless router. Wait a moment and reconnect them. This step helps you decide if the error is related to your network equipment or if the problem is somewhere else.
Check error log
When you experience a 502 Bad Gateway error after a particular change or update, the fault may lie within your own server. The best approach to this problem is to check your error log. Your hosting service usually provides access to enable website error logging through an admin panel. You can also enable error logging on your WordPress site by adding the following lines to wp-config.php:
define(‘WP_DEBUG’, true); define(‘WP_DEBUG_LOG’, true); define(‘WP_DEBUG_DISPLAY’, false);
All generated errors will appear in the wp-contents/debug.log file, allowing you to spot which ones are causing a 502 Bad Gateway error.
Check plugins and themes
Sometimes faulty plugins or themes can be one of the reasons for a 502 Bad Gateway error. This is because poorly coded plugins and themes can conflict with each other. When this happens, your server will stop all scripts and queries on your website, making it inaccessible.
For some websites, the problem usually comes from caching or security plugins. There is a good chance that these plugins will block communication between servers, which will cause the error to persist. If you don’t have a caching or security plugin installed, but still encounter an HTTP 502 error, it’s best to disable your plugins and re-enable them one by one. To do so, go to Plugins and simply click Disable in the Bulk Actions menu.
Then activate each plugin while updating your WordPress site after each one. Once the 502 error reappears, you have found the problematic plugin. However, if you can’t access your WordPress control panel, you can try disabling them from your hosting panel or FTP program. Navigate to the wp-content directory and rename the plugins directory, for example plugins-disable. If you use Hostinger, go to your hPanel and click on Files. From there go to File Manager -> public_html -> wp-content.
Once your site is up and running after all plugins are disabled, you can rename the folder to plugins. Then try enabling the plugins one by one to determine which one caused the error first. If the website still doesn’t work, follow the same steps with your WordPress themes.
Check site status
If the 502 error continues despite trying most of the methods so far, the origin server may be experiencing downtime. Fortunately, there are plenty of tools on the web to check if a site is down, including Down for Everyone or Just Me and IsItDown. Just enter your URL and check the status of your website.
Final remarks: How To Fix ‘502 Bad Gateway Error’ issue
I hope you understand this article, How To Fix ‘502 Bad Gateway Error’ issue. If your answer is no, you can ask anything via the contact forum section related to this article. And if your answer is yes, please share this article with your friends and family to give us your support.
