Integration and Testing

[jenlampton]

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 - "https://secure.authorize.net/gateway/transact.dll"

* About to connect() to secure.authorize.net port 443 (#0)

*   Trying 64.94.118.32...

* connected

* Connected to secure.authorize.net (64.94.118.32) port 443 (#0)

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

* Unknown SSL protocol error in connection to secure.authorize.net:443

* Closing connection #0

curl: (35) Unknown SSL protocol error in connection to secure.authorize.net:443

I get the following from my live enviornment:

curl -v -v -v -D - "https://secure.authorize.net/gateway/transact.dll"

* About to connect() to secure.authorize.net port 443 (#0)

*   Trying 64.94.118.32... connected

* Connected to secure.authorize.net (64.94.118.32) 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

[RaynorC1emen7]

Look like is https://secure.authorize.net

getting timout on it once in a while.

Look to be working for me now.

[RichardH Administrator]

@jenlampton 

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

Richard

[allen]

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.

[jenlampton]

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 https://secure.authorize.net/gateway/transact.dll 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.