WordPress cURL Error 28 usually means WordPress cannot complete an outbound HTTP request before the connection/operation timeout. The safest repair starts by identifying the destination hostname, timeout value, Site Health/REST output and server firewall/DNS logs before changing plugins, code or server settings.
Symptoms
Use the exact symptom and affected URL as the starting point. WordPress cURL Error 28 can look similar across sites even when the root cause is completely different.
- Site Health reports cURL error 28.
- Plugin API calls, webhooks or updates time out.
- REST or loopback tests fail intermittently.
- The destination works from a browser but not from the WordPress server.
Common causes
The main areas to investigate are slow DNS, blocked outbound traffic, remote API latency, firewall rules, SSL negotiation, loopback issues or overloaded hosting. A good diagnosis narrows these possibilities with logs and request-level evidence instead of changing multiple systems at once.
- Outbound connections are blocked or rate-limited by hosting/firewall rules.
- DNS resolution on the server is slow or failing.
- The remote service is slow or unavailable.
- A security plugin or proxy interferes with loopback/outbound requests.
- The server is overloaded and cannot complete the request in time.
Safe diagnosis
- Identify the exact destination and request context.
- Test DNS and outbound HTTPS from the same server environment.
- Compare direct server requests with requests routed through a proxy/CDN.
- Check host firewall and application logs for blocked or delayed connections.
Production safety: Create a current backup or recovery point before changing code, database values, plugins, PHP, rewrite rules or server configuration. On WooCommerce and lead-generation sites, test disruptive changes in staging whenever possible.
How the issue is fixed
- Correct DNS/firewall/proxy rules that block the destination.
- Repair the plugin integration if it is calling an invalid or slow endpoint.
- Resolve loopback configuration where WordPress is calling itself.
- Retest Site Health, the plugin action and any affected webhooks.
What to avoid
Avoid this shortcut: Do not blindly increase HTTP timeouts. If the server cannot reach the destination because of DNS or firewall rules, a longer wait only delays the same failure.
When expert troubleshooting makes sense
If wordpress curl error 28 is affecting revenue, wp-admin access, publishing, checkout, forms or a live campaign, the priority is a reversible fix with a documented root cause. WP•FIX separates ordinary software faults from security incidents, so suspicious redirects, unknown administrators or injected code are handled through the malware-response path instead of being treated as a normal bug.
FAQ
What usually causes WordPress cURL Error 28?
Common causes include slow DNS, blocked outbound traffic, remote API latency, firewall rules, SSL negotiation, loopback issues or overloaded hosting. The visible symptom alone is not enough to identify which one is responsible.
Can WordPress cURL Error 28 be fixed without wp-admin?
Often yes. Hosting logs, SFTP/SSH, database tools, browser developer tools or the hosting control panel can provide enough evidence when wp-admin is unavailable.
Should I disable every plugin to fix WordPress cURL Error 28?
A full plugin shutdown can be useful as a controlled test, but on a live business site it can create new failures. It is safer to collect evidence and isolate the likely component with a reversible plan.
When should I request professional WordPress troubleshooting?
If the site is down, checkout or lead generation is affected, the error returns after a temporary workaround, or the cause is unclear from logs, a targeted diagnosis reduces risky trial-and-error.
Need WordPress cURL Error 28 fixed?
Send the exact error or broken behavior, the affected URL and what changed before it started. No passwords are requested in the form.
Request professional troubleshooting