Hello Linkpoint API Module Crew,
I am having a problem when clicking "Submit Order" on the "Review order" page, e.g. https://www.domain.com/cart/checkout/review , the form submit hangs for a while then I get these error messages on a blank white page:
Warning: MySQL server has gone away
couldn't connect to host
Credit card declined: $0.50
Payment failed: Credit card payment declined: Sorry - Could not connect to payment gateway.
I assume SSL is working fine since https://www.domain.com/cart/checkout/review works ok.
I checked to see what my absolute path was and if curl is enabled using the following php code and received the output below:
$_SERVER['DOCUMENT_ROOT']
output: /home/account_name/public_html
var_dump(curl_version())
output: libcurl/7.18.2 OpenSSL/0.9.7a zlib/1.2.1.2 libidn/0.5.6
My settings at store/settings/payment/edit/gateways for the Linkpoint API are:
Store Number: xxxxxxxxxx (10 digits)
PEM File: /home/account_name/public_html/modules/ubercart/payment/uc_linkpoint_api/xxxxxxxxxx.pem
Transaction mode: Production
Transaction Type: Sale
I noticed that Linkpoint also gave me a 6 digit user id that is the same as the last 6 digits in the 10 digit store number. Should I be using the 6 digits instead of the 10 digits for the Store Number field?
Also, I noticed that when I first extracted the module into the /home/account_name/public_html/modules/ubercart/payment/uc_linkpoint_api directory, there is an 000000.pem.txt file in there with the instructions: "Delete all text within this file, then copy and paste your key from Linkpoint API here. Do not leave any whitespaces or returns at the end of the file. Then rename this file to your store id, 6 digits, with .pem as the file extension."
However, when I download my PEM file from Linkpoint, the file is named xxxxxxxxxx.pem (10 digits) and it has a trailing line break on the end of the file.
I have tried using the 6 digit user id as my store number, switching to the xxxxxx.pem (6 digit version with no trailing line break and no white space), switched between production and test modes, and still receive the same errors that I listed above.
Has anyone ran into a similar problem, or know of anything to fix this problem? Thanks!