Site Health in WordPress is showing a few cURL error 28 errors when we have CiviCRM installed and activated. Deactivate CiviCRM, the problem disappears. Activate it, the problem is back.

I've seen the WordPress Site Health contains critical errors unless CiviCRM is disabled question, but my research has found no justification for the top response that the health checks are inaccurate. So I need to dig deeper to try to solve this.

During a long chat session with tech support for the hosting company (SiteGround), they could find no reason for the error on their end. Server memory is maxed out, phpinfo shows everything is current and up to date (and shows server memory as 768M). So far, all of the diagnostic things I've found online have been dead ends.

With Query Monitor installed, I can see that the offending call is Health_Check_Site_Status->get_test_rest_availability(), which uses the URL


That health check works fine with CiviCRM disabled, but chokes with it activated, giving the cURL error 28.

What is CiviCRM doing that causes that call to fail?

1 Answer 1


When I looked at this I found that SiteHealth does not account for sessions and CiviCRM depnds on them. See the discussion at https://lab.civicrm.org/dev/wordpress/-/issues/32

  • Thanks, Kevin! That discussion has lots of good information about the issue. I'm a little dismayed that CiviCRM seems to be out of whack with how WordPress works, but I guess that's the risk of a tool that supports multiple CMSs. Commented Jun 8, 2020 at 3:37
  • I'd argue that WP should support sessions, but either way, we need it and WP doesn't. I agree the project starting with Drupal gives us a challenge with certain WP conventions. Commented Jun 8, 2020 at 16:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.