|
Robert Bertazon
|
July 11, 2018 at 7:19 pm
Today my customers began getting the following error message when trying to process their payment via PayPal Express Payment – “It appears the offsite Payment Method was not configured properly. Please try again or contact info@mdconstructionnet.net for assistance. EE SPCO Reg Step Payment Options – post payment processing 2426.
That last line is what I think it says, the print is too small to really be certain.
Anyway, everything was working fine until today. When I look at the registration information the Gateway Response message in EE says – “Error occurred while trying to setup the Express Checkout.”
Event Espresso 4.9.64.p
WordPress 4.9.7
|
|
Tony
|
July 12, 2018 at 3:44 am
Hi there,
Can you install this plugin on the site:
https://wordpress.org/plugins/tls-1-2-compatibility-test/
Then go to Tools -> TLS 1.2 Test and check if your site passes?
|
|
Robert Bertazon
|
July 12, 2018 at 5:47 am
Hello Tony,
Here is the result from the test. It says it should work.
TLS 1.2 Enabled
Your site should work fine when making calls to gateways and APIs that require TLS 1.2. You may still want to consider the actions below to secure your site as much as possible.
Setting Value Action/Notes
Endpoint https://tlstest.paypal.com/ (PayPal) PayPal_Connection_OK
PHP Version 5.6.32 PHP version 5.5.19 or higher detected.
cURL Version 7.24.0 Upgrade to cURL version 7.34.0 or higher.
cURL SSL Version OpenSSL/1.0.0 Make sure you are running OpenSSL/1.0.1 or higher, NSS/3.15.1 or higher, or the latest version of other cryptographic libraries.
|
|
Josh
|
July 12, 2018 at 7:20 am
Hi,
The report indicates the server needs an update to cURL 7.34.0 or higher, and an update to OpenSSL/1.0.1 or higher. Can you contact your web host to see if they can run those updates?
|
|
Robert Bertazon
|
July 12, 2018 at 8:44 am
Hello Josh,
I am working on that right now. FYI, I use Bluehost and while the report is showing available updates to the cURL protocol, their servers are TLS 1.2 compliant. I am on hold with their support right now awaiting their reply.
|
|
Robert Bertazon
|
July 12, 2018 at 11:38 am
The request to update the servers has been made but It has to be reviewed by persons up the food chain if/before the update are made. However, I was assured their servers are TLS 1.2 compliant and, I have to believe them. I have submitted a support token for this matter as I really need to get my registrations processing again.
|
|
Josh
|
July 12, 2018 at 12:06 pm
Hi there,
We’ve received the support token but I’m afraid the log in details you sent are incorrect. The response from the wp-login.php page says the username is incorrect. Can you please double check the information and re-send the form? Thank you.
|
|
Josh
|
July 12, 2018 at 1:06 pm
Those worked, thank you.
This is the specific error from PayPal when it tries to communicate with your website:
http_request_failed
cURL error 35: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
Can you send the above error code to Bluehost? The error basically means they need to fix/update cURL on the server side.
|
|
Robert Bertazon
|
July 12, 2018 at 1:57 pm
Josh, I am on a call with them right now. Quick question – Do I need to be using REST API now?
|
|
Josh
|
July 12, 2018 at 2:03 pm
Are you asking about the WordPress REST API? If so, the answer is maybe, because some of Event Espresso’s features require the WP REST API. One of them is the Attendee mover add-on.
|
|
Robert Bertazon
|
July 12, 2018 at 2:25 pm
I was just wondering if my problem was because something changed in the last two days and I needed to be using REST instead of NVP/SOAP API integration. It was merely me thinking out loud while I was on hold (something I’ve spent the majority of my day doing).
For what it’s worth, Bluehost is kicking my issue up to the next level.
|
|
Josh
|
July 12, 2018 at 2:49 pm
If you’re using the built in PayPal Express gateway (the one that’s bundled into Event Espresso 4 core) you still use Classic (NVP/SOAP) API credentials:
https://eventespresso.com/wiki/paypal-express-payment-gateway/#locate
|
|
Robert Bertazon
|
July 13, 2018 at 6:22 am
Still not able to process payments through EE. I did not think about this earlier but I use WooCommerce for membership and sales on my site. PayPal payment processing is working through Woo. Still no response or resolution from Bluehost support.
|
|
Josh
|
July 13, 2018 at 8:11 am
Hi Robert,
The PayPal module for WooCommerce doesn’t use the same API as the one that’s bundled with Event Espresso. In any case, if Bluehost can upgrade to newer versions of OpenSSL/cURL that will allow for compliance with PayPal’s new requirements that just got rolled out.
|
|
Tony
|
July 13, 2018 at 8:19 am
Hi guys,
Bluehost need to update the version of cURL and OpenSSL installed on the server, once those are updated the connection should work as expected.
I did not think about this earlier but I use WooCommerce for membership and sales on my site.
It depends on the specific integration method they are using if the above config will be a problem or not. With your WooCommerce setup your using PayPal standard, which basically collects info and then directs the user off to PayPal to make a payment, it won’t be affected by the above in the same way, but have you confirmed that IPN’s are working as expected and your site updates when a user makes a payment?
|
|
Robert Bertazon
|
July 16, 2018 at 9:07 am
Tony,
I saw your post on another thread about this issue. Sure enough, the code you inserted has fixed my problem as well. I appreciate your work to resolve this issue. I was getting very nervous. It’s never fun when things you depend on to make a living don’t work.
Rob
|
|
Tony
|
July 16, 2018 at 9:23 am
My apologies, Bob.
I hadn’t gotten around to updating your post just yet as I’ve been investigating the cause further but I’m glad the change also worked for you. I’ve added another reply to other thread with more details HERE.
As mentioned in other thread, we have a ticket open for our developers to discuss this further and whatever we chose to do to work around this issue will very likely be included in the next update to EE, so my modification will be lost, but replaced with whatever fix we use.
|
