topic Re: TLS 1.2 Magento Gateway error: Unable to read response, or response is empty in Integration and Testing

TLS 1.2 Magento Gateway error: Unable to read response, or response is empty

JohnCiesluk — Tue, 06 Mar 2018 22:29:15 GMT

On our server, we have upgraded our ciphers and TLS settings to match api.authorize.net on ssllabs.

Ours: https://www.ssllabs.com/ssltest/analyze.html?d=metrahometheater.com

Theirs: https://www.ssllabs.com/ssltest/analyze.html?d=api.authorize.net

They match.

Yet, we continue to get a 'Gateway error: Unable to read response, or response is empty' error and are unable to process credit cards.

We have tried this in test mode and get the same response.

Any help would be greatly appreciated.

Re: TLS 1.2 Magento Gateway error: Unable to read response, or response is empty

RichardH — Wed, 07 Mar 2018 17:15:07 GMT

Hello @JohnCiesluk

Are you able to succesfully connect to the sandbox using TLS 1.2?

Some developers are reporting that issues connecting to production when they work in sandbox are resolved by switching to use our Akamai endpoints, https://api2* or https://secure2*

Richard

Re: TLS 1.2 Magento Gateway error: Unable to read response, or response is empty

JohnCiesluk — Wed, 07 Mar 2018 21:47:15 GMT

We have the same issues in Sandbox mode.

We have also tried using the api, api2, secure, and secure2 endpoints with no success.

Re: TLS 1.2 Magento Gateway error: Unable to read response, or response is empty

RichardH — Wed, 07 Mar 2018 21:54:46 GMT

@JohnCiesluk

It sounds like your platform may need upgrades or configuration changes to ensure its setup properly. Can you provide details for your system for the community to see?

Richard

Re: TLS 1.2 Magento Gateway error: Unable to read response, or response is empty

JohnCiesluk — Mon, 12 Mar 2018 20:23:43 GMT

Hello All,

Eventually we solved the problem.

This is what we did to solve it:

We updated libcurl from version 7.19 to 7.58 because all versions prior to libcurl 7.42 default to TLS 1.1 which isn't compatible. So even though our certificate and htaccess was giving us an A rating and using TLS 1.2, our curl was requesting to Authorize.net on TLS 1.1.

Of course, in our case, we are using an older version of Zend server and had to install the update to Zend server. Our version of Zend server does not support the newer versions of libcurl so we had to install it via a workaround which we did compliments of this tutorial:

https://zend18.zendesk.com/hc/en-us/articles/219131697-HowTo-Implement-TLS-1-2-Support-with-the-cURL-PHP-Extension-in-Zend-Server