With a new 4.5.0 store going up, I tried again to get a live transaction thru X-Payments using Payflow Pro, and got the following error message in X-Payments at var/log/payment/2012-05-27/errors.0001.log:
ERROR [2012-27-05 23:42:36]
User: unknown; IP: [my home IP]
Code: CURL_EXEC_ERROR (216)
CURL library: error while sending the request to remote server "https://payflowpro.verisign.com/transaction". Error: "#7: couldn't connect to host"
Affected systems: Core/Bouncer.php file (180:assert); Core/Bouncer.php file (295:getResponse); Model/PaymentConf.php file (856:sendRequest); Model/PaymentConf.php file (822:processSecure3dBuiltIn); Controller/Payment/Main.php file (282:processSecure3d); Controller/Payment/Main.php file (213:doSecure3d); Core/Controller.php file (181:actionPay); Controller/Payment.php file (277:process); Core/Dispatcher.php file (148:process); Application.php file (156:dispatch); /home/xp/public_html/xpayments/payment.php file (26:run)
I sent a trouble ticket to my host (HostGator) to see what they would say about my error message. Here is the reply:
I don't know what to think, except that maybe I need to start looking for another gateway. We've been with Payflow Pro for over 10 years and have a package deal we don't want to give up.
Is anyone using Payflow Pro successfully using X-Payments? Anyone using Hostgator also? Does your config file look similar to mine (post 4 above). I'm using our servers shared secure server. Does that matter?