Web Plura

Problem

WordPress cURL Error 28

Diagnose WordPress cURL error 28 timeouts by identifying the remote service, timeout length, DNS path, firewall behavior, and plugin action involved.

WordPress troubleshooting guideWeb Plura Diagnostics - Site Health, Email, Hosting, and Update Risk Advisor

Problem, cause, fix, verify

Problem

A WordPress HTTP request timed out before the remote server returned a usable response.

Audience

Site owners seeing timeout errors from updates, APIs, webhooks, license checks, or Site Health.

First check

Find the destination URL. cURL error 28 is a timeout symptom, not the root cause by itself.

Verify

Repeated retries can create queue backlogs or duplicate provider requests. Confirm the external endpoint and server connectivity before asking users to repeat checkout, imports, or sync actions.

Editorial trust

Published
Updated
Content type
Problems
Review editorial policy

On this page

Symptom

A WordPress HTTP request timed out before the remote server returned a usable response.

For: Site owners seeing timeout errors from updates, APIs, webhooks, license checks, or Site Health.

Diagnosis

What to check before changing the site

Quick Diagnosis

Find the destination URL. cURL error 28 is a timeout symptom, not the root cause by itself.

Provider vs Host

If only one API endpoint fails, start with that provider; if many endpoints fail, inspect hosting/network rules.

Timeout Context

Record whether the timeout happens during updates, license checks, webhook delivery, Site Health, payment callbacks, or background jobs. The affected workflow usually names the right owner.

Retry Discipline

Repeated retries can create queue backlogs or duplicate provider requests. Confirm the external endpoint and server connectivity before asking users to repeat checkout, imports, or sync actions.

WordPress AdminSeverity: MediumLast reviewed: 2026-09-16

Diagnosis

Symptoms, causes, checks, and fixes

Symptoms

  • Logs or Site Health mention cURL error 28.
  • Updates, API calls, webhooks, or external checks fail slowly.
  • The same request may work intermittently.

Most Common Causes

  • Remote API outage.
  • Slow DNS or network path.
  • Firewall or WAF delay.
  • Host outbound HTTP restrictions.
  • Plugin calling an unavailable endpoint.

How To Confirm The Cause

  • Identify the URL WordPress is trying to reach.
  • Check whether only one plugin/service fails.
  • Ask hosting to test outbound connectivity from the server.

Fixes

  • Retry after a confirmed provider outage.
  • Allow required outbound hosts when verified.
  • Disable or reconfigure the plugin making slow external calls.

How To Verify The Fix

  • Repeat the failing action.
  • Confirm the timeout no longer appears.
  • Monitor scheduled tasks that call the same endpoint.

When To Contact Support

Contact hosting when outbound HTTP requests are blocked or DNS/network timeouts happen before WordPress receives a response.

References

Official references

WordPress HTTP API reference