|
Shaun Davis
|
June 11, 2013 at 10:15 pm
I’m am having trouble getting Rapid 3.0 working. Upon registration, it returns “An error has occured in the using of the Eway Rapid 3.0 payment gateway. Please try a different gateway” when I select “Pay by Credit Card”.
Sandbox mode works perfectly. I’ve contacted eway Australia and they can see my sandbox connection attempts but they cannot even see any connection attempts for the live server. Also, my live api credentials authenticate when using https://api.ewaypayments.com/soap.asmx.
It is a new installation of wordpress 3.5.1 and event espresso 3.1.33p.
Thanks in advance!
|
|
Josh
|
June 12, 2013 at 11:57 am
Hi Shaun,
This sort of thing has come up before where live credentials don’t seem to work and a few times it was from an extra leading or trailing white space was accidentally copied and pasted into the API credential fields. Can you check and rule that out?
|
|
Shaun Davis
|
June 12, 2013 at 4:47 pm
I’ve already checked for leading or trailing white spaces. Could it be something to do with the handling of special characters? I’ve tried to make a live key several times and it always has a / character, whereas the sandbox key doesn’t.
|
|
Sidney Harrell
|
June 12, 2013 at 5:38 pm
Can you try changing line 71 of eway_rapid3_vars.php to be:
<p class="error"><?php _e("An error has occured in the using of the Eway Rapid 3.0 payment gateway. Please try a different gateway","event_espresso");?></p>
<?php var_dump($rapid3Response); ?>
|
|
Shaun Davis
|
June 12, 2013 at 8:38 pm
That returns NULL in place of the error.
|
|
Shaun Davis
|
June 12, 2013 at 9:54 pm
Looking a little deeper I’ve managed find the following error when the connection to eway is attempted:
Curl error: SSL: certificate subject name ‘www.eway.com.au’ does not match target host name ‘api.ewaypayments.com’
|
|
Shaun Davis
|
June 13, 2013 at 1:37 am
I’ve fixed this issue with a workaround.I put:
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);
before the line:
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
in EWayRapid3Client.class.php.
|
|
Michael Nelson
|
June 14, 2013 at 10:50 am
I talked to eway support about this, as it sounds like a problem with eway’s SSL certificate.
They said:
Our certificate is a SAN SSL issued to http://www.eway.com.au however with api.ewaypayments.com as one of the SAN’s…. As you can imagine, the majority of our customers connect using cURL in a LAMP environment so we’d expect this to be far more widespread if we’d broken something.
It looks like the SAN issue was fixed from libcURL 7.19.1 so it should be simply a matter of having cURL/libcURL updated on their server – http://daniel.haxx.se/blog/2009/11/04/curl-and-libcurl-7-19-7/
So basically, they believe the error is actually a bug in your version of libcurl, which doesn’t support SAN (Subject Alternative Name). You can run the following code to get your CURL verison (paste it into your theme’s functions.php file temporarily):
var_dump( curl_version (CURLVERSION_NOW));
What version are you running?
|
