SOLVED – cURL error 28: Operation timed out
WordPress and other applications interact with the server using the REST API. The block editor screen, for example, uses this to view and save your posts and articles.
The REST API request failed due to an error.
Error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)”
cURL error 28: Connection timed out, resulting in sluggish Page Speed Insights, is usually found to occur when you are transferring your site from one cPanel Account to another or to a new server.
However, regardless of how you got the mistake, you must FIX it and close all doors to prevent it from reappearing.
Is your site taking a long time to load? First and foremost, search for Curl Error 28 on the site. Curl Error 28 – Request Timeout Error – How to Fix The Error that took ten days to fix after trying hundreds of different approaches to get my site back online. Do you want to know how I fixed it?
While most tech blogs and forums will tell you that this is a server mistake, it’s likely that your hosting company won’t be able to help you with this and you’ll be told that something is wrong with your domain.
If your website’s page load time has unexpectedly risen from 10 seconds to 40-50 seconds, this is most likely due to cURL error 28.
Here are a few steps to check error cURL 28, request timeout from your website backend: –
- Go to your WordPress Website back-end with the link – Domain Name/wp-admin.
- Click on Settings & then Tools, there you will find, Site health tab
- This Site Health tab tells you the current Website issues going in your site whether they are related to Plugins, theme updates, old PHP versions, latest WordPress updates, or any other website loading issue.
Server error, certain DNS problems, WordPress Connectivity problem with the domain, old PHP versions, or restricted memory allocated to the site are all predicted to cause cURL error 28 on your websites.
- Check your website PHP version, upgrade if low.
- To find out where the exact problem is occurring, go to PHP INI manager and open the error display setting for the PHP version your site is running.
- Check your WordPress & it’s plugins update – Keep everything updated. Check your domain, IP, and DNS connections. Site – “What’s my DNS” is helpful – https://www.whatsmydns.net/.
- Increase PHP limits (check PHP INI for that) or Add a file “php.ini” in your Website’s root directory with the following code.
- Check the error log in cPanel to check which code line is causing the error in your website.
- Error logs also come up in File manager (outside public_html).
- If you are technically sound (highly recommended), then check your Server Security Configuration in mod_security, in WHM Panel. This is helpful if all your websites are showing the same error. However, if only 1 or 2 sites are showing this error, then the issue lies somewhere else.
- Contact your administrator or Hosting Provider.
- Try “Troubleshooting Plugin” of WordPress and deactivate all plugins through it. Then reactivate your plugins one by one to check which is causing the issue. (I would recommend to completely delete that plugin and then install it, a fresh).
- If none of the above works out, remember the one option left is, you need to completely set up your website again.