topic Re: SSL connect error in Integration and Testing

SSL connect error

alexanderm — Mon, 22 May 2017 16:58:15 GMT

Hello

When try send request to AuthnetAIM arise problem with connection SSL on our test server.
We switched off old TLS 1.0 and 1.1, as had been said in instruction.
But we still have problem with SSL connect error.
We checked certificate by https://www.ssllabs.com/ssltest/analyze.html and get next result

Protocols
TLS 1.2 Yes
TLS 1.1 No
TLS 1.0 No
SSL 3 No
SSL 2 No

Server Key and Certificate #1

Key RSA 2048 bits (e 65537)
Weak key (Debian) No
Issuer RapidSSL SHA256 CA
AIA: http://gp.symcb.com/gp.crt
Signature algorithm SHA256withRSA
Extended Validation No
Certificate Transparency Yes (certificate)
OCSP Must Staple No
Revocation information CRL, OCSP
CRL: http://gp.symcb.com/gp.crl
OCSP: http://gp.symcd.com
Revocation status Good (not revoked)
DNS CAA No (more info)
Trusted Yes

Additional Certificates (if supplied)

Certificates provided 2 (2508 bytes)
Chain issues None
Valid until Fri, 20 May 2022 23:45:51 UTC (expires in 4 years and 11 months)
Key RSA 2048 bits (e 65537)
Issuer GeoTrust Global CA
Signature algorithm SHA256withRSA

nginx/1.10.3
PHP 5.6
Can you please tell us about mistake in our settings.

Thanks

Re: SSL connect error

NexusSoftware — Mon, 22 May 2017 18:12:28 GMT

Try running the following test script, to see what version TLS your cURL is using to connect with:

<?php 
$ch = curl_init('https://www.howsmyssl.com/a/check');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$data = curl_exec($ch);
curl_close($ch);

$json = json_decode($data);
echo $json->tls_version ."\n";

Re: SSL connect error

alexanderm — Tue, 23 May 2017 15:12:16 GMT

Reason what curl used TLS 1.0, because of was old curl version (earlier 7.34)

Thank you so much

Re: SSL connect error

NexusSoftware — Tue, 23 May 2017 15:42:35 GMT

You're welcome.

Re: SSL connect error

idsinc001 — Tue, 27 Mar 2018 20:51:21 GMT

im using TLS 1.2

still i cannot connect

it gives me error connecting to authorize.net