Showing results for 
Search instead for 
Did you mean: 

Intermittent cURL errors

Using the AIM service, my users are getting these errors intermittently:


cURL error: SSL connect error

cURL error: <url> malformed


Users get one, the other, or neither error.  In some cases, the user can resubmit the form without changes and it goes through fine.  Sometimes the transaction goes through fine without errors the first time.  We started seeing these errors just today, but that may be because, prior to today, we have not used for the past few weeks.


Here is the bit of PHP where the cURL options are set, in case it reveals anything:


// Setup the cURL request.
  $ch = curl_init();
  curl_setopt($ch, CURLOPT_URL, $url);
  curl_setopt($ch, CURLOPT_VERBOSE, 0);
  curl_setopt($ch, CURLOPT_POST, 1);
  curl_setopt($ch, CURLOPT_POSTFIELDS, implode('&', $pairs));
  curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
  curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
  curl_setopt($ch, CURLOPT_NOPROGRESS, 1);
  curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 0);
  $result = curl_exec($ch);



It may not be relevant, but we are using the commerce_authnet module in the Drupal framework.




I'm getting the error "cURL error: SSL connect error" in the production enviornment. 


I get the following from my local enviornment:


curl -v -v -v -D - ""


* About to connect() to port 443 (#0)

*   Trying

* connected

* Connected to ( port 443 (#0)

* SSLv3, TLS handshake, Client hello (1):

* Unknown SSL protocol error in connection to

* Closing connection #0

curl: (35) Unknown SSL protocol error in connection to


I get the following from my live enviornment:


curl -v -v -v -D - ""


* About to connect() to port 443 (#0)

*   Trying connected

* Connected to ( port 443 (#0)

* Initializing NSS with certpath: sql:/etc/pki/nssdb

*   CAfile: /etc/pki/tls/certs/ca-bundle.crt

  CApath: none

* NSS error -5978

* Closing connection #0

* SSL connect error

curl: (35) SSL connect error

Look like is

getting timout on it once in a while.


Look to be working for me now.



If this problem persists, I would recommending contacting your web administrator or hosting provider and see if they can help you troubleshoot the problem.



i also receive many errors "ssl connect error" from 2014-10-08 17:18 to 2014-10-08 18:18.

what's wrong with it? or anyway to prevent it?

we also Use AIM and CIM.

Thanks, but I am the system administrator / hosting provider.


As it turned out I needed to update the certificates on my server.  a yum update on my Cent OS 6 machine replaced the out-of-date mozilla certificates with newer ones, and the connections to stopped failing.


I do find it funny that everything was working just fine until about 10am yesterday.  Was a change made on your end, yesterday around 10am, that would start rejecting these connections?  If so, it would be nice if you had notified all your customers ahead of time, so that they could be sure their servers were up to date BEFORE that particular time.