DNS propagation takes between 24-48 hours to complete, so use a DNS propagation checker to verify whether the process is complete. If the WordPress site was recently moved to a different domain or server, the change might not have finished propagating globally. Server-side DNS issues generally occur on websites with unresolved IP addresses, while client-side ones are caused by an outdated or corrupted DNS cache, which could result in HTTP error 504. Flush DNSĭNS issues can originate on both the server and client sides. Clearing the browser cache before reloading the page will also increase its load time and reduce the probability of server timeouts. Try loading the WordPress site on another browser and using incognito mode to verify that it’s not a server-side error. If refreshing the page and increasing the maximum execution time limit of PHP scripts didn’t resolve the 504 gateway timeout error, the issue might be browser-related. Hostinger users can check their allocated resources by accessing the Resource Usage menu from hPanel.ĭon’t set the max-execution-time value to 0 as it would allow PHP scripts to run for an infinite period and consume your server resources. Check the Order UsageĮach hosting plan allocates a certain amount of resources for optimal website performance. Doing so will confirm whether the problem is related to your local network. While waiting for the page to refresh, consider checking if the website is down. Alternatively, press Ctrl + F5 to clear the browser cache and force refresh the page.

The easiest way to do it is to click the Refresh button next to your browser’s address bar or press F5. The server might be receiving more requests than usual, so refreshing the page is worth a try. This tip may sound simple, but it’s one of the most common fixes to resolve the 504 gateway timeout error. Most of the solutions apply to any website, but some are WordPress-specific. We’ll go through the basic troubleshooting steps with both options in mind. However, they may also pop up due to issues or an incorrect configuration on the client side. In most cases, 504 errors have server-side causes. These include an incorrect DNS configuration and an outdated or corrupted DNS cache. Without sufficient PHP workers, your website might fail to process multiple requests. These components handle requests whenever a visitor takes action on a WordPress website. A web server running low on resources can get overloaded and thus respond to browser requests slowly, causing the other server to time them out.

If the 504 Gateway Timeout error appears on multiple browsers, devices, or websites, your network equipment might be experiencing temporary connection problems.

This issue could happen when a website has been recently moved to a different IP address or hosting nameserver. This occurs when a domain fails to resolve to a correct IP address. Faulty firewall configuration may also be the issue. The DDoS protection and mitigation systems of some firewalls may block requests from a specific internet service provider or a content delivery network like Cloudflare. Here are several problems that may cause 504 gateway timeout: Domain took too long to respondĭetermining the causes is the first step of fixing the 504 Gateway Timeout error. This HTTP error can appear in different forms and various error messages across browsers, servers, and operating systems. When you encounter the 504 Bad Gateway error, it will usually look something like this: 504 Bad Gateway Timeout Error Variations and Causes Error codeĥ04 Gateway Time-out. We’ve included troubleshooting tips to help you get the site up and running in no time. In other words, the 504 Gateway Timeout Error means that there’s an issue with your network connection or server communication speed as it did not load the web page.ĭebugging the 504 gateway timeout error can be challenging due to the high number of potential causes. In most cases, you can resolve it by refreshing the web page. The 504 “Gateway Timeout” Error indicates that the browser sent an HTTP request to the server and it did not receive a response in time from another server to complete the request.

504 gateway time out aparece en moodle