WordPress

HTTP 504 Gateway Timeout and HTTP 502 Bad Gateway errors are the most common server errors for WordPress website visitors and owners. In my previous article, we’ve already discussed the causes of a 504 Gateway Timeout error and possible solutions for it. In this article, we’ll come to understand what a 502 Bad Gateway error is, talk about the reasons for a 502 Bad Gateway error, and explore some tips for troubleshooting this type of errors. What does 502 Bad Gateway mean? Before we define what a 502 Bad Gateway error is, let’s deep-dive into server infrastructure and find out the meaning of some terms, like web server, proxy server or gateway, and upstream server. Let’s first discuss how hosting a modern web application works. For this we need three actors: The web application The gateway The web server In the picture below you can see the PHP modern web…

An HTTP 504 Gateway Timeout error is the most common error encountered by website developers. And in many cases, it can become a real pain. Generally, it’s difficult to find out the reason for a timeout error because the server response has no helpful information about the error cause. In this article, we’ll find ways to troubleshoot timeout errors and find solutions for them, while giving you a better understanding of timeout errors and their causes. What is a 504 Timeout error? To deeply understand what a 504 Gateway Timeout error is let’s first have a look at server and client relationships. What happens when the client sends an HTTP request to the server? When the server receives the request, it processes it, and–depending on whether the result is successful or unsuccessful–returns a response with the corresponding HTTP status code in the HTTP response headers. HTTP status codes are a…