A 502 Bad Gateway error occurs when Cloudflare is unable to contact the origin web server.
If you're seeing this error message on your website, the 502 Bad Gateway error can hurt your SEO if you don't fix it as soon as you see it.
This is because if you leave the 502 Bad Gateway error unattended for too long, Google will see this as a site-level problem, which will bruise your SEO ranking.
In this context, we shall look into how to fix the 502 Bad Gateway Cloudflare error.
Cloudflare returns an HTTP 502 or 504 error when the origin web server responds with a standard HTTP 502 bad gateway or 504 gateway timeout error.
This means that the server you were trying to connect to was acting as a proxy or gateway for another server, but it got a bad response from the other server.
A few reasons for this error include:
1. Excessive server load.
2. Firewall restrictions - Firewall might have been improperly configured.
3. There might be network issues between the servers.
The exact steps to be followed to resolve the 502 error depend on the particular reason that triggered it.
Some of those include:
1.Investigate excessive server load
The first step that our we follow when they receive the 502 error is to investigate the server load.
As this error generally triggers due to excessive server loads, crashes, or network failures, they cross-check these parameters initially.
You can try to troubleshoot server load to see what can be done.
We often see that the underlying cause for 502 errors can be service failures for web server, mysql server etc.
Also, we largely see 502 errors when the Web server in failed status. A simple restart of the httpd service will make the websites working again.
To avoid recurrence, our Support Experts go way further and fixes the real reason for web server failure.
2. Firewall restrictions
Most Web Hosting servers have built-in firewall to block traffic from bad networks. Additionally, some servers implement Country-based firewall blocks as well.
That is, websites will be served only to users from selected countries.
In such cases, a user accessing the website from a blocked network will see 502 errors.
Here, we modify the server firewall in a way that does not create a security risk for the server.
Nowadays, many website owners rely on third-party content delivery networks for faster loading of images, videos etc. on the websites.
So this firewall modification also needs to accommodate these third-party content delivery networks as well.
3. Reload the webpage
This is one of the first things you should do when you see any error message, including the 502 Bad Gateway error.
If the error message happened because the server is overloaded, waiting a while then reloading the page will usually solve the problem.
4. Clear your browser cache
Sometimes, you'll see an error message because your browser's cached version of the webpage is different from the current version on the website.
Clearing your browser cache will force your browser to retrieve the newest copy of the webpage from the website.
To clear your cache in Google Chrome, click the three-dot icon in the top-right corner of your browser, then select More Tools >> Clear Browsing Data and check only the box for Cached images and files.
5. Check your DNS
A 502 Bad Gateway error can also be caused by a DNS problem, like the domain not mapping to the right IP address. In fact, if you’ve recently migrated your WordPress website to a new host, this is the most likely cause of the problem.
To fix this, you'll need to wait at least 24 hours for complete propagation. If you haven't recently migrated your website, try flushing your local DNS cache by opening a command window and typing the following: ipconfig /flushdns If you use a Mac, you'll enter the following in the terminal, instead: dscacheutil -flushcache