Support » Fixing WordPress » error: The loopback request to your site failed

  • Resolved cfm168



    I have always received the following error warning on site health:
    The loopback request to your site failed, this means features relying on them are not currently working as expected.
    Error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)
    I have WP5.5 and the latest theme Twenty Eleven. Since my eCommerce works fine I’ve just ignored it.

    Is this related to server? If yes, how can I tell my hosting to fix it?

    I tested all plugins one by one but the problem persists.

    Please advise. Thanks in advance!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator bcworkz


    Yes, it’s a server configuration issue. The message means the server cannot make a HTTP request to itself through the cURL package. cURL allows PHP to make requests to its own server and other servers using various protocols like HTTPS, FTP, telnet, etc. It’s possibly a problem with modSecurity configuration, though there are numerous other possible reasons.

    Whether the failure affects you or not depends on what WP functionality you use. It’s usually related to backend functionality and rarely affects frontend functionality AFAIK.

    In asking your host for help, I’d just give them a copy of the site health message itself. They should know about cURL and loopbacks. No further explanation is necessary.

    Checked all plugins one by one and Found two plugins cause the same 3 critical errors report in site health.
    1) An active PHP session was detected
    2) The REST API encountered an error
    3) Your site could not complete a loopback request

    Hope developers can fix it soon.

    @cfm168 – Thanks for the update.

    Which 3 plugins cause those errors? It would be helpful to know.


    I found one plugin named Woocommerce Product Designer has php sessions issue. Deactivate it all issues are resolved. Developer promised to fix this problem but still persists without any further response almost two months now.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.