Cloudflare Error 524: A Timeout Occurred

What the error means

According to the Cloudflare documentation, error 524 means a connection to the site's server was established, but the server did not return an HTTP response within 125 seconds, which is the default limit. On the Enterprise plan, the site owner can increase it to 6000 seconds.

Most often the server simply does not finish in time: it is running a heavy database query, building a large report or export, or it lacks resources.

A proxy does not affect this limit. The request reached Cloudflare and the site, and the time ran out on the site's server.

Causes

• A heavy request. A large export, a search without filters, a report for a long period.
• The site's server is overloaded. Many simultaneous requests, including from your program.
• Long background processes on the server. The site runs a task that takes longer than 125 seconds within a single request.
• The site lacks resources. There is not enough memory or CPU to respond in time.

How to fix it

1. Reduce the size of a single request: fetch data in parts, by pages, for shorter periods.
2. Reduce the number of parallel threads to this site so as not to add to its load.
3. If the site has an API with separate export tasks, use it: for long processes, Cloudflare recommends polling the status rather than one long request.
4. Do not increase the timeout in the program beyond what is needed: Cloudflare will stop waiting at its own limit anyway.
5. If the site is yours, look for slow requests in the server logs; the Cloudflare documentation also describes options for long operations.

How to check that it works

Run the same request with a smaller volume. If it passes and the full one gives 524 again, the issue is the processing time on the site's server, not the connection. Check the overall proxy operation in the proxy checker.

Two-minute diagnosis

First paste the line into the proxy checker. If the proxy works there, the cause is in your app or its settings. If not, test the line from a terminal:

curl -v -x "http://USERNAME:PASSWORD@gw.prokso.com:823" https://api.ipify.org

• A < HTTP/1.1 407 line right after CONNECT means the proxy answered. The name after the code, for example NO_USER, points to the cause.
• The proxy answered CONNECT with 200 and then another code arrived - the proxy works, and that answer came from the website.
• No answer at all, only a timeout - the connection never reached the proxy: check the host, port and network.