Cloudflare Error 524: A Timeout Occurred

How to fix it

Try these in order — the most common fix is first.

1. 1. Find and speed up the slow request

   Copy steps
   1. Log response times on the origin
   2. Use Origin Analytics > Top endpoints to see paths near the timeout
   3. Optimise the query or add caching
   Did this fix it? Yes No

2. 2. Make long jobs asynchronous

   Copy steps
   1. Return immediately and poll for the job status instead of one long request
   2. Use a queue or background worker for exports and imports
   Did this fix it? Yes No

3. 3. Serve long requests on a DNS-only subdomain

   Copy steps
   1. In DNS, create a subdomain such as admin.example.com
   2. Set it to DNS only (grey cloud)
   3. Use it for the long-running tool
   Did this fix it? Yes No

4. 4. Enterprise only: raise the timeout

   Copy steps
   1. Use a Cache Rule with Proxy Read Timeout, or the proxy_read_timeout zone setting via API
   2. Values up to 6,000 seconds are allowed; set 1 second higher than needed
   Did this fix it? Yes No

Symptoms

'Error 524: A timeout occurred' appears after a long wait, typically on exports, imports, backups or heavy admin pages.

Why it happens

• Origin takes longer than the 125-second Proxy Read Timeout
• Large database query or overloaded server
• Write to the origin not finishing in 30 seconds (cannot be changed)

This guide also covers

• cloudflare error 524
• a timeout occurred cloudflare
• cloudflare 524 wordpress

Other Cloudflare errors

• Cloudflare Error 521: Web Server Is Down
• Cloudflare Error 522: Connection Timed Out
• Cloudflare Error 525: SSL Handshake Failed
• Cloudflare Error 526: Invalid SSL Certificate
• Cloudflare Error 520: Web Server Returned an Unknown Error
• Cloudflare Error 1020: Access Denied
• Cloudflare Error 1015: You Are Being Rate Limited
• Cloudflare Error 1016: Origin DNS Error