Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix "Loopback Request Failed" in Site Health in WordPress

Short answer

A 'Loopback Request Failed' result means WordPress could not send an HTTP request to its own site address, so scheduled posts, background updates and editor safety checks may not run. Open Tools > Site Health, expand the loopback result and copy the exact error code or message. Fix the cause it names: a plugin or theme conflict, a firewall or Cloudflare rule, a DNS or SSL fault, or a host block.

Key takeaways

  • A loopback request is WordPress calling its own site address over HTTP to run WP-Cron and check plugin and theme edits.
  • The Site Health test posts to wp-cron.php and waits 10 seconds, so a slow or blocked reply fails the test.
  • A plugin or theme conflict is the most common cause, so deactivate plugins and switch to a default theme first.
  • Cloudflare Super Bot Fight Mode can block loopbacks until you turn on its Optimize for WordPress setting.
  • A real server cron job that calls wp-cron.php keeps scheduled tasks running even while the loopback stays broken.
  • If plugin, theme, firewall, DNS and SSL checks all pass, the block sits with the host, so ask for its server logs.

What does “Loopback Request Failed” mean in Site Health?

It means WordPress sent an HTTP request to its own site address and did not get a usable reply within 10 seconds.

The loopback test in WordPress core posts to your site's wp-cron.php file and waits 10 seconds for a reply (checked November 2026).

When no reply arrives, Site Health shows this message: "The loopback request to your site failed, this means features relying on them are not currently working as expected.“ The result is marked as ”critical" in Site Health.

A different result appears when the server answers with the wrong status code. WordPress then marks the test as “recommended” and says the loopback returned an unexpected HTTP status code. A 200 reply is the only pass, and Site Health then reports that the loopback request completed successfully.

What is a loopback request and why does WordPress need it?

A loopback request is WordPress connecting back to its own site over HTTP, using its public site address.

WordPress uses loopbacks to start WP-Cron, which runs scheduled posts and other timed events. Loopbacks are also used by the built-in plugin and theme file editors, which check that a change does not break the site. WordPress Developer Resources' Loopbacks page describes both uses (checked November 2026).

The Site Health check itself is a small version of this process. It sends a POST request to wp-cron.php with a test body and a 10 second timeout, then reports whether the reply arrived. That is why the error names a request, not a file or a setting.

What breaks when loopback requests fail?

Scheduled posts can miss their times, background updates can stall, and the plugin and theme editors lose their safety check.

  • Scheduled posts and other timed events do not run on time.
  • Background updates and other background jobs stall.
  • The plugin and theme editors cannot check edits before saving them.
  • Features that rely on the REST API can fail, and Site Health may also show a REST API error.

Your visitors may notice nothing, since the front end still loads. The damage is quiet: background jobs stop, and you only find out when a post misses its time or an update never arrives. A related cURL error 28 timeout often has the same root cause.

How do you read the exact error in Site Health?

Open Tools > Site Health, click the Status tab, and expand the loopback result to read the full error text.

  1. Log in to WordPress as an administrator.
  2. Go to “Tools > Site Health” and wait for the tests to finish.
  3. Find “Your site could not complete a loopback request” under the critical issues.
  4. Click it to expand the result and read the error line.
  5. Copy the whole message, including the cURL error number or HTTP status code.

Site Health was added in WordPress 5.2, and WordPress.org's Site Health page says the first screen runs the check and then lists critical or recommended improvements (checked November 2026).

Use the Info tab for the details your host will ask for. Kinsta's cURL error 28 guide points to “Tools > Site Health > Info > Server” for the PHP, cURL and OpenSSL versions on the server (checked November 2026).

What do the common loopback error codes mean?

The error code tells you which layer failed: DNS, connection, timeout, SSL, or access control.

ErrorMeaningWhat it usually points to
cURL error 6Could not resolve hostDNS fault on the server
cURL error 7Failed to connect to host or proxyServer unreachable or port blocked
cURL error 28Operation timed outReply took longer than the limit
cURL error 35SSL/TLS handshake problemCertificate or TLS setup fault
cURL error 60Peer certificate cannot be authenticatedCertificate chain or trust fault
HTTP 401UnauthorizedPassword protection on the site
HTTP 403ForbiddenFirewall or security rule block
HTTP 500Server errorPHP error while handling the request

The cURL meanings come from the libcurl error reference, which lists error 28 as an operation timeout and error 60 as a certificate that cannot be authenticated (checked November 2026). Match the code first, then fix only that layer, since each code points to a different cause.

A 403 result is the most common sign of a block. Our guide to fixing the 403 Forbidden error covers the firewall and permission checks in detail.

A 500 result points at a PHP fault instead. Our guide to fixing the 500 internal server error covers the log and plugin checks for that case.

How do you fix a loopback failure caused by a plugin or theme?

Deactivate all plugins and switch to a default theme; if the error clears, reactivate plugins one at a time to find the cause.

WordPress Developer Resources calls a plugin or theme conflict the most common cause of loopback failures, so this is the first fix to try. The Loopbacks handbook page lists the same order: plugins first, then the theme, then the host (checked November 2026).

  1. Go to “Plugins > Installed Plugins”, tick the box at the top to select all plugins, choose “Deactivate” in the Bulk actions menu, and click “Apply”.
  2. Reload “Tools > Site Health” and check the loopback result.
  3. If it passes, reactivate one plugin, recheck Site Health, and repeat until the error returns.
  4. Go to “Appearance > Themes” and activate a bundled default theme, such as Twenty Twenty-Five, to rule out the theme.
  5. If you cannot log in, rename the plugins folder by SFTP so WordPress deactivates them all.

Also check must-use plugins, which the normal deactivation step does not touch. The handbook says to rename the mu-plugins folder to mu-plugins-old for the same test, then restore the name when you finish.

How do you fix a loopback failure caused by a firewall or Cloudflare?

Turn the firewall or bot protection off briefly, retest Site Health, and if the error clears, add a narrow exception for your own site.

A security plugin or server firewall can treat the self-request as suspicious and block it. Kinsta's guide notes that a WordPress firewall may stop a REST API request it sees as a threat (checked November 2026).

  1. In Wordfence, go to “Wordfence > Firewall”, set “Web Application Firewall Status” to “Disabled”, and save.
  2. Reload “Tools > Site Health” and check the loopback result.
  3. If it passes, turn the firewall back on and look for a setting that allows requests to wp-cron.php or your own server IP.
  4. If you use Cloudflare, open the Cloudflare dashboard and turn on “Optimize for WordPress” under Super Bot Fight Mode.

Cloudflare's docs say Super Bot Fight Mode can block WordPress loopback diagnostics, and its Optimize for WordPress setting authorizes the site's automated loopback requests. Steps from the docs: dashboard, “Security Settings”, filter by “Bot traffic”, “Super Bot Fight Mode”, then “Configurations” and turn on “Optimize for WordPress” (checked November 2026).

The feature is available for all Super Bot Fight Mode customers, and the page was updated on 3 August 2026.

Turn the firewall back on after every test. Leaving it off fixes the warning but leaves the site open, which trades one problem for a worse one.

How do you fix a loopback failure caused by DNS or SSL?

Check that the server resolves your domain to the right IP and that the SSL certificate chain is valid, then ask your host to fix what you cannot change.

A faulty or poorly configured DNS server can stop WordPress from loading its own HTTP requests. Kinsta's guide also lists an outdated PHP, cURL or OpenSSL version as a possible trigger, and points to “Tools > Site Health > Info > Server” to check them (checked November 2026).

For a quick DNS check, Kinsta's guide lists public DNS addresses: Cloudflare 1.1.1.1, Google Public DNS 8.8.8.8 and OpenDNS 208.67.222.222. If the server resolves the domain to the wrong IP, only the host can fix the server-side DNS, so send them the error text and the time it appeared.

For SSL, run the Qualys SSL Labs test on your hostname and read its report. A broken chain or an expired certificate explains cURL error 60, and reinstalling the certificate is a host or certificate job in most cases.

Check the server software versions before you ask for an upgrade. WordPress lists its hosting requirements for PHP and related software, so compare your Info tab values with that list.

If the PHP version is old, our guide to updating PHP in WordPress walks through the change. Ask the host to update cURL or OpenSSL, since those are server packages you cannot change from the dashboard.

Can a real cron job work around a failed loopback?

Yes, a server cron job that calls wp-cron.php on a schedule runs scheduled tasks without any loopback request.

WordPress Developer Resources' WP-Cron handbook shows how to set this up. Add define( 'DISABLE_WP_CRON', true ); to wp-config.php, then schedule a system task that calls wp-cron.php.

The handbook's example uses wget --delete-after with your site URL, and a 15 minute schedule looks like /15 * (checked November 2026).

Do not set DISABLE_WP_CRON on its own. Without the server job, nothing runs scheduled tasks at all, so posts, updates and plugin jobs all stop. Pair the two changes in the same session.

This workaround keeps scheduled tasks running, but it does not fix the loopback test. Site Health will still report the failure until the underlying block is fixed, so use the cron job as a bridge, not a final answer.

How do you check that the fix worked?

Reload Tools > Site Health and confirm the loopback result says the request completed successfully.

  1. Reload the “Tools > Site Health” Status tab and wait for the tests to finish.
  2. Confirm the loopback result shows “good” with the message that the loopback request completed successfully.
  3. Schedule a test post a few minutes ahead and check that it publishes on time.
  4. Check “Dashboard > Updates” to confirm background update checks are running again.
  5. Turn back on anything you disabled for testing, such as the firewall.

If the error is still there, read the new error text before changing anything else. A fix can change the code from a timeout to a 403, which means you moved the fault from one layer to another and the next fix is different.

When should you contact your host?

Contact your host when the error stays after plugin, theme, firewall, DNS and SSL checks, since the block is then on the server.

The Loopbacks handbook says to ask whether server-side security rules, firewall rules, DNS configuration, SSL configuration, or HTTP authentication are blocking the site from requesting its own URL (checked November 2026).

Send the host the exact error text, the time it appeared, the steps you already tried, and a copy of your Site Health info. Kinsta's guide makes the same point: the more detail you give, the faster the host can trace the blocked request.

Ask for the server error log entries for wp-cron.php at the time of the failed test. A host-side rule rarely shows in the dashboard, so the log is often the only record of what blocked the request.

What mistakes should you avoid?

Do not disable your firewall or SSL checks for good, and do not edit core files to silence the warning.

  • Leaving the firewall off after a test instead of adding a narrow exception.
  • Turning off SSL verification to make the warning vanish.
  • Setting DISABLE_WP_CRON without a server cron job, which stops all scheduled tasks.
  • Reactivating all plugins at once after the bulk test, which hides the plugin that caused the fault.
  • Editing WordPress core files to hide the Site Health result instead of fixing the cause.
  • Treating a passing front end as proof that nothing is wrong, while scheduled jobs stay broken.

Frequently asked questions

Why does my site load fine for visitors but fail the loopback test?

Visitors reach your site from outside, while a loopback is the server calling itself. A firewall rule, DNS fault or SSL problem can block the server's own request while outside traffic still works, so a healthy front end does not prove loopbacks work.

Can I ignore a failed loopback request?

You can leave it only if scheduled posts publish on time, background updates run and the plugin and theme editors work. If any of those stall, fix the loopback, because the same block is behind the symptom. Check the error code first instead of guessing.

Does a failed loopback mean my site is hacked?

No. The loopback test only checks whether WordPress can reach its own site address over HTTP. A failure is a connection problem, not a security verdict. Read the error code to find which layer failed, and check your security plugin logs if you also see strange admin activity.

Will disabling WP-Cron fix the loopback error?

No. Setting DISABLE_WP_CRON stops WordPress from running WP-Cron on page loads, but it does not repair the failed self-request, so Site Health keeps reporting it. Pair the setting with a server cron job that calls wp-cron.php, and keep fixing the underlying block.

What should I send my host when I ask for help with a loopback failure?

Send the exact error text from Site Health, the time it appeared, the steps you already tried, and a copy of your Site Health info from the Info tab. Ask whether server security rules, firewall rules, DNS, SSL or HTTP authentication are blocking the site from requesting its own URL.

Sources

  1. Loopbacks WordPress Developer Resources
  2. WP_Site_Health::can_perform_loopback() WordPress Developer Resources
  3. Site Health: keep your website healthy WordPress.org
  4. Hooking WP-Cron Into the System Task Scheduler WordPress Developer Resources
  5. Super Bot Fight Mode for WordPress Cloudflare Docs
  6. How To Fix the “cURL Error 28: Connection Timed Out” Kinsta
  7. libcurl-errors Ubuntu Manpages

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test