PayPal Error (35) error:1408F10B SSL3_GET_RECORD:wrong version number

PayPal Express has been working well up until we received this error.

Dear store owner,
An error occurred when attempting to initiate a PayPal Express Checkout transaction. As a courtesy, only the error "number" was shown to your customer. The details of the error are shown below.



(35) error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

Zen Cart message: An error occurred when we tried to contact the payment processor. Please try again, select an alternate payment method, or contact the store owner for assistance.

Problem occurred while customer was attempting checkout with PayPal
Express Checkout.

We are ZC v1.5.1

Thanks for any insight you can provide.

Phil and Pam
www.heirloomstocherish.com

Two carts just started throwing errors with PayPal Pro.

First error is error:14094410:SSL routines:SSL3_READ_BYTES:sslv3

Second is error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
version number

I found a post here: http://stackoverflow.com/questions/2...r-paypal-maybe

It says they believe PayPal has changed - and the fix someone has discover is this:
curl_setopt($handle, CURLOPT_SSLVERSION, 4);

Has anyone heard anything?

Just found this: https://www.ssllabs.com/ssltest/anal...ypal.com%2Fnvp

Getting this too. Same ZC version 1.5.1

Looks like a sudden change made by Paypal, some discussion here: http://stackoverflow.com/questions/2...r-paypal-maybe

Quote:

---

Originally Posted by Phil Soth

PayPal Express has been working well up until we received this error.

Dear store owner,
An error occurred when attempting to initiate a PayPal Express Checkout transaction. As a courtesy, only the error "number" was shown to your customer. The details of the error are shown below.



(35) error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

Zen Cart message: An error occurred when we tried to contact the payment processor. Please try again, select an alternate payment method, or contact the store owner for assistance.

Problem occurred while customer was attempting checkout with PayPal
Express Checkout.

We are ZC v1.5.1

Thanks for any insight you can provide.

Phil and Pam
www.heirloomstocherish.com

---

Sounds like this (posted about 8hrs ago)
http://stackoverflow.com/questions/2...r-paypal-maybe

I'm not sure this will be of any help though. Point is, you're not alone.

Cheers
RodG

PS: Shoot. you just beat me to it. Exact same link. LOL

Yes, the immediate solution is to change the CURLOPT_SSLVERSION from 3 to 4 ... or comment-out the line entirely.

Quote:

---

Originally Posted by RodG

Shoot. you just beat me to it. Exact same link. LOL

Cheers
RodG

---

Hehe, as you say--good to know we're all aware of it. Hopefully the thread catches the attention of the right people, assuming any ZC updates are needed.
The stackoverflow thread links to the Paypal SDK github discussion, which has been updated to closed/resolved.

Add me to the list as well. Both pro and express checkouts affected. Orders bouncing all morning.

Quote:

---

Originally Posted by DrByte

Yes, the immediate solution is to change the CURLOPT_SSLVERSION from 3 to 4 ... or comment-out the line entirely.

---

In the Paypal github discussion (https://github.com/paypal/rest-api-sdk-php/pull/127) the "official" recommendation appears to be changing CURLOPT_SSLVERSION

I have no expertise here, just reading the posts; happy to follow the official ZC recommendation.
Changes to: "/includes/modules/payment/paypal/paypal_curl.php" correct?

I found the string to change, fortunately its easy:

/web/content/includes/modules/payment/paypal/paypal_curl.php
Line #58 : CURLOPT_SSLVERSION => 3,

Change to CURLOPT_SSLVERSION => 4,

It works ...for now. Thanks for the notice paypal...

Quote:

---

Originally Posted by nightdesigns

I found the string to change, fortunately its easy:

/web/content/includes/modules/payment/paypal/paypal_curl.php
Line #58 : CURLOPT_SSLVERSION => 3,

Change to CURLOPT_SSLVERSION => 4,

It works ...for now. Thanks paypal

---

Good to hear it worked for you. It was a sudden change, but it's related to a new, serious bug with ssl: "Poodle"