Error: cURL error 28: Operation timed out after X milliseconds

I mostly face this error in all my WordPress admin panels in plugin updates or any other external operation
I have seen many community threads but couldn’t find any useful

It would be greatly appreciated if someone could get this solved and let me know how actions to take in cyberpanel admin panel


Hello @ideveloppro

cURL operation timed out. Check PHP memory limit, PHP timeout settings, WordPress timeout settings, Firewall settings e.g. CSF or Imunify settings

These are the PHP settings, I guess they are fine. Let me know your view

I am using CSF not imunify
These are the following settings, let me know if you can find anything wrong

Also, it would be great if you can share what security settings are best to set in cyberpanel so that I don’t face these types of problem next

Hello @ideveloppro

It could also be caused by a plugin. Check your wordpress plugins. To check for a plugin conflict you can temporarily deactivate all other plugins, and then see if it Screenshot by Lightshot this works like try to update wordpress core.

  • First disable all security modules - CSF, modsecurity etc

  • Secondly disable all plugins

  • Test if you can update WordPress core

  • Activate plugins one by one testing editing a post or page/ updating core/ leveraging WP-REST API etc

Post here if you need more clarification

Till I know, the firewall is the one conflicting because this is happening in all WordPress accounts and they have been built for 2 3 years running on other servers and now on cyberpanel so it’s not about plugins

Can you share with me the best settings for cyberpanel firewall CSF/ModSecurity etc


Personally I do not use CyberPanel ModSecurity because development stopped long time ago. And i do not recommend it for any of my customers. Prefer CloudFlare WAF, Imunify

As for CSF its just a packet inspection app that from experience only stops intrusions such as bruteforce exploitations such as wordpress XMLRPC. The default configuration is sufficient enough. Install as is and csf will do the rest. Prefer CrowdSec

1 Like

I am not using ModSecurity in my server (screenshots below)

My CSF is turned on in cyberpanel

Let me know if I can do anything else then this

I see you have an extra rule in the ModSecurity rules. The default is sually modsecurity SecRule 99999

SecRule ARGS "\.\./" "t:normalisePathWin,id:99999,severity:4,msg:'Drive Access' ,log,auditlog,deny",

and nothing else. WordPress should run as expected

i saw this problem also my websites. so i changed my dns resolver addresses to google dns


u can do this on your vps dashboard if u are using vps. like hostinger.

also another solution is change nameservers directly server files.

/etc/resolv.conf file.

backup file and after delete inside and write new nameservers like up.

now my website working veryfast

1 Like

So do you mean to say I remove

sudo: unable to resolve host cloud2: Name or service not known,SecRule ARGS "\.\./" "t:normalisePathWin,id:99999,severity:4,msg:'Drive Access' ,log,auditlog,deny",

& replace it with
SecRule 99999

I am using digital ocean and Cloudflare as DNS
My current view of /etc/resolv.conf is as follows


Let me know if I can change the records as per what you mentioned

1 Like

Kindly check the directive in code block above its rule 99999. That is the only line that should be there on first install

I have never changed ModSecurity rules, this is all by default

I am learning it so can you please tell me the steps I need to follow

Go to https://SERVER_URL:8090/firewall/modSecRules and check if this is only line there

Yes its the same

Hello @ideveloppro Sorry you still experiencing the same issue.

Can you disable all firewalls, security modules and WAFs

Same problem :frowning:

Do you have a firewall wp plugin?

Try deactivate all plugins and try update wp core

Post a screenshot of Tools => Site Health >> Info

Thanks bro, I was experiencing the same problem, all my wordpress websites were slow and in the Query Monitor it was showing cURL error 28, after I changed the the DNS resolver it was back to normal. So much thanks!