Cloudflare 524 increase timeout will help corporate clients to extend timeout up to 6000 seconds rather than the default 100 seconds. At Bobcares, as part of our Server Management service, we respond to all Cloudflare inquiries.
What Is “Error 524: a timeout occurred”?
Error 524 signifies that Cloudflare connected to the origin web server successfully, but that the original failed to send an HTTP response before the connection’s default timeout of 100 seconds. This may occur if the origin server is simply taking too long due to a backlog of work, such as a large data query, or a PHP application or if the server is running low on resources and is unable to deliver any data on time.
Firstly, it’s a good idea to check our server’s available resources, including CPU and RAM, and overall traffic levels. If our server is overloaded, it may also result in this error. A web server will not be the reason always. A resource issue may be present if our server has a high CPU load or little memory. So reviewing our web server access/error logs would be a good choice.
This is something that our knowledgeable Server Support team can help with any time. We are here to help you.
How To Fix The ‘Error 524: a timeout occurred’ Error?
- To prevent running into this error, implement status polling for large HTTP processes.
- Move HTTP requests that frequently take more than 100 seconds to complete (for instance, large data exports) behind a subdomain that is not proxied in the Cloudflare DNS app.
- Make sure the lan.timeout is set higher than the default of 30 seconds and restart the railgun service if error 524 occurs for a domain using Cloudflare Railgun.
- Contact the hosting provider to exclude any long-running process or an overloaded origin web server.
- To exclude any ongoing processes or an overburdened origin web server, get in touch with the hosting company.
- Corporate customers can increase the 524 timeout up to 6000 seconds using the proxy_read_timeout API endpoint.
How To Increase The 524 Timeout For Enterprises?
This is an option only available in the Enterprise edition of Cloudflare. In order for Cloudflare 524 increase timeout
Get Proxy Read Timeout setting: Maximum time between two read operations from origin.
Change Proxy Read Timeout setting: Maximum time between two read operations from origin
PATCH zones/:zone_identifier/settings/proxy_read_timeout
Required Parameter:
Name/type: value /number
Description/example: Value of the zone setting /100
Constraints: default value: 100; Value between 1 and 6000
[Looking for an answer to another query? We are available 24/7.]
Conclusion
To summarize, ‘Error 524: a timeout occurred’ is unique to Cloudflare and denotes that the server connection terminates as a result of a timeout. In this article, our Support team describes the resolving methods for the error.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
var google_conversion_label = "owonCMyG5nEQ0aD71QM";
Hello,
could you please explain more , where in the cloudflare settings this changes must be done ?
Hello,
Please contact our support team via live chat(click on the icon at right-bottom).