If you’ve encountered the cURL error 28, don’t worry—this guide will help you resolve it. Typically, this error comes as a message in the Site Health section of your WordPress dashboard is labeled under “The REST API encountered an error.” When expanded, you might see:
Error: cURL error 28: operation timed out after x milliseconds with x bytes received (http_request_failed).
In some cases, you might also see a related message:
The loopback request to your site failed, meaning features relying on them are not working as expected.
This article explains what this error means and provides step-by-step solutions to fix it.
Understanding cURL and the error
What is cURL?
Client URL (cURL) is a command-line tool used to transfer data to and from a server via URLs. In WordPress, cURL powers the REST API, enabling your site to send and receive data with its server and database.
The cURL error 28 indicates a timeout—when a request takes too long to complete. This timeout disrupts the flow of data, triggering the error message.
Common causes and troubleshooting steps for cURL error 28
Check your firewall
A WordPress firewall might flag certain REST API requests as suspicious and block them. To verify if this is the issue:
- Temporarily disable your firewall. Check if the error persists.
- Re-enable your firewall after testing. If the firewall is causing the issue, consider switching to another plugin or contacting its developers for further support.
Important:
Ensure your firewall is reactivated after testing to maintain your website’s security.
Check your plugins
A plugin might be causing the timeout. To identify the culprit:
- Deactivate your plugins one by one:
- Go to Plugins > Installed Plugins in your WordPress Admin dashboard or to the plugins menu of your 10Web dashboard.
- Disable each plugin individually, checking for the error after each deactivation.
- If the error resolves, the last plugin deactivated is likely the source. Contact the plugin’s support team or look for alternatives.
Note:
If the error blocks access to your WordPress dashboard, you can disable plugins manually by connecting to your site via SFTP or SSH and renaming plugin folders there.
Check your SSL certificate
A misconfigured or expired SSL certificate can block “insecure” requests, causing cURL error 28. To fix this:
- Use an online SSL checker (e.g., SSL Shopper) to verify your SSL certificate.
- If you’re using a free SSL certificate from 10Web, you can regenerate it via your 10Web dashboard. Refer to the detailed instructions in 10Web’s documentation for assistance.
Check your DNS settings
Incorrect DNS records can prevent WordPress from processing HTTP requests, triggering the error.
If you were pointing your domain from another registrar instead of obtaining it from 10Web, ensure your domain’s DNS records match the credentials provided in your 10Web dashboard:
- Go to Domains > Manage DNS in the dashboard.
- Compare the A/Nameserver records with those listed in your domain registrar depending on the pointing route you had taken and use a DNS checker tool to confirm proper propagation. You can refer to this domain pointing guide for reference on the correct DNS configuration.
Note:
If you purchased your domain from 10Web, contact our support team if DNS issues persist.
Update PHP version and resources
Outdated PHP versions or insufficient server resources may also cause this error. To address this, ensure your site is running the latest PHP version and try increasing your server’s memory limit via the 10Web dashboard. Refer to this help center guide for step-by-step instructions on upgrading PHP version and modifying PHP resources on 10Web dashboard.
Need further assistance?
If none of the above steps resolve the issue, contact 10Web Customer Care Team for personalized support.