Paypal express error 35

Surfing round the forum I found something similar, should have bookmarked it, can't find it now.

I installed Paypal Express Checkout, got the handshake error (35). Looked thru the forum, found that Version 1.5.4 contains fixes to this problem, so upgraded - but still the same problem.

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. () - (35) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

I should say that I was expecting to have to reinstall after uploading 1.5.4 but it didn't seem necessary...? Could that be it?

Any other suggestions?

Do you have all of your information entered into the payment module in admin? Sounds simple but once long ago I got snagged with a cut-and-paste problem - the paypal credentials had a period and trailing digits.

Two clicks to uninstall the payment module in admin, then reinstall it carefully entering the required fields. Set paypal to debug to a log file. Then test on the live site and check your logs folder for any errors.

Thanks, I had removed and reinstalled once but did it again anyway, still the same problem. But how do I check the log filer?

FTP on over to your root directory and look for** /logs **within you may find many errors... there should be separate error log files related to paypal only. Those are the ones you need to open and read/post here for help.

Just ensure you NEVER post sensitive data to the forum!

Yeah, I looked there and there's only an htaccess, and 2 index files (html and php) neither with anything in them :(

Okay basics out of the way, you posted this error:

error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

What version of ZC are you using and have you fixed it here:
http://www.zen-cart.com/showthread.php?214916-Important-announcement-about-POODLE-and-payment-security

Recently:
NOTE: Zen Cart v1.5.4 already contains all the POODLE fixes for SSLv3 in all the built-in core payment/shipping modules.

Yep, first thing I did - upgraded from 153 to 154. As I said, I expected to have to go through the re-install, but I didn't. Can/should I "force" a re-install?

jenpen:

Yep, first thing I did - upgraded from 153 to 154. As I said, I expected to have to go through the re-install, but I didn't. Can/should I "force" a re-install?

**It appears your site files have not been upgraded to 1.54 if you are getting this error. **

I'm uncertain about any of the details related to your 'upgrade' to 1.54. If the site was upgraded properly all the new 1.54 files would be up and running with an upgraded database and the original error would not exist.

Did you follow the ZC instructions to perform an upgrade from 1.53-1.54?

Did those files get published to your live site?

What happened to the old files on the server?

You're right, there's a detail I missed. I'll fix it and get back to you. Thanks for your pointers so far.

Progress! A different error now:

We are sorry for the inconvenience. The PayPal account authentication settings are not yet set up, or the API security information is incorrect. We are unable to complete your transaction. Please notify the store owner so they can correct this problem. (10002) 10002 Security error - Security header is not valid

The Paypal settings are all correct. What does "Security header is not valid" mean?

jenpen:

Progress! A different error now:

The Paypal settings are all correct. What does "Security header is not valid" mean?

**Paypal says this...
**
Error code: 10002

Short/Long Message:
Authentication/Authorization Failed - Username/Password is incorrect

Correcting This Error:
This error can be caused by an incorrect API username, an incorrect API password, or an invalid API signature. Make sure that all three of these values are correct. For your security, PayPal does not report exactly which of these three values might be in error.

And be certain you have PayPal Express set for 'Live'** NOT** 'Sandbox'

OK, OK, OK! I misunderstood "sandbox". I thought it meant "testing mode" and I assumed it would be invisible to customers. Wrong and wrong! I took it out of sandbox and now it's working fine.

But, what is sandbox for if not testing? :dontgetit

Great to hear it's working!

Sandbox requires its own paypal sandbox credentials for testing.

I had the same error even after the upgrade to 1.5.4 and creating new Paypal API signature seemed to solve it.