How to Fix Cloudflare Error 524 (Timeout Occurred): 6 Proven Methods

TL;DR: Cloudflare Error 524 means Cloudflare connected to your origin server but the server took too long to send a response, so Cloudflare gave up after 100 seconds. The fix almost always lives on your origin server, not in Cloudflare itself: increase PHP’s execution time limit, hunt down slow database queries, or disable a misbehaving plugin.

Last Updated: July 2026. Tested against WordPress 6.7, PHP 8.3, and Cloudflare’s current proxy rules.

You open your WordPress site, and instead of your homepage you see a stark white page reading “Error 524 — A Timeout Occurred.” Visitors bounce. Orders stop. Support tickets pile up. The good news: a Cloudflare error 524 timeout fix is usually straightforward once you know where to look. This guide walks through every common cause and six specific, step-by-step remedies for WordPress-hosted sites in 2026.

What Is Cloudflare Error 524?

Try GigaPress AI Free →

Error 524 is a Cloudflare-specific HTTP status code that means:

• Cloudflare successfully established a TCP connection to your origin (web) server.
• Cloudflare sent the HTTP request.
• Your origin server never sent a complete HTTP response within Cloudflare’s timeout window.
• Cloudflare gave up and returned the 524 error to the visitor.

Cloudflare’s default origin response timeout is 100 seconds on all free and Pro plans. Enterprise plans can request an extended timeout. If your server needs longer than 100 seconds to generate a response, you will see 524 errors no matter how healthy everything else looks.

Error 524 is different from similar-looking errors. A Cloudflare Error 521 means the connection was refused entirely — the server was not listening. A 504 Gateway Timeout is a generic HTTP-level timeout that can appear even without Cloudflare. A 524 is always Cloudflare-specific and always means a slow, unresponsive origin.

What Causes Cloudflare Error 524 on WordPress Sites?

Before you apply a fix, you need to know which process is eating up the time. The most common culprits on WordPress sites are:

• PHP max_execution_time set too low. PHP has its own internal timer. If a script hits that limit before Cloudflare’s 100-second window, PHP terminates the process and the response never completes.
• Slow or unoptimized MySQL queries. A poorly indexed database table can turn a simple page load into a multi-second query marathon, especially on WooCommerce stores with thousands of orders.
• Large file uploads or imports. Importing a WooCommerce product CSV or a large media file through the WordPress admin can easily exceed 100 seconds on shared hosting.
• A poorly written or conflicting plugin. Some plugins run expensive background tasks on every page load, blocking the PHP process until they finish.
• Overloaded server resources. If CPU or memory is exhausted on the host, every request slows down proportionally.
• External API calls that hang. Payment gateway callbacks, newsletter API calls, or social login providers can cause PHP to wait for an external response, stalling the page.

How to Diagnose the Root Cause

Do not guess. Run these diagnostic steps first so you apply the right fix.

Check Your Server Error Logs

In cPanel, navigate to Logs and open the PHP Error Log and the Apache/Nginx Error Log. Look for lines timestamped around the time the 524 occurred. Common patterns include “Maximum execution time of X seconds exceeded,” “MySQL server has gone away,” or “connection timed out” from a third-party API domain.

Test the Request Without Cloudflare

Temporarily set Cloudflare to Development Mode (Cache tab in the Cloudflare dashboard) or pause Cloudflare entirely for your zone. Then trigger the same action that caused the 524. If the request now completes slowly but without error, the server is genuinely slow. If it returns a different error code, the problem may be specific to Cloudflare’s interaction with your server.

Enable WordPress Debug Mode

Add these lines to your wp-config.php file temporarily:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Reproduce the 524, then check /wp-content/debug.log for PHP errors or warnings that pinpoint the slow code. Remember to remove or disable these constants once you have finished diagnosing.

Run a Query Monitor Check

Install the free Query Monitor plugin from WordPress.org. Load the slow page while logged in as an administrator. Query Monitor will show you every database query, how long each one took, and which plugin or theme triggered it. Any query taking over 500 ms is a red flag worth investigating.

6 Proven Methods to Fix Cloudflare Error 524 in 2026

Method 1: Increase PHP max_execution_time

PHP’s max_execution_time directive controls how many seconds a single PHP script is allowed to run. The default is often 30 seconds on shared hosts, well below Cloudflare’s 100-second limit. If PHP kills the script at 30 seconds, Cloudflare never gets a response.

Option A: Edit php.ini

If your host allows direct php.ini access, find or create a php.ini file in your WordPress root directory and add:

max_execution_time = 300
max_input_time = 300

Option B: Edit .htaccess (Apache)

Open your .htaccess file in the WordPress root and add this line above the WordPress rewrite block:

php_value max_execution_time 300

Option C: Add to wp-config.php

You can also set a higher limit from within WordPress itself. Add this line near the top of wp-config.php, before the line that reads “That’s all, stop editing!”:

set_time_limit( 300 );

A value of 300 seconds gives your scripts plenty of runway before Cloudflare’s 100-second cutoff becomes the binding constraint for normal requests. For very large imports or batch jobs, you may need to bypass the web entirely and run them via WP-CLI on the command line, which is not subject to Cloudflare’s timeout at all.

Method 2: Optimize Slow MySQL Database Queries

Database bottlenecks are one of the most common causes of the Cloudflare error 524 timeout on mature WordPress and WooCommerce sites. Use these steps to find and fix them.

Step 1: Enable the MySQL slow query log. In your MySQL configuration (my.cnf or my.ini), set:

slow_query_log = 1
slow_query_log_file = /var/log/mysql/slow.log
long_query_time = 2

Restart MySQL. Any query taking over 2 seconds will be logged. Review the log after reproducing the 524 to identify the offending query.

Step 2: Run OPTIMIZE TABLE on bloated tables. WooCommerce’s wp_options, wp_postmeta, and wp_woocommerce_sessions tables accumulate fragmented rows over time. In phpMyAdmin, select these tables and run “Optimize Table” from the Operations menu. Alternatively, use WP-CLI:

wp db optimize

Step 3: Add missing indexes. A missing index on a commonly queried column forces MySQL to perform a full table scan. Query Monitor or a database administration tool like phpMyAdmin can highlight queries doing full scans. Adding the correct index can reduce a multi-second query to milliseconds.

Step 4: Clean up transients and post revisions. Accumulated transients and thousands of post revisions bloat the wp_options and wp_posts tables. Use a plugin like WP-Optimize (actively maintained, available on WordPress.org) to clean these safely.

Method 3: Disable or Replace Problem Plugins

Plugins are the number-one source of unexpected slowness on WordPress sites. A single plugin doing something expensive on every page load — fetching a remote API, running an unindexed database query, or blocking PHP while waiting for a lock — can push response time past Cloudflare’s 100-second threshold.

Bisect method: Deactivate all plugins at once via the Plugins screen in the WordPress admin (or via FTP by renaming the /wp-content/plugins/ directory). If the 524 disappears, reactivate plugins one at a time and test after each until the problem returns. The last plugin you activated is the culprit.

What to look for in Query Monitor: Sort database queries by duration. If a specific plugin function appears at the top of the list with query times in the multi-second range, that plugin is the problem even if it is a popular one.

Common offenders include:

• Backup plugins that schedule full-site backups during peak traffic hours.
• Social proof or live visitor counter plugins that poll external APIs synchronously.
• Poorly configured WooCommerce shipping rate calculators that call external rate APIs on every cart load.
• Page builder plugins that load large template libraries on every admin request.

Method 4: Increase Cloudflare’s Proxy Read Timeout (Enterprise Only)

On Cloudflare’s free, Pro, and Business plans, the 100-second proxy timeout is fixed and cannot be changed through the dashboard. On Enterprise plans, you can open a support ticket with Cloudflare to request an increased timeout for specific routes, such as a WooCommerce checkout endpoint or a REST API route used for large data imports.

However, for most WordPress site owners, raising the timeout is not the right fix. A response that legitimately takes more than 100 seconds is a server-side performance problem. Masking it with a longer timeout just means visitors wait longer before the page eventually loads, which harms both user experience and Core Web Vitals scores. Fix the root cause instead.

One Cloudflare setting that is available on all plans: the Proxy Status for DNS records. If you temporarily set your A record from “Proxied” (orange cloud) to “DNS Only” (grey cloud) in the Cloudflare DNS tab, requests will bypass Cloudflare entirely. This removes the 100-second constraint and confirms whether the issue is a Cloudflare interaction or a pure server performance problem.

Method 5: Fix Large File Upload and Import Timeouts

Importing large WooCommerce product CSVs, uploading large video files through the WordPress media library, or running a WordPress XML importer are all operations that commonly trigger a 524 because they are processed synchronously through the web interface.

For file uploads: Increase PHP’s upload limits alongside the execution time. In php.ini or your host’s PHP settings panel:

upload_max_filesize = 256M
post_max_size = 256M
max_execution_time = 300
max_input_time = 300

For large data imports: Use WP-CLI to run imports from the command line rather than through the browser. WP-CLI commands run outside the web server and are not subject to Cloudflare’s proxy timeout. For example, to import a WooCommerce product CSV:

wp wc product import products.csv --user=admin

For media: Upload large files directly via FTP or SFTP to the appropriate /wp-content/uploads/ subdirectory, then use the WordPress “Add from URL” feature or a plugin like Media from FTP to register those files in the media library without a time-constrained upload.

Method 6: Upgrade Your Hosting Plan or Server Resources

If your error logs show the server is hitting CPU or memory limits before PHP’s execution timer runs out, the root cause is resource exhaustion, not a misconfiguration. Optimizing queries and plugins helps, but at a certain traffic level you simply need more horsepower.

Signs you have outgrown your current plan include: consistent 524 errors during peak traffic hours that resolve overnight; slow query logs showing queries taking 20 or more seconds that are already properly indexed; server load averages that consistently exceed 1.0 multiplied by the number of CPU cores.

Consider moving from shared hosting to a managed WordPress hosting plan that provides dedicated PHP-FPM workers, object caching with Redis or Memcached, and guaranteed CPU/RAM allocation. Managed hosts typically use Nginx with PHP-FPM pools, which handle concurrent requests far more efficiently than Apache with mod_php on shared servers. You can find a comparison of hosting options at GigaPress WordPress Hosting.

For sites with intermittent database connection issues alongside the 524 errors, see the full troubleshooting guide at WordPress Error Establishing Database Connection: Step-by-Step Fix 2026.

Cloudflare 524 vs Other Timeout and Gateway Errors

Knowing which error you are dealing with saves diagnostic time. Use this table to distinguish related errors:

Error Code	What It Means	Where the Problem Lives	Best For
524	Cloudflare connected, server too slow to respond	Origin server performance	Slow PHP/DB, resource overload
521	Cloudflare could not connect to origin	Web server down or refusing connection	Apache/Nginx crash, firewall blocking Cloudflare IPs
504	Upstream server timed out during request	PHP-FPM, upstream proxy, or backend service	Nginx/PHP-FPM misconfiguration
502	Invalid response from upstream	PHP-FPM crash or bad gateway config	PHP process crashes, memory exhaustion
500	Generic server-side error	PHP fatal error, bad .htaccess	Plugin conflicts, corrupted .htaccess

Step-by-Step Checklist: Applying the Cloudflare Error 524 Timeout Fix

If you are not sure where to start, follow this ordered checklist. Work through it top to bottom and stop as soon as the 524 resolves.

1. Check server error logs for “Maximum execution time exceeded” or MySQL errors at the time of the 524.
2. Enable WordPress debug mode and reproduce the error. Review /wp-content/debug.log.
3. Install Query Monitor and identify any database queries taking more than 1 second.
4. Set max_execution_time = 300 in php.ini or .htaccess and test again.
5. If the 524 only occurs on specific admin actions (imports, backups), switch those operations to WP-CLI.
6. Deactivate all plugins, test, then reactivate one by one to isolate a problem plugin.
7. Run wp db optimize and clean up transients via WP-Optimize.
8. If the server shows consistent resource exhaustion, upgrade the hosting plan.
9. For operations that legitimately need more than 100 seconds, move them out of the web request entirely using WP-Cron or a background job queue.

Preventing Cloudflare Error 524 from Recurring

Once you have cleared the immediate 524 error, put these practices in place to keep it from coming back.

Use object caching. Redis or Memcached stores the results of expensive database queries in memory. Subsequent requests pull data from the cache instead of re-running the query. Most managed WordPress hosts include Redis; on shared hosting, a plugin like W3 Total Cache can connect to a local Memcached instance if one is available.

Schedule heavy tasks outside peak hours. WP-Cron-based backups, database cleanups, and report generation should run at 3 AM, not noon. Managed backup plugins like UpdraftPlus allow you to set a specific schedule.

Set up Cloudflare Health Checks and alerts. Cloudflare’s Health Checks feature (available on Pro plans and above) monitors your origin and can alert you before a slowdown turns into a full outage. Pair it with an uptime monitor from a service like UptimeRobot for free external monitoring.

Keep PHP, WordPress, and plugins updated. PHP 8.3 is substantially faster than PHP 7.4 on most workloads. Keeping WordPress core and plugins current ensures you benefit from performance improvements and reduces the risk of resource-hungry legacy code.

Profile before you add plugins. Every plugin you install has a performance cost. Before adding a new plugin, use Query Monitor to establish a baseline page load database query count. After activation, run it again. If the count or time has jumped significantly, look for a lighter alternative or implement the functionality manually.

Want a Pro WordPress Site in Minutes?

GigaPress AI builds you a full WordPress site in about 15 minutes — AI handles layout, styling, content, and images. Free to design, only pay when you’re ready to go live. If you are building a fresh WordPress site on managed infrastructure, GigaPress AI Builder sets you up on hosting optimized for fast PHP execution, so Cloudflare 524 timeouts from under-resourced servers are far less likely from the start.

Frequently Asked Questions About Cloudflare Error 524

How long does Cloudflare wait before showing a 524 error?

Cloudflare waits exactly 100 seconds for an HTTP response from your origin server on free, Pro, and Business plans. If the server has not sent a complete response within that window, Cloudflare closes the connection and returns the 524 error to the visitor. Enterprise customers can negotiate a longer timeout with Cloudflare support for specific routes.

Can I fix Cloudflare error 524 by pausing Cloudflare?

Pausing Cloudflare or setting your DNS record to “DNS Only” will stop the 524 from appearing because Cloudflare is no longer proxying the request. However, this is not a real fix. It removes Cloudflare’s security, CDN caching, and DDoS protection. The correct approach is to fix the underlying server slowness so responses complete within 100 seconds with Cloudflare active.

Why does error 524 only happen during WooCommerce checkout?

WooCommerce checkout pages commonly trigger 524 errors because checkout involves multiple synchronous operations: inventory checks, tax calculations, real-time shipping rate API calls, and payment gateway pre-authorization requests. Any one of these can introduce seconds of latency. Start by checking whether a specific shipping carrier API or payment gateway is the slow component, using Query Monitor’s request tab to see external HTTP calls made during checkout.

Does increasing PHP max_execution_time fix Cloudflare 524?

It depends on the cause. If PHP is terminating the script before Cloudflare’s 100-second window, then yes, increasing max_execution_time will prevent the premature script death and allow the response to complete. However, if the script genuinely needs more than 100 seconds (for example, processing a 50,000-row CSV import), increasing PHP’s limit will not help because Cloudflare will still cut the connection. In that case, move the operation to WP-CLI or a background queue.

Is Cloudflare error 524 the same as a 504 Gateway Timeout?

They are similar but not identical. A 504 Gateway Timeout is a standard HTTP status code that any reverse proxy (Nginx, a load balancer, Cloudflare) can return when an upstream server does not respond in time. A 524 is a Cloudflare-proprietary code that specifically means Cloudflare’s proxy read timeout was exceeded. The practical difference: if you see 524 only when Cloudflare is active and the request succeeds (slowly) when Cloudflare is bypassed, it is a 524 problem. If you see 504 even without Cloudflare, it is an Nginx or PHP-FPM configuration issue on your server.