What is a 504 Gateway Timeout error? How to fix a 504 error

A 504 Gateway Timeout error can be a major roadblock for any website owner or developer. This error occurs when a server takes too long to respond, leaving your website inaccessible to visitors. Understanding why this happens and how to resolve it is essential to maintaining smooth online operations. In this article, we’ll break down the causes, show practical solutions, and share tips to prevent future downtime.

What is a 504 Gateway Timeout error?Link to heading

The 504 gateway timeout is an HTTP status code that occurs when a server does not receive a timely response from another server it relies on while trying to load a web page or process a browser request.

In simple terms, this error happens when one server, which you don’t control, fails to respond quickly enough to the server handling your request. Essentially, two servers are involved: the first server (usually your main server) waits for a reply from the second server (upstream server) but hits a timeout before receiving it.

Common messages users may see when encountering this issue include:

• 504 Gateway Timeout
• Gateway Timeout Error
• 504 Gateway Timeout NGINX
• NGINX 504 Gateway Timeout
• Error 504
• Gateway Timeout (504)
• HTTP 504
• HTTP Error 504
• 504 Error
• This page isn’t working - Domain took too long to respond
• 504 Gateway Time-out - The server didn’t respond in time

>>> Learn more: What is a 503 Service Unavailable error? Causes & solutions

What causes a 504 Gateway Timeout?Link to heading

A 504 gateway timeout occurs when there’s a delay in communication between servers, meaning the problem isn’t usually caused by your device or internet connection. This includes both your equipment and network. This error signals that your web server didn’t receive a timely response from another server it was trying to contact while loading a page. In simple terms, the servers aren’t communicating quickly enough.

A 504 gateway timeout typically happens when a middle server fails to connect with the main server. If too much time passes before a request completes, the timeout limit is reached, and the connection stops. Common causes include an overloaded server, server downtime, maintenance, or temporary unavailability.

How to fix 504 Gateway TimeoutLink to heading

Clear your DNS cacheLink to heading

A 504 gateway timeout error can be triggered by DNS issues on either the server or your device. On the server side, it often happens when the domain name (FQDN) doesn’t resolve correctly to an IP address, or the DNS server doesn’t respond, common after moving a WordPress site to a new host. Server DNS updates can take up to 24 hours to propagate fully.

On your device, clearing the local DNS cache can help. This is similar to clearing your browser cache but removes stored DNS records from your operating system, potentially resolving the timeout.

Refresh the page (F5)Link to heading

When a 504 gateway timeout appears, the simplest first step is to reload the page. Sometimes, the server is temporarily overwhelmed, and a brief wait followed by a refresh can restore access. This basic action often resolves the issue without additional troubleshooting.

Restart your internet devicesLink to heading

If refreshing doesn’t work, the issue may be with your network equipment. Restart your computer, modem, router, and any connected devices. Powering devices back on in the correct order, starting from the ISP connection to your main device, can restore proper network communication and may fix the timeout.

Check browser proxy settingsLink to heading

A proxy server sits between your device and the internet, often used for privacy or VPN purposes. Incorrect proxy settings can sometimes cause a 504 gateway timeout. Try disabling any proxy or VPN temporarily and reload the page to see if the error clears.

Disable plugins or themesLink to heading

For WordPress users, third-party plugins or themes can trigger a 504 gateway timeout. Disable plugins one at a time via your dashboard to identify the culprit. The same applies to themes, switching to a default theme temporarily can determine whether custom code is causing server delays.

Contact the Website AdministratorLink to heading

If the error persists, reach out to the site administrator. The server may be undergoing maintenance or experiencing issues. Admins can check server logs, identify the problem, and provide instructions or fixes to resolve the 504 gateway timeout efficiently.

Contact your internet service providerLink to heading

If all else fails, the problem might be with your network connection. Contact your ISP to report the issue and get assistance. They can investigate connectivity problems, address routing issues, and help restore access if the 504 gateway timeout is caused by your internet connection.

Check the error logLink to heading

A 504 gateway timeout can occur after updating your website or making major changes. One common and simple fix is to enable WordPress debugging. Add these lines to your wp-config.php file:

define('WP_DEBUG', true); 
define('WP_DEBUG_LOG', true); 
define('WP_DEBUG_DISPLAY', false);

This will log errors into wp-content/debug.log, allowing you to identify the cause of the 504 gateway timeout.

Check your pluginsLink to heading

Outdated or incompatible plugins are frequent causes of a 504 gateway timeout. To identify the culprit, temporarily deactivate your plugins:

1. Go to the wp-content folder and rename the plugins directory.
2. Rename the folder back to its original name and test plugins one by one.
3. Deactivate each plugin individually until the error disappears to pinpoint the source.

Adjust server configurationLink to heading

If you are using a VPS, hosting, or dedicated server, modifying server settings can resolve 504 gateway timeout issues.

For Apache servers:

• Edit httpd.conf to increase the default Timeout value.
• Update php.ini to raise max_execution_time.
• Save changes and restart Apache.
• Test your website to see if the 504 gateway timeout persists.

For Nginx servers:

• Open /etc/nginx/conf.d/timeout.conf and increase these values:

proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;

• Adjust max_execution_time in php.ini.
• Save changes, restart Nginx, and check your website again.

>>> Learn more: Is your website showing a 502 Bad Gateway error? See how to fix it now!

ConclusionLink to heading

In summary, a 504 gateway timeout error signals a delay in server communication, but it can be resolved with systematic troubleshooting. By following the steps outlined, you can restore website functionality quickly. 

Read more in-depth articles on website security and management on the W7SFW blog right now.