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

[mprough]

What about USPS?

[Phil Soth]

I have made the change to 4 and everything is back on track!

To underscore earlier praises, thank you so much for the quick and accurate response to this problem.

BTW, I also called PayPal this morning, and the tech told me outright that it was not a PayPal problem, but a selling platform problem, and that if I was paying for a website ( as opposed to using Zen Cart ), this would probably have been resolved before I had seen it appear. I felt dutifully spanked for my transgression, and slinked off into the sunset....

Anyway, thanks again - - - -you people are exceptional!

Phil
Heirlooms To Cherish

[DrByte]

What about USPS?

For USPS, if you're getting the same error, simply comment-out the CURLOPT_SSLVERSION line. I posted similarly in the Release Announcement earlier. I'll update it with more specific wording shortly.

(That said, I recall a time I was working with Ajeh where it actually *needed* v3 specified ... so change according to your server requirements, ie: whatever stops throwing any errors.)

[DivaVocals]

if I was paying for a website ( as opposed to using Zen Cart ), this would probably have been resolved before I had seen it appear.

That's like the dumbest a$$ed remark the tech could have made.. I DO HOPE this foolish person tells one of their larger corporate clients who ALSO do not have any kind of "paying website" (because they have a tech dept that built their site) this SAME message..

**SMH**

[DrByte]

I WOULD NOT CHANGE IT TO v1.

SSL v3 IS NOT THE SAME AS TLS v1

THERE IS A LOT OF CONFUSION IN THE PHP DOCUMENTATION and testing various approaches yields confusing results.

If you're uncomfortable with setting it to v4 (which technically doesn't yet exist), then simply comment-out the line, so that the version is auto-negotiated with the server. (Which is really the desired result anyway. The whole reason for specifying v3 initially was that v2 was deemed insecure but was the assumed default, but that has changed in modern PHP versions.)

FYI, I've changed our recommendation to simply comment out the CURLOPT_SSLVERSION instead of setting it to v4.

[DrByte]

It's also worth noting that it appears as though PayPal may have recanted their aggressive block of all SSL3 connectivity to their live site, as connections are once again working fine (at this moment) using the original CURLOPT_SSLVERSION => 3 setting.

[bumba000]

That's like the dumbest a$$ed remark the tech could have made.. I DO HOPE this foolish person tells one of their larger corporate clients who ALSO do not have any kind of "paying website" (because they have a tech dept that built their site) this SAME message..

**SMH**

Seconding That /\ /\ /\

[bumba000]

How does this apply to authorizenet_aim.php? Didn't notice a separate thread for it and do see

curl_setopt($ch, CURLOPT_SSLVERSION, 3);

at my 576...

What's the move??

Thanks a bunch,
John

[DrByte]

How does this apply to authorizenet_aim.php? Didn't notice a separate thread for it and do see

curl_setopt($ch, CURLOPT_SSLVERSION, 3);

at my 576...

What's the move??

Thanks a bunch,
John

IMO I'd leave it alone for now (I'm not seeing any errors with Authnet as-is right now), as even PayPal has apparently relaxed their initial hyper-protective rejection of all SSL3 connections. But if the same error pops up suddenly, simply comment out the line.

[mprough]

PP tech support told me it's only a 24 hr reprieve