Sure many times you have encountered the error 504 when you enter a web. All web pages must be hosted on a server with external access, when you enter a domain, the server and the browser must establish communication. If the server can not respond, the page does not load and you see the HTTP status code 504, it starts with 5 as all errors related to the server.
You can display different messages such as:
- 504 Gateway Timeout nginx
- Gateway Timeout Error
- HTTP Error 504
- 504 Gateway Time-out – The server did not respond in time
- HTTP Error 504 – Gateway Timeout
In some cases, the error may come from your CDN although this type of errors is rare, the most common reason is that the server where your website is not working correctly, and that does not require a solution on your part but a complaint to the suppliers.
In the case that it’s a flaw in your website, today we will show you how to fix it.
How to fix 504 Gateway Time-out error
We will see some solutions to this error, from those that do not require you to modify anything on your website, to disable options and check your proxy. Let’s see!
Adjust server settings
You can try increasing the limits of specific resources on the server that you are using, such as the timeout value.
If you have many active plugins at the same time, the response time of your web can be the problem. The solution can be to enter via FTP with a client such as FileZilla and disable the plugins from there by changing the name of the directory. If the problem is caused by the plugins, start activating them individually until you find the one causing the error.
Refresh the page
It sounds obvious, but it can happen that if the server is receiving too many visits it may have difficulties. Wait a few minutes and reload the page. You can use tools like Hosting Review to verify that the website is not down.
Verify your Proxy settings
To do this, access the configuration of your browser and check if there is any active proxy in your local network.
In the LAN configuration button, check the Proxy server section. If it is active, deactivate it and save the changes.
Try another browser
Clear the browser’s cache, switch to the incognito mode with the browser changing anyway.
Check the DNS
Several cases may be occurring:
The status of your DNS is negative since it is not “propagating” correctly and you should wait a bit. You can use a tool like DNS map to verify it.
Your DNS cache may be incorrect or outdated. Update it and verify.
Change to the Googe Public DNS server and you can rule out that this is the problem.
Check the CDN
Sometimes CDNs may be down, temporarily disable them to rule out that this is the reason for the error. If you deactivate your website, keep it off for a few hours and then activate it again to verify that the error has been corrected.
Try another device
Try to enter from a mobile device or from the computer if you are from one, so you can know if the problem is local or can be the server.
Check the error log
If you have made changes or updates to the website, you may have caused an error during the process. Review the error log by adding these lines to the wp-config.php file:
define ('WP_DEBUG', true);
define ('WP_DEBUG_LOG', true);
define ('WP_DEBUG_DISPLAY', false);
Then, in the wp-contents / debug.log file, you will see the error entries.
Contact Customer Service
If you have already tried everything, we can confirm that it is a server failure by contacting the customer service of the server that manages your website. If they do not fail, they could give you guidance on how to fix it.