Troy Posted August 8, 2009 Share Posted August 8, 2009 Anyone having problems with the EnomSSL module? We're just now getting it set up, having performed ssl certificate orders manually previously, but when the customer fills out the configuration form and submits it, we get a Curl error: CURL Error: 56 - Failure when receiving data from the peer Matt suggested it might have something to do with the problems people have been reporting with Enom over the last couple days, but all of our other Enom functions are working fine, and have been for years. I figured I see if anyone else has seen this problem. We're still on 3.8.2 FWIW. 0 Quote Link to comment Share on other sites More sharing options...
pdpd Posted August 9, 2009 Share Posted August 9, 2009 I think this is down to Enoms current problems. Our SSL orders have been fine until this problem in the last couple of days, and now we get the same error as you (56) 0 Quote Link to comment Share on other sites More sharing options...
Troy Posted August 10, 2009 Author Share Posted August 10, 2009 Good to know! I hope it clears up once Enom fixes whatever the problem is. 0 Quote Link to comment Share on other sites More sharing options...
JLHC Posted August 10, 2009 Share Posted August 10, 2009 Well the SSL error from my end is:- CURL Error: 28 - Operation timed out after 100000 milliseconds with 0 bytes received 0 Quote Link to comment Share on other sites More sharing options...
othellotech Posted August 10, 2009 Share Posted August 10, 2009 >CURL Error: 56 - Failure when receiving data from the peer you get this when enom is too busy/too slow/under maintenance to respond correctly to the API requests - if you raise the occurrences with enom support, tey generally get it escalated and fixed pretty quick Rob 0 Quote Link to comment Share on other sites More sharing options...
bpamiri Posted August 10, 2009 Share Posted August 10, 2009 I too am getting the "CURL Error: 28 - Operation timed out..." but don't know if it is something we are doing or entirely an enom problem. I just started to setup the SSL automation on Friday and started getting this error. Initially I thought it was due to our IP not being set properly on our enom account, but domain registrations work fine, domain registration syncing works fine, and it looks like the beginning of the SSL cert process works fine. Basically the cert record is created and the fees are deducted from our account but when the customer tries to submit the configuration form they get the time out. 0 Quote Link to comment Share on other sites More sharing options...
Troy Posted August 10, 2009 Author Share Posted August 10, 2009 I finally got one to go through - so seems it's definitely an Enom problem. 0 Quote Link to comment Share on other sites More sharing options...
DataViking Posted August 10, 2009 Share Posted August 10, 2009 I get the curl 28 when creating an account in the server not at enom 0 Quote Link to comment Share on other sites More sharing options...
othellotech Posted August 11, 2009 Share Posted August 11, 2009 I get the curl 28 when creating an account in the server not at enom Then your server is one-or-more of: *overloaded *incorrectly setup *busy *junk *firewalling you off *with an oversold provider start by checking the f/wall and running top ... 0 Quote Link to comment Share on other sites More sharing options...
cyberneticos Posted October 18, 2009 Share Posted October 18, 2009 or you're tryign to create a user on that server that already exists (just happened to me) Edit: Nevermind, that wasn't it. 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.