There are all kinds of mysterious mistakes that you can get when visiting websites online. The most famous is probably the 404 error you encounter while trying to visit a non-existent website. The second most popular error is the 504 bad gateway error. There are dozens of others.
Dealing with such errors when trying to load web pages is frustrating for both visitors and brands. Visitors do not get the information they are looking for, while brands reduce their exposure and alienate the audience.
The good news is that the 504 error code is somewhat under your control, and you can maintain your reputation by taking a few precautions and learning how to quickly resolve the 504 gateway timeline when it occurs. But first, let’s list what a 504 bad gateway error actually means and what the reasons are for it.
What is the waiting time for a 504 gateway?
Every time you visit any website, your server tries to communicate with the host server (also known as the upstream server) of that website in order to get all the necessary information to display the content of the website.
When the host server does not respond with the requested information quickly enough, the request will expire and you will not be able to load the website properly. This is a 504 gateway timeout error.
Depending on your browser and operating system, you may see different versions of error 504:
Google Chrome only says HTTP ERROR 504 followed by “This page is not available”.
Windows applications can say HTTP_STATUS_GATEWAY_TIMEOUT or even WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT
Another possible message may be “Proxy server did not receive a timely response from the upstream server.”
Unfortunately, error code 504 itself is not that specific and there can be many reasons for its occurrence, which makes the problem-solving process somewhat complex.
Why does the 504 gateway access time expire?
Before you start correcting a bad gateway error 504, you need to think about all the possible causes for it and try to conclude which one is responsible for the error this time.
Servers cannot connect to each other. The most obvious reason for error 504 is a failure on the host server. For example, interruptions could occur due to overload, attack, or maintenance.
DNS changes. Moving your server to a different IP address would also change your DNS. Because it takes some time to expand DNS, your website may be unavailable during that time. This situation should be resolved within a day.
Strict firewall. Given that there is so much malware on the internet, leaving your website open for any bot or malicious script is not a good idea. Setting up a firewall can prevent illegitimate traffic and DDoS attacks, but it can sometimes repel real visitors as well, showing them a 504 bad gatekeeper error.
Site errors. If you’ve recently made changes and updated the code on your website, it’s possible that you’ve introduced some incompatibilities that your server can’t handle.
Network problems. Most of the time 504 errors are related to the host server. But if only you see the error page, it could indicate an unresolved issue with your internet connection.
Going through the various reasons listed above one by one can help you discover the true cause of the 504 gateway timeout error. With this information in mind, then you will easily find the right solution.
How to fix 504 gateway timeout errors
If you look carefully at all the possible reasons for error code 504, the solution is likely to be discovered. Here are some of the most popular fixes.
Troubleshoot server connection issues. Your server may crash without you even being aware of it, resulting in 504 errors for all your visitors. This can be a quick server maintenance by your hosting company, or it can be a more serious and time consuming error with the server itself. To see that, you need Simon.
Simon is a smart application that automatically monitors the status of all your servers and websites in one place. This app has a complete set of tools that seamlessly helps you control and troubleshoot your internet properties. You can set up monitoring systems, design various tests, detect all changes, find errors and track recovery. Notifications are also instantaneous, which means less downtime in anything you track.
Restart the network devices. Although it has become a rather clichéd repair, restarting network hardware is probably one of the best ways to solve network-related problems. Locally, start with a modem, router and any switches. You can remotely restart the server or rebuild the website.
Reconfigure your DNS. One of the most common reasons for a bad gateway 504 to appear is that your website is in the process of migrating to a new server and thus changing your DNS. DNS changes can take from a few hours to a few days. Once you’ve verified that your DNS settings are correct, it’s best to simply wait for DNS to fully expand online.
Find errors in the server logs. If your server, network device, and DNS are OK, the problem could be more localized. Log on to your server and check the server logs to find any inconsistencies that could be caused by the 504 bad gateway in the server status updates.
Adjust firewall configurations. While using a firewall is a really good idea, it can sometimes give you headaches by blocking legitimate traffic, which would result in error code 504.
Locally on your Mac, make sure your firewall is turned off in System Preferences ➙ Security & Privacy ➙ Firewall. Then go to the firewall settings on your server and try to deactivate them to check if the 504 gateway retention lasts. If it disappears, try restoring the firewall settings one by one to find the faulty one.
Make sure the proxy settings are correct. Most Macs don’t actually use custom proxy settings, so that may not apply to everyone. But if you do, double-checking can solve problem 504, especially if you fix them with Proxyman.
Proxyman is the best Mac debugging application for proxy settings. You can categorize the various applications that communicate with the Internet, as well as all the domain names you own, view HTTP / HTTPS requests, and view potential errors on a Mac, iOS simulator, or remote devices. Really debugging the proxy effortlessly.
Check the code of your website. You rarely see a code base where there are no errors. And while most errors are insignificant, some can interfere with the way your server handles different requests. First look at your git submissions to see if there are any code plugins that have to do with the server. If your web environment is quite difficult to decipher, try VirtualHostX Pro.
VirtualHostX Pro is a comprehensive tool for building and testing websites locally on your Mac. It’s a great all-in-one solution for developers to have complete control over their website before launching it into the world. You can even install a real Linux virtual machine on your Mac to simulate a real server environment.
Contact your hosting company. If you are not well versed in server configuration, try talking to your hosting provider and see what support they can offer.
As you can see, once you know how long the 504 gateway is, it’s all in the methodical attempt of various debugging solutions. What could definitely help you is proactively monitoring your website for any bugs with Simon, checking proxy settings with Proxyman, and testing your versions before applying them with VirtualHostX Pro.
Best of all, Simon, Proxyman and VirtualHostX Pro are available to you completely free for seven days through a trial version of Setapp, a platform with over 220 outstanding Mac applications for any task. Try every Setapp app today at no cost and quickly gather a collection of new favorites!
Friendly communicator. Music maven. Explorer. Pop culture trailblazer. Social media practitioner.