Jump to content

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


ahsteve

Recommended Posts

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

Link to comment
Share on other sites

  • 5 weeks later...
  • 4 weeks later...

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • 6 years later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated