cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received
A PHP cURL (or Guzzle) request timed out before the remote server answered.
cURL error 28Operation timed out afterConnection timed out after Meaning
Error 28 is cURL’s timeout. “0 bytes received” usually means the connection was never answered (firewall, wrong host); a partial byte count means the server was too slow.
Common causes
- Remote API slow or down
- Outbound firewall on the host blocking the port
- DNS slow
- Timeout set very low
⚡ Quick fix
- Test reachability from the server with curl on the command line
- Set sensible CURLOPT_CONNECTTIMEOUT and CURLOPT_TIMEOUT
- Retry idempotent calls with backoff
Detailed fix by platform
PHP
- Guzzle:
new Client(['connect_timeout' => 5, 'timeout' => 20])
How to diagnose
- Bytes — 0 bytes (no answer) or partial (slow)?
- Reachability — curl from the same server
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in PHP
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026