Gateway Time Out Please Try Again Later
The 504 Gateway Timeout error is one of the most common HTTP 5xx errors faced by website owners and site visitors. For many WordPress blogs and ecommerce platforms, knowing how to fix server errors like this is crucial to keep their difficult-earned visitors from bouncing to competitor sites.
Every bit the 504 Gateway Timeout error doesn't tell you why it occurred, information technology's hard to pinpoint what's causing the server timeout. This article will help you empathise it in detail, learn how to diagnose its cause, and then fix information technology.
Later on trying all the diverse solutions mentioned in the post, your site should exist up and running in no time.
Sounds interesting? Let's dive in!
Prefer to sentry the video version?
What Is the 504 Gateway Timeout Error?
Every time you visit a website in your browser, the browser sends a request to the web server where the site is hosted. The server processes the asking and responds with the requested resources.
The server response includes one of many HTTP status codes to indicate the response'southward status to the browser. Only not all these HTTP status codes are errors. For instance, a 200 OK status code ways that the server candy the asking successfully and "Everything is OK."
The 5xx grade of HTTP status codes indicates that something's wrong with the server, the server is aware of information technology, and it cannot carry out the customer request. Every bit a result, they're also referred to as Server Fault 5xx condition codes.
Officially, 5 status codes are specified under the 5xx grade (500, 501, 502, 503, 504). Yous may come upon many unofficial codes too (506, 507, 509, 520, etc.).
The Internet Engineering Task Force (IETF) defines the 504 Gateway Timeout error as:
The 504 (Gateway Timeout) condition code indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in guild to complete the request.
To simplify information technology further, this mistake occurs when two servers are involved in processing a request. The first server (typically the principal server) times out, waiting for a response from the second server (upstream server).
The 504 Gateway Timeout mistake manifests itself in diverse forms. Hither are some ways it usually shows up:
The 504 Gateway Timeout fault is similar to the 502 Bad Gateway error, which indicates that the first server received an invalid response from the second server (upstream server).
Variations of the 504 Gateway Timeout Error
The browser displays any 504 Gateway Timeout error inside it, merely like any other error. Every bit there are various operating systems, spider web servers, browsers, and user agents, it tin prove up in multiple means.
Below are a few common 504 error message variations that you may run into:
- 504 Gateway Timeout
- 504 Gateway Timeout NGINX
- NGINX 504 Gateway Timeout
- Gateway Timeout Mistake
- Error 504
- HTTP Mistake 504
- HTTP Error 504 — Gateway Timeout
- HTTP 504
- 504 Mistake
- Gateway Timeout (504)
- This page isn't working — Domain took likewise long to respond
- 504 Gateway Time-out — The server didn't respond in time
- The page request was canceled considering it took too long to consummate
- Site visitors: There was an upshot serving your request, please try again in a few minutes.
- Site Owners: There was a gateway timeout. You should visit your error log for more information.
- A blank white screen
All the above error responses, though worded differently, indicate to the same 504 Gateway Timeout server error.
Web servers and websites can customize how they show the 504 Gateway Timeout error to users. Some of them can be absurd! It's an fantabulous tactic to quell their visitors' disappointment.
SEO Impact of the 504 Gateway Timeout Error
All 5xx errors prevent a webpage from loading, making them detrimental to user experience. Hence, search engines similar Google take these errors seriously. If the error persists for a long duration, it may even lead to deindexing the webpage from the search engine results.
For instance, when Google spiders stumble upon a 503 Service Unavailable error, they'll sympathise that it'south a temporary outcome as it's mostly used to enable site maintenance mode. Thus, they'll try to clamber the folio over again later.
A 504 Gateway Timeout error isn't necessarily temporary as it tin can be due to multiple reasons. If your site is down for just a few minutes, and if the spiders are trying to crawl information technology multiple times every minute, they'll endeavor to serve the page from their cache. They wouldn't even notice it.
Just if your site is down for 6+ hours or more, and so Google will consider the 504 mistake every bit a serious site-wide effect that you need to prepare every bit soon as possible. This can impact your SEO negatively.
Google Search Console is i of the all-time SEO tools to monitor your website's HTTP 5xx errors.
Causes of the 504 Gateway Timeout Error
Every bit the 504 error is due to a timeout between servers, the problem probably isn't with the customer's device or cyberspace connectedness. That also includes your device and connectedness.
A 504 Gateway Timeout error indicates that the web server is waiting too long to respond from another server and "timing out." There can be many reasons for this timeout: the other server is non functioning properly, overloaded, or downwards.
The other server need non ever exist external (e.thousand. CDN, API gateway). Information technology can besides be a server-like entity inside the main web server (e.g. reverse proxy server, database server).
How to Fix the 504 Gateway Timeout Mistake
Without knowing exact details about the WordPress site, such as its server configuration, hosting program, 3rd-party plugins, and the traffic it attracts, y'all may find it frustrating and overwhelming to gear up a 504 Gateway Timeout mistake.
Since many variables are involved, I recommend you to commencement past fixing client-side issues, which are pretty rare, and then movement towards fixing server-side issues. They're usually the culprits with 504 errors.
Endeavor Reloading the Webpage
One of the get-go things yous tin can endeavour when encountering a 504 Gateway Timeout fault is to wait a few minutes and try reloading the page.
You can printing the F5 keyboard shortcut to refresh/reload the webpage in most browsers. To remove the page'south browser cache before reloading, you can press the CTRL+F5 shortcut combo instead.
While you're at it, you can also try loading the site in a unlike browser to dominion that out as an issue. Every bit most 504 errors are due to temporarily overloaded servers, using this solution should brand your site come up correct back.
If waiting and reloading the site doesn't fix the 504 mistake issue, you tin check whether a site is down for anybody or just y'all. Two useful online tools to exam a site for downtime are Down for Everyone or Just Me and Is It Down Right Now?
Reboot Your Network Devices
Sometimes, problems with your network devices like modem or router could lead to a 504 Gateway Timeout fault. Rebooting these devices could help you with fixing the problem.
While you tin can switch off all these networking devices in any gild, the lodge you switch them dorsum on is important. Typically, plow these devices on from the "outside-in," following the connection order from the net service provider to your main client device.
Check Your Proxy Settings
A proxy server sits betwixt your device and the internet. It's by and large used to enhance online privacy by hiding individual data (east.g. device location) from websites and webservers (east.grand. using a VPN).
While it'south rare for proxy servers to cause a 504 error, wrong proxy server settings can sometimes be the reason. Yous tin can disable the proxy server and endeavor reloading the webpage to run across whether it'll fix the error.
Most clients don't use a proxy service, and so yous tin skip this step if y'all're confident that y'all don't use any proxy server. Yet, you might have set it without you even knowing about information technology. I'd propose you check your device's and browser's proxy settings to rule this cause out.
DNS Issues
A 504 Gateway Timeout error can also be caused by DNS issues on the server-side or the client-side (or both).
The most probable reason for a server-side DNS issue is the FQDN (fully qualified domain proper noun) not resolving the correct IP accost or the DNS server not responding. Usually, this occurs when y'all've simply migrated your WordPress site to a new server or host. Hence, it'southward important to wait for the domain's DNS records to propagate fully, which can take up to 24 hours.
Y'all can apply free tools like whatsmydns.internet DNS Checker or DNSMap to see if your DNS has propagated around the earth.
For fixing client-side DNS bug, you could try flushing your local DNS enshroud. It'south like clearing your browser enshroud, except here, yous're flushing the DNS enshroud from the operating system.
If y'all're using Windows, you can affluent the DNS cache by opening the Command Prompt and entering the post-obit directive:
ipconfig /flushdns 
Yous should see a "Successfully flushed the DNS resolver Cache." message if it worked.
For the latest macOS versions, you can open the Terminal and run the post-obit control:
sudo killall -HUP mDNSResponder You won't meet whatsoever notification in macOS when the procedure finishes, but you can change that by appending the command with your custom message.
sudo killall -HUP mDNSResponder; DNS Cache was cleared successfully If yous're using older macOS versions, the command you demand to enter varies based on which version of macOS you're running. For more details, you can refer to the macOS section in Kinsta's in-depth flush DNS tutorial.
If y'all're using the Linux operating system, then the process is quite similar to macOS as even Linux uses the Last as its command-line interface. Since at that place are many Linux distributions, the verbal control you demand to run may vary from i distro to another. You can cheque out Kinsta's guide for more than information.
Finally, you can change your client-side DNS servers temporarily. Past default, your Internet service provider assigns the DNS servers automatically to yous. But you can change these to public DNS IPs temporarily.
Some reliable DNS servers you can try out are Google Public DNS, Cloudflare i.1.ane.1, Quad9 DNS, and Cisco OpenDNS.
Disable Your Site's CDN Temporarily
Sometimes, the issue could also be with your content delivery network (CDN). If a site'southward origin server isn't reachable, almost CDNs will attempt to serve the full webpage from their cache.
But most CDNs don't enable this feature by default as it's complex to enshroud dynamic assets on nigh sites (e.g. the WordPress admin dashboard).
A straightforward style to troubleshoot this is to disable your CDN temporarily. For example, if yous're using the gratuitous CDN Enabler WordPress plugin to link your site assets to the CDN URLs, and then you tin deactivate the plugin and test reloading your site.
The same goes for using any other plugin you may use to connect to your CDN (e.g. WP Rocket, Breeze, W3 Total Cache).
If you can't access your site's admin dashboard, you tin disable the plugin via SFTP by renaming the plugin's folder name.
CDNs like Cloudflare or Sucuri, which provide total proxy services, have extra firewalls between their edge servers and your origin server. Hence, y'all may meet HTTP 5xx errors more than frequently while using them. Most of them enshroud 5xx errors returned past your origin server, then it's piece of cake to troubleshoot them.
Cloudflare's gratuitous plan is prone to throw up a 5xx error. Unfortunately, since it's a full proxy service, in that location's no quick way to disable it. But before you blame Cloudflare for it, know that Cloudflare shows two variations of the 504 Gateway Timeout error.
504 Gateway Timeout at Cloudflare (Variation 1)
Cloudflare will show you lot a custom 504 Gateway Timeout error screen when your site'due south origin server responds with a standard HTTP 504 response.
Here, the issue lies with your web server and not Cloudflare. Y'all can effort fixing it with the other solutions mentioned below or contact your hosting provider'southward back up for technical assist.
504 Gateway Timeout at Cloudflare (Variation 2)
If Cloudflare causes the 504 Gateway Timeout error, the fault screen will mention "cloudflare," which is currently the standard server name for all Cloudflare avails. Usually, the error screen volition announced equally beneath:
Since Cloudflare itself is unresponsive, you'll non run into whatsoever Cloudflare-branded mistake screen here.
Well-nigh likely, Cloudflare is already aware of the issue and is working on a ready already. You lot can confirm this by checking the Cloudflare Organisation Condition webpage. Alternatively, you tin can get in touch on with Cloudflare support for a quicker resolution.
504 Gateway Timeout at Cloudflare Due to Large Uploads
The size of your uploads to your site can also be a reason for the server timeouts. Cloudflare limits upload file size (per HTTP Postal service request) to just 100 MB on both Free and Pro plans.
The issue tin exist on your host's stop or with Cloudflare. Y'all can observe out the exact cause by bypassing Cloudflare with your DNS hosts file and trying your upload again.
If you're using Cloudflare with WordPress, I recommend using their gratuitous plugin and excluding critical URLs from caching (such equally the WordPress admin dashboard). You can refer to Kinsta's detailed post on how to configure Cloudflare settings for WordPress.
Suggested reading: How to Set up Cloudflare APO for WordPress.
Server Issues (Check With Your Host)
Server problems are one of the most mutual reasons for facing a 504 Gateway Timeout error. Since most WordPress sites are hosted on Nginx or Apache webservers, Nginx or Apache is waiting for a response from something and timing out.
Many clients come to Kinsta for exactly this trouble they're facing at other WordPress hosts. The chat goes something like this:
Nosotros're getting effectually 100k visitors per calendar month with more than than 200k views. Currently, we're hosting with ____ and we experience 504 errors constantly due to server overload. I don't similar how ____ handled the trouble, and we were also advised that we will have to move to their dedicated plans before long, which I believe is non necessary.
High-traffic and ecommerce sites are more than prone to getting 504 errors because of server overload as they generate many uncacheable requests. However, this effect can ingather with any site, including simple blogs. Many hosts volition ask you to upgrade to a high-tier program to fix the issue, which in nigh cases is unnecessary.
Subscribe At present
Kinsta uses LXD managed hosts and orchestrated LXC software containers for each site. Thus, every WordPress site is housed in its own isolated container with access to all the software required to run information technology (Linux, Nginx, PHP, MySQL). The resources are 100% individual and aren't shared with whatsoever other site, even your sites.
About WordPress hosts providing shared hosting plans don't have this adequacy. Hence, a loftier-traffic site hosted on the aforementioned server equally yours may cause your site to throw up a 504 error too.
Autonomously from isolating each site in its container, Kinsta has also designed its infrastructure to handle thousands of concurrent connections easily. Kinsta even hosts the MySQL databases at localhost, not a remote server. This means no latency between machines, resulting in faster queries and fewer chances of timeouts occurring.
Many clients who migrate to Kinsta see huge decreases in overall load times.
An overloaded server isn't the only crusade for a server timeout. There tin be many other reasons for the 504 mistake:
Boring Server Infrastructure
The server you use to host your WordPress site may not accept enough resources to handle the load. Information technology's like playing a modern, graphics-intensive videogame on a decade-old PC.
The server only hangs upwardly trying to serve the website. The only solution to this problem is to upgrade to a server with amend infrastructure. For this reason, fifty-fifty Kinsta'due south virtually basic WordPress hosting programme volition handle a static site with medium traffic.
Needs More PHP Workers
PHP workers are used to execute your WordPress site'due south code. An ecommerce site that gets l,000 visitors per month needs a lot more resources than a simple blog with the same amount of traffic. If all the server'south PHP workers are busy, they'll build up a queue.
When the queue gets too big, the server disregards quondam requests, which may crusade the server to throw up a 504 gateway error. Yous can ask your host about increasing your number of PHP workers. This'll allow your site to execute multiple requests simultaneously.
Firewall Issues
Your server'due south firewall could have some errors or an improper configuration. Possibly, a few of its rules prevent the server from establishing a connexion properly. To know if your firewall is the culprit, you lot can cheque your server'due south error logs.
Network Connectivity Problems
Connectivity issues between the proxy server and the web server could cause delays in responding to HTTP requests. If yous apply a load balancer, there could as well exist network connectivity bug with it.
HTTP Timeouts
HTTP timeouts can occur when a connection between the web server and the client is kept open for likewise long. With WordPress sites, this usually happens when running WordPress imports. One style to resolve this issue is to switch to a faster internet connexion.
You tin can too use a tool with support for WP-CLI to run the scripts directly on the server, bypassing the HTTP connection entirely. For instance, you can employ the wp import WP-CLI control to run the WordPress Importer plugin direct through the control-line interface.
Important: 504 Gateway Timeout errors wait like to 503 Service Unavailable errors or 502 Bad Gateway errors. Only they're all dissimilar. If you're experiencing a 504 error at Kinsta, open a support ticket to become your issue stock-still immediately.
For monitoring your site's downtime on your own, you can use a tool like updown.io. It'll check your website's condition (or any URL) periodically by sending an HTTP request to it. You tin can gear up the check frequency from 15 seconds to 1 hour. If your website isn't responding correctly, it'll notify you with an e-mail or an SMS.
You'll get a generous quantity of gratuitous credits with every business relationship of updown.io, but if you're looking for cheaper alternatives, you tin can check out WebGazer or UptimeRobot. Both these tools will help you monitor your site's uptime every 5 minutes for free. That'south decent enough for most website owners.
Monitoring your website will give you an idea of how often it'southward downwards. This is especially helpful if you're using a shared hosting provider. Most managed WordPress hosts accept care of this automatically for you lot. Hence information technology'southward always recommended to get with them.
For a detailed explanation, check out Kinsta's post on the importance of managed WordPress hosting.
Spam, Bots, or DDoS Attacks
Malicious attackers tin bring your web server to a crawl by sending too many and/or resource-intensive requests. If your site is getting spammed past bots or undergoing a DDoS attack, it can overwhelm your server and result in 504 Gateway Timeout errors for many genuine users.
You can look at your server traffic and analytics to see if yous can spot any irregular patterns in the site traffic. If yous're using Kinsta to host your site, you tin view this data hands by going to your MyKinsta Analytics dashboard.
Starting time your investigation past looking at the top customer IPs. It'll give you an idea of who generates the maximum number of requests, and from where. If your server suddenly uses up enormous bandwidth or attracts a lot of traffic, then this study volition come in super handy.
Next, you can check out the Cache Analysis report. Hither, you tin can run across how many requests are bypassing or missing the cache, or being served from the cache. For performance and stability reasons, you want to enshroud as many requests as possible, only information technology's not ever possible to achieve that.
For example, WooCommerce sites generate many uncacheable requests for features such as the shopping cart and the checkout process.
Finally, you can use a WordPress security plugin to beefiness upwardly your website's security by spotting and blocking worrisome traffic/IPs. You lot can inquire your host to block certain IPs too.
Depending upon the length and scale of the attack, this could be a never-ending process of blacklisting IPs as many attackers change their IPs and proxy addresses after getting blocked.
Annotation: Kinsta doesn't let its clients to install WordPress security plugins as they tin can have a huge effect on the site'due south performance, especially its scanning capabilities. Every bit Kinsta uses load balancers with Google Cloud Platform, blocking IPs wouldn't always work every bit intended.
You can use dedicated security solutions such as Cloudflare or Sucuri to protect your sites from DDoS attacks and spambots. For more, you can check out Kinsta'southward articles on how to install Cloudflare on your WordPress site and how Sucuri helped stop a DDoS attack in its tracks.
Corrupted WordPress Database
Sometimes, a 504 Gateway Timeout fault can be considering of a decadent database, especially in WordPress sites. Typically, this is due to corrupted database tables or files. Sometimes, it can also exist caused by a serious security issue like your site or database being hacked.
Repairing a corrupted WordPress database depends on the problem. Plugins like WP-DBManager make it piece of cake to diagnose database problems and repair them. I recommend you to read Kinsta's detailed walkthrough on repairing WordPress database bug to become started.
Bank check Your Site's Plugins and Themes
In well-nigh cases, third-party plugins and themes don't cause 504 errors. Simply there's a slight chance that they might cause server timeouts, usually by queuing up many uncached requests generated by the plugin/theme. Every bit this ties upwardly a lot of your server'southward PHP workers, it can crusade 504 errors.
A great example of this issue is WooCommerce, a plugin installed to add together ecommerce functionality to WordPress sites.
The simplest way you can troubleshoot this problem is past deactivating all your plugins. Remember, you lot won't lose any data if you just deactivate a plugin.
If y'all can access your admin dashboard, yous can become to the Plugins screen, select Deactivate from the bulk actions menu, checkmark all the plugins, and then hit the Apply button. This volition disable all of your plugins.
If yous can't access your admin surface area, you can disable plugins via SFTP using the method described before. Only rename the main plugin folder name to disable all the plugins in bulk.
Once you lot've deactivated all the plugins, check whether your site loads properly. If it works, you must activate each plugin, testing the site afterwards enabling every plugin.
Finally, make sure that your plugins, themes, and WordPress core are up to date. As well, ensure that your server is running the recommended version of PHP.
If you experience this to be too overwhelming, you tin always reach out to your host for help. Kinsta uses New Relic and other troubleshooting techniques to aid clients narrow downwards what plugin, query, or script might cause the error.
In the worst-example scenarios, like an inefficient query or bad lawmaking in a plugin/theme, you tin bring in a WordPress developer to fix the issue.
Check Error Logs
Viewing error logs tin can be very helpful when troubleshooting and debugging 504 errors on your WordPress site. This can assist yous narrow down an issue on your site chop-chop, especially if it's resulting from a demanding plugin on your site.
If you're a Kinsta customer, you tin hands see errors in the log viewer in your MyKinsta dashboard.
If your host doesn't have a logging tool, then you tin enable WordPress debug manner by adding the following code to your wp-config.php file:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', truthful ); define( 'WP_DEBUG_DISPLAY', false ); The WP_DEBUG constant enables or disables the WordPress debug mode. It has ii optional companion constants that can extend its features. The WP_DEBUG_LOG constant directs all errors to be saved to a debug.log file inside the /wp-content/ directory. If yous don't see this file, you tin always create one.
The WP_DEBUG_DISPLAY constant controls whether debug logs show upward on the HTML page. Setting this to faux volition hibernate all errors, merely you can review the errors later, every bit yous've besides divers WP_DEBUG_LOG equally true.
Important: If you have WP_DEBUG enabled in the Kinsta surround, information technology'll route all errors to the debug.log file and not the mistake.log in the MyKinsta dashboard.
You tin as well download the raw WordPress error log files via SFTP. Typically, yous can find error logs in your server's root directory in a folder named "logs."
Kinsta users tin besides enable WordPress debug mode from their MyKinsta dashboard. To do that, navigate to Sites > Tools > WordPress Debugging and click the Enable button. This will allow y'all to see PHP errors and notices without enabling debug mode via SSH or SFTP.
Lastly, you can bank check the server log files. Depending on which server you're using to host your WordPress site, they're normally found in these locations:
- Apache:
/var/log/apache2/error.log/ - Nginx:
/var/log/nginx/error.log/
You can refer to logging related documentation of Apache or Nginx for more information.
Configure Apache or Nginx Settings Properly
Y'all tin can edit your server config files to increase resource limits for specific directives. This can help you resolve the 504 Gateway Timeout error.
For Apache Webservers
Showtime, add together the post-obit code to your httpd.conf:
TimeOut 600 This setting defines how long the server will wait for certain requests before marking it as a network timeout issue. Its default value is 60 seconds (Apache 2.iv version).
You can only add this directive in your httpd.conf file, non in your .htaccess file. Since most shared hosting providers don't allow you to modify the httpd.conf file, you can endeavour increasing the value of the LimitRequestBody directive in your .htaccess file instead.
And then add the following line to your php.ini file:
max_execution_time 300 The default value of PHP's max_execution_time directive is 30 seconds. Increasing it will permit your site's PHP scripts to run longer.
For Nginx Webservers
If yous're running your WordPress sites on Nginx + FastCGI Process Manager (PHP-FPM) or using Nginx every bit a opposite proxy for Apache, you can tweak the server settings to assistance forbid 504 Gateway Timeout errors.
504 Gateway Timeout Error on Nginx + FastCGI (PHP-FPM)
Outset, you must edit your PHP-FPM puddle config file. You can find it at the /etc/php7.4/fpm/pool.d/world wide web.conf location in your Nginx server (the exact path may vary based on the PHP version). Alternately, you can run the post-obit command in your final to edit the PHP-FPM pool config file:
sudo nano /etc/php/7.2/fpm/pool.d/www.conf Next, set the following directive:
request_terminate_timeout = 300 Subsequently this, yous must edit your php.ini file. You can locate it at /etc/php.ini. Open up the file and add together/change the value for the max_execution_time directive to 300 seconds.
max_execution_time = 300 Finally, add together the following code to your nginx.conf file's location block:
location ~ .php$ { ... fastcgi_read_timeout 300; } Reload Nginx and PHP-FPM for the changes to accept effect.
sudo service nginx reload sudo service php7.4-fpm reload The exact code to reload PHP-FPM volition vary based on the PHP version installed on your server. Test your site to meet whether it has fixed the issue.
504 Gateway Timeout Error on Nginx Proxy
If you're using Nginx as a reverse proxy server for Apache, then you can go far more than lenient towards server timeouts past adding the post-obit directives to your nginx.conf file:
proxy_connect_timeout 600; proxy_send_timeout 600; proxy_read_timeout 600; send_timeout 600; Don't forget to reload Nginx after making your changes.
sudo service nginx reload
Other HTTP Errors Like 504 Gateway Timeout
As mentioned earlier in the article, many other HTTP 5xx errors are just like the 504 Gateway Timeout error. Information technology's considering they all happen on the server-side. These errors include:
- 500 Internal Server Error
- 501 Non Implemented Mistake
- 502 Bad Gateway Error
- 503 Service Unavailable Error
Other HTTP errors acquired due to client-side issues, like the 404 Not Constitute fault, are also like the 504 mistake. Y'all tin refer to Kinsta'southward detailed guide and list of HTTP status codes for more information.
Summary
Your WordPress site can exist affected by the 504 Gateway Timeout error because of multiple reasons. In this article, you learned how to troubleshoot them all. Typically, these errors are acquired due to server-side issues, in which case you can reach out to your host and get it resolved quickly.
However, you must too sympathize that this error can be due to third-party plugins, themes, services, inefficient database queries, or a combination of two or more of these. If you're maxing out your server'south resources (e.thou. PHP workers), information technology'southward recommended to optimize your site for performance.
If you all the same find that your website is timing out, then it might very well be that y'all need to upgrade your hosting plan or the number of PHP workers. I recommend you to consider this pick merely after y'all've wearied all the other solutions described in this article.
From simple static sites to complex ecommerce and membership sites, Kinsta's scalable hosting plans are designed to suit all types of websites. To learn more virtually our scalable deject hosting, check out this article!
Did we miss annihilation? If you're still finding it difficult to ready the 504 Gateway Timeout mistake on your WordPress site, leave a comment beneath.
Relieve fourth dimension, costs and maximize site functioning with:
- Instant help from WordPress hosting experts, 24/vii.
- Cloudflare Enterprise integration.
- Global audience reach with 29 information centers worldwide.
- Optimization with our built-in Application Operation Monitoring.
All of that and much more, in ane plan with no long-term contracts, assisted migrations, and a xxx-twenty-four hour period-coin-back-guarantee. Check out our plans or talk to sales to find the program that'south right for you lot.
Gateway Time Out Please Try Again Later
Source: https://kinsta.com/blog/504-gateway-timeout/
0 Response to "Gateway Time Out Please Try Again Later"
Post a Comment