Living in the world of blogs and websites is full of twists and turns. Especially for beginners, the digital world is sometimes full of challenges, but it also offers many solutions so that you can be helped easily. Well, one of the obstacles or obstacles that are most feared by website activists is when you are faced with a 502 bad gateway.
What is a 502 bad gateway? At first glance, it is a condition in which web managers and web viewers are faced with a blank condition so that the website can no longer be operated. Likewise, people who want to access the web or blog will be constrained because the condition of the blog only says 502 bad gateway.
If you experience a 502 bad gateway, don’t panic and despair. This condition is annoying and certainly makes you sad. Especially if the web that you manage is very influential for the existence of your business. Surely the condition of the 502 bad gateway will be very detrimental.
Don’t panic immediately, because all problems must have a solution. If you are faced with a 502 bad gateway problem, there are a few steps you can take to solve it. But before we step on to discussing how to fix error 502 bad gateways, it’s good that we first know the cause.
Like a doctor who prescribes, we are required to detect the disease first, right? Therefore, let’s look at the causes of 502 bad gateways in the following description.
Causes of the 502 Bad Gateway are Various
One thing you should know, 502 bad gateways can be experienced by all websites, including those owned by large and well-established companies like Google and Twitter. The causes are many, so we must be skilled in looking for them. If your website has an error it doesn’t always say “502 bad gateway”.
The error notification can also be displayed in other words, for example “HTTP Error 502 Bad Gateway”, “502 Service Temporarily Overloaded”, “Error 502”, “502 Bad Gateway NGINX” and a number of other writings, adjusting to the cause.
Most Popular Server Setup Detection
The next step, detect the most popular server setups. For example, if you use a WordPress site, it will involve a database server, an application server and a Reversed proxy server. The so-called third (reversed proxy server) is also known as the gateway. He plays a role in running software, including Nginx software (pronounced Engine-X), Apache, and Varnish.
When you access the website through a browser, there is automatically a request to prepare the data needed so that the page appears complete with its features. The request is sent to all servers. Well, when the server receives an invalid response from the upstream server, that’s the cause of the 502 bad gateway.
The 502 bad gateway message briefly represents the voice of the reverse proxy server wanting to reveal that it tried but failed to receive the requested content. The disclosure in the form of 502 bad gateway is also a defense, because it has been blamed by the upstream server.
In short, the cause of 502 bad gateways is that there has been a communication miss between servers. Communication errors are of course beyond your control. Other causes of the 502 bad gateway include damage to one or all of the upstream servers, the server is overloaded, there are bugs in the PHP script, problematic browser cache, and network problems. Another cause is a problem with the Content Delivery Network (CDN) or a problem with the domain name system.
How to Fix 502 Bad Gateway
After knowing the cause, let’s move on to the next process, which is overcoming 502 bad gateways. Of course this will restore your web condition to normal. Come on, follow the steps below with a calm heart and cool head. Hopefully, with the methods that will be presented, the 502 bad gateway problem will be resolved soon.
1. Reload the Web Page
You need to know, the 502 bad gateway error is not permanent, but temporary. It also doesn’t break the system as a whole. Reloading the web will return your web situation back to normal, because it could be the cause of 502 bad gateways because the original server has been overloaded, aka overloaded, so it must be refreshed.
While waiting for your website to return to normal, you can do the following steps. Copy and paste your site URL into the isup.me tool. There you can check whether the 502 bad gateway error only occurs for you as the manager, or if the error also annoys people who visit your site. If the error message only occurs for administrators, while web visitors everywhere do not feel it, then try accessing your website through another browser.
2. Clear Browser Cache
If the first method doesn’t work, then clearing the browser cache can be an effective next step. Cache is a file that is stored on the server because you open the web for the umpteenth time. So the cache automatically makes it easier for you to receive a complete web view without the need to make the server work repeatedly.
Although useful, cache can also make your website overloaded or overloaded. Therefore, deleting the cache will help the web to lighten the files, and the 502 bad gateway problem is likely to be resolved quickly.
3. Resetting (Restart) Internet Network
If the first and second steps fail to solve the cause of the 502 bad gateway, don’t immediately give up hope. You can take the next step, which is to reset your internet network. Because it could be, the error that creates a 502 bad gateway is due to an error on the network device.
For example, you use a router as an internet network device.
Out of control, your gateway router is experiencing problems or errors. If the cause of the 502 bad gateway is because of this, restarting is quite simple. You just need to unplug the internet network power cable, then wait for about a minute. While waiting, you can also restart your computer. After that, re-plug or plug in your router cable, and try to access your web again.
4. Turn off the CDN for a while
CDN stands for Content Delivery Network. It is a service that serves to improve site performance. One of the best CDN products is CloudFlare. However, the free CDN version sometimes causes 502 bad gateways.
Well, if you experience 502 bad gateways, chances are CDN is the culprit. So if steps one through three don’t work, try turning off the CDN for a while. After that, try to check your website again whether the error has stopped or still continues.
5. Waiting for Web Provider Switching Process
IP Address error is also a cause of 502 bad gateways. If your domain doesn’t display a valid IP address, then an error message encountered with 502 bad gateway will appear. This may also happen because you just moved from your old hosting to a new hosting provider.
While the migration takes from 12 to 36 hours, when you want to access the web in that time, you will receive a 502 bad gateway message. The only way if this happens, be patient to wait until the process of moving providers is complete, and do not stop domain propagation until the process is successful.