Platform-specific

    Cloudflare Error 524 on WordPress

    Why it happens on WordPress

    Cloudflare closes the connection after 100 seconds. Long WordPress jobs — imports, backups, WooCommerce reports — exceed that even though they eventually finish.

    The fix on WordPress

    Move long jobs to WP-Cron or a queue and return immediately. For admin-side imports, run them over a Grey-clouded (DNS-only) subdomain so Cloudflare's timeout does not apply.

    Is Cloudflare Error 524 happening on your domain?

    An external probe reports actual response time, which tells you how close normal requests are running to the limit before they tip over.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    If that didn't fix it

    WordPress has its own failure mode, but Cloudflare Error 524 has a wider set of causes that apply everywhere. The most common one overall is: a single request genuinely takes longer than 100 seconds.

    All causes and fixes for Cloudflare Error 524

    Monitor this continuously with LemWatch

    A one-off cloudflare error 524 monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.