Andreas Posted January 24, 2011 Share Posted January 24, 2011 Since Upgrading to WHMCS 4.4.2 I am getting errors with new signups. I am noticed on one order The welcome email was never sent out. I checked the logs and found this. Module Create Failed - Service ID: 21 - Error: (Curl Error) Operation timed out after 150002 milliseconds with 0 bytes received - code: 28 The I got another order today, and noticed the only email I got wa the email from paypal that I got funds in my account. I logged into WHMCS, and noticed there was a new account created. Checked the logs and found this again Module Create Failed - Service ID: 23 - Error: (Curl Error) Operation timed out after 150000 milliseconds with 0 bytes received - code: 28 THis time not user account or pwd was generated. Any idea what is going on? 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted January 25, 2011 WHMCS Support Manager Share Posted January 25, 2011 It means your server is taking longer than 150 seconds to create the account so WHMCS gives up waiting. You'll need to optimise your server so it takes less than 150 seconds. Nothing related to the upgrade. 0 Quote Link to comment Share on other sites More sharing options...
mysmallbizu Posted January 31, 2011 Share Posted January 31, 2011 It means your server is taking longer than 150 seconds to create the account so WHMCS gives up waiting. You'll need to optimise your server so it takes less than 150 seconds. Nothing related to the upgrade. I'm getting a similar error as well, nothing has changed on the provisioned machine, only thing that has changed is the upgrade of whmcs... Error: (Curl Error) connect() timed out! - code: 28 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted February 1, 2011 WHMCS Support Manager Share Posted February 1, 2011 This could be because your server was heavily overloaded at the time it was attempted and you should find it only occurs if your server is very busy at the time. This response could also suggest you have entered an incorrect IP in the server profile or a firewall blocking the connection. The port being used depends on what module you are using but for cPanel it would be 2086/2087, Plesk 8443, DirectAdmin 2222, etc... You would need to verify that the ports are open for incoming and outgoing connection on both the local and remote servers. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.