What is the 502 bad gateway error? Bad 502 gateway errors occur when the webserver your browser is connected to acts as a proxy to relay information from other web servers, but it is receiving a bad response. Such errors are known as 502 errors because that is the HTTP status code used by the webserver to indicate them.
This bad response can be caused by several different reasons.
- Perhaps the server is overloaded.
- There is a network issue between the two servers, and the issue is just temporary.
- There may also be a firewall that configures correctly
- Coding error, and this problem will not be repaired until the problem is solved.
As with 404 errors, website designers can customize the appearance of 502 errors. Therefore, you may see 502 different pages on different websites. The website might also use a name that is slightly different for this error. You might come across the following, for example:
- HTTP 502 bad gateway error
- HTTP 502.
- 502 services while overloaded
- Temporary mistake (502)
- 502 Server Error: The server is experiencing a temporary problem and is unable to finish your request.
- 502 Bad Gateway Nginx
These errors are often the result of errors on the server-side. Sometimes, this is a temporary mistake; sometimes it isn’t. However, there are several things you can try at your end as well.
Cause of 502 bad gateway errors
Before you can fix 502 bad gateway issues, you must first rule out any possible causes, such as:
- Unresolved domain names: This happens when the domain name is not resolved to the correct IP. Keep in mind that your DNS change might take up to 24 hours to be fully reproduced and active if you have just migrated your domain name to another host.
Overloading of the original server: When the server runs out of resources, it can be overloaded and crash, resulting in error 502. There are several general reasons for excess servers, including sudden traffic spikes, low memory, and software deadlines.
- Browser Error: Sometimes, the browser might show 502 errors even though it doesn’t have a server or network problem. In this case, errors may be triggered by broken browser extensions such as ad-blockers, an outdated browser version, or a damaged file in your browser cache.
- Home-network equipment problems: If you experience 502 errors in more than one website or browser, there is a good probability that your network equipment may have a temporary connection problem.
- Block firewall: A firewall protects your website from suspicious traffic. However, some firewall systems are very sensitive and may detect false positives. The system might block certain ISPs or requests from CDN.
How to Fix 502 Bad Gateway Error
Although 502 bad gateway errors are usually related to server-side problems, they can also be caused by configuration errors or problems from the client side. Therefore, we will review the troubleshooting steps with both causes in mind.
While some solutions are specific to WordPress, the majority may be utilized on any website.
1. Refresh the page
The first solution is quite straightforward – you simply have to wait a few minutes, refresh your browser, and try again. Errors were often caused by sudden traffic surges.
Thus, a simple page refresh will usually do the trick. Windows users can press F5 or Ctrl + F5 for shortcuts, while Mac users can press CMD + R.
You can also use online tools such as planet websites or host trackers to see if the website is down. This will help identify whether the server or client-side problems cause errors.
2. Delete browser cache
If the error continues, your browser cache may have saved an outdated and damaged file. In this case, cleaning the browser cache can fix a bad 502 gateway error.
Keep in mind that removing cache may risk losing important browser data, including bookmarks and preference settings. To prevent this, just export your data from the browser and import it back after.
3. Try in Incognito mode
Using incognito mode while browsing the Internet can also help to identify whether the 502 error notice appears as a result of a browser problem. On your browser screen, click the Three-Point button and select a new disguising window.
If an error does not occur in disguise mode, the problem may be caused by the browser extension. With that thought, try to deactivate your add-on or extension gradually. After you delete the extension causing the error, you should be able to access the website.
If deactivating the extension does not help, try opening a different browser. For example, if you are currently on Google Chrome, try using Mozilla Firefox.
When the page contains normal in a new browser, your previous browser might cause an error. To solve the problem, try to delete and reinstall your wrong browser.
4. Flush DNS
502 DNS issues, such as the erroneous IP address or an unresponsive DNS server, can potentially cause a Bad Gateway Error.
In this case, your DNS cache flushing can help resolve the error. This method works together to clean your browser’s cache. It will delete the damaged file from your DNS server.
Changing your DNS server is another step you can take. DNS servers are assigned by default by your ISP. However, you can always change it to a third-party server, like Google’s public DNS.
5. Test on Other Devices
If no other options exist for repairing 502 bad gateway issues, try connecting additional computers or mobile devices, ideally on separate networks.
Try restarting your PC and other network equipment. To do this, turn off your computer and remove your wireless router again. Wait a minute before replacing it.
This step helps decide whether this error is related to your network equipment or if the problem is somewhere else.
6. Check the Error Log
The problem may be on your server when you get 502 bad gateway problems after making certain modifications or updates. The best approach to this problem is to check your error log.
Usually, your hosting service provides access to activate the website error log through the admin dashboard. You can also enable errors when entering on your WordPress site by adding the following lines on wp-config.php:
define (‘wp_debug’, right);
define (‘wp_debug_log’, right);
Defining (‘wp_debug_display’, false);
All of the problems that arise will show up in the WP-contents / debug.log file, allowing you to figure out which one is causing the 502 bad gateway errors.
7. Check the Plugins and Themes
Sometimes, the wrong plugin or theme can be one reason for the 502 bad gateway error. It is because coded plugins and themes cannot conflict with each other. When this happens, your server will stop each script and query on your website, making it inaccessible.
For some websites, this problem usually comes from caching or security plugins. This plugin likely blocks communication between the server, causing an error to survive.
If you don’t have a caching or security plugin installed but are still getting 502 problems, removing each plugin individually is the easiest thing to do. To do this, go to the plugin and click Disable from the mass action menu.
8. Check CDNs
502 bad gateway failures might also be caused by a problem with your CDN or DDoS mitigation provider.
Content networks add additional layers between your server and browser to submit web content efficiently. However, this layer can experience problems when connecting with your home server, generating 502 errors.
Cloudflare is a good example, where the faulty 502 gateway might take two distinct forms depending on the issue.
9. Check the Site Status
If the 502 error still appears even though it tries most of the methods so far, the original server may now experience downtime.
The web provides many tools to check whether a site is down, including whether it is down for everyone or just me. Check the status of your website by entering your URL.
10. PHP max_execution_time and max_input_time
The PHP deadline occurs every time the PHP process contains more than the specified max_execution_time or max_input_time. This is the value specified in your PHP configuration on your web server. Usually, values are set to 300 seconds by default.
The deadline can occur during the migration process and trigger poor 502 gateway errors. To fix this problem, you can talk to your web host to check your value set and increase it.
11. Contact Customer Support
It is best to contact customer support if there is no solution above which fixes 502 bad gateway errors.
While explaining this problem, try to enter the troubleshooting step you have taken. Provide as much information as possible, and let the support team help you.
The Final Word
However, when a gateway server receives an erroneous response from the original server, a 502 bad gateway error occurs. If not treated, this error will have an impact on your conversion rate, user experience, and page rank.
According to the status code, the cause of this error usually lies on the server. In other words, the problem is not caused by your website, internet connection, or computer. Therefore, it is also important to pay attention to any damaged plugins or themes.