Module Command Error (Curl Error) Operation timed out after 400000 milliseconds with

[ahsteve]

Hello Guys,

 

I am getting this error while doing pretty big task, like suspending resellers with more than 300 accounts .... etc. The actual operation is not getting completed within the 400000 milliseconds range, so I need help in increasing the timeout limit.

 

Steve

[ahsteve]

This is the actual error

 

Module Command Error (Curl Error) Operation timed out after 400000 milliseconds with 47592 bytes received - code: 28

 

Steve

[ahsteve]

Hello,

 

Can someone help me on this.

 

Steve

[WHMCS John]

Hi,

The causes of a curl 28 error are similar to a curl 7 error, so please start your troubleshooting at http://docs.whmcs.com/Common_Troubleshooting_Tips#Server_Command_Error_-_Curl_Error_-_Couldn.27t_connect_to_host_.287.29

[ahsteve]

Hello John,

 

The issue discribed in error 7 is related with firewall and other inaccessibility issues. In my case, whmcs is able to connect to the server and start the job. But the problem is the server is unable to complete the process with in the mentioned time (400000 milliseconds) . The curl timeout value is 6.6 minutes or 400000 millisec, my process takes more than 15 mints to complete. So I need help in increasing the timeout value to something more that 6.6 minutes.

 

Steve

[WHMCS John]

Hi,

That's a really long time, but if you please open a support ticket advising which module you're using, our developers can usually customise the code to extend the timeout for you.

[DavidBee]

Whats really a long time? The time it takes to suspend over 300 accounts or the time allowed before time-out?

 

(400 000 milliseconds) / 300 = 1.33333333 seconds an account.

 

I would consider maybe doing this via WHM or shell then updating the WHMCS manually.

[Gama Laptop]

Currently I also get this error with my Wordpress site, I see it says it affects SEO.
Please guide how to fix this problem!
Thank you