Linkpoint API (We apologize for the inconvenience, but...)

[rompalicious]

Hello:

I am currently unable to process orders using a linkppoint API module that has been functioning properly for months.

I (and everyone else attempting to purchase with a CC# at rompalicious) am receiving the following error:

"We apologize for the inconvenience, but we are presently unable to contact the Credit Card company for authorization. Please contact the Store Owner for payment alternatives."

After searching elsewhere in the forums I have had a few conversations with the host (JSweb) and we have evaluated Dr. Byte's advice from a similar (older) thread:

- port 1129 not open for bidirectional communication
- CURL access requires a proxy server configuration
- CURL is not installed or not functioning
- incorrect or invalid or "no" .PEM file found in modules/payment/linkpoint_api folder

These do not seem to be the problem (e.g. port is forwarded, etc.).

Again, nothing has changed that I am aware of but it just stopped working within the last 24 hours.

Any thoughts/suggestions/advice?

Thank you.

[kobra]

There is a debug tool/module that will create entries in a log so you can determine precisely what is not happening...
Could be that LP is having issues

[rompalicious]

Here's the results from the Debug file. Doesn't look terribly specific to me. Any insight?

"Apr-20-2009 07:50:26
=================================

Communication Result: 7 - couldn't connect to host

Response Code: <

Sending to Gateway:
result = LIVE
oid = 676-h5HGbb
ip = 68.189.137.166
ponumber =
subtotal = 1
tax = 0.07
shipping = 0
chargetotal = 1.07
cardnumber = ******
cardexpmonth = 09
cardexpyear = 11
cvmindicator = provided
cvmvalue = ******
userid = 2
customerid = 2
name = <edited out>
company =
address1 = <edited out>
address2 =
city = <edited out>
state = <edited out>
country = US
phone = <edited out>
email = <edited out>
addrnum = <edited out>
zip = <edited out>
sname = <edited out>
saddress1 = <edited out>
saddress2 =
scity = <edited out>
sstate = <edited out>
szip = <edited out>
scountry = US
comments = Website Order
items = Array
(
[1] => Array
(
[id] => 1583
[description] => 2.5 Liter/4 Cyl Engine Parts - Part 1 (Crown OE, CJ, YJ, TJ)
[quantity] => 1
[price] => 1.00
)

)

ordertype = PREAUTH
host = secure.linkpt.net
port = 1129
keyfile = <edited out>/includes/modules/payment/linkpoint_api/<edited out>.pem
configfile = <edited out>
transactionorigin = ECI
terminaltype = UNSPECIFIED


Result: proved>FAILURE</r_approved><r_error>Could not connect.</r_error>

Communication Result: 7 - couldn't connect to host
CURL info: Array
(
[url] => https://secure.linkpt.net:1129/LSGSXML
[http_code] => 0
[header_size] => 0
[request_size] => 0
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0
[namelookup_time] => 5.1E-5
[connect_time] => 0
[pretransfer_time] => 0
[size_upload] => 0
[size_download] => 0
[speed_download] => 0
[speed_upload] => 0
[download_content_length] => 0
[upload_content_length] => 0
[starttransfer_time] => 0
[redirect_time] => 0
)

"

[rompalicious]

Oh... and thank you very much for your help. It is very much appreciated!

[kobra]

Communication Result: 7 - couldn't connect to host

Response Code: <

Sending to Gateway:
result = LIVE
oid = 676-h5HGbb
ip = 68.189.137.166

Try pinging that IP - I suspect that this is the LP IP address
Would call them if that is the case

[DrByte]

The IP kobra mentioned is very unlikely to be the issue (It's the customer's IP, not Linkpoint's).
However, he's right that the communications going to Linkpoint is broken.

Communication Result: 7 - couldn't connect to host

host = secure.linkpt.net
port = 1129

Communication Result: 7 - couldn't connect to host
(
[url] => https://secure.linkpt.net:1129/LSGSXML
)

The real problem is that your server can't talk to the Linkpoint server. Usually that's because your hosting company's server isn't allowing you to successfully connect to the linkpoint server. That could be a port 1129 block or other firewall misconfiguration, or a DNS misconfiguration which prevents server-name lookups from working properly. Your hosting company will have to fix those problems.

Alternatively, Linkpoint's servers might not be responding. You'll have to follow up with *them* about that angle.

[rompalicious]

Well... having spoken to LP, they provided me with the correct address for the linkpoint module (secure.linkpt.net) which was already set correctly within the module (as expected since it's been working perfectly for a long time). We (LP and I) also tried using the direct LP IP address to bypass potential DNS problems but received the very same result when a transaction was tried...

LP did mention that they moved servers around over the weekend but don''t see why that would be an issue. Also tried looking up the host's IP address (as provided to me by them) to see if it was blacklisted suddenly anywhere and it looks clean at all the blacklist aggregates I've tried.

[eflat]

Linkpoint is down. Actually, tech support said it was "sporadic", which mathces their Gateway Status Page. Something about a platform change they attempted. No announced eta from level 2. Big FAIL.

[rompalicious]

Yes. It does appear that the issue is LP connection problems due to the server move over the weekend. At least according to them and my host.

Apparently, they are still wading through over 300 support tickets with no ETA on a fix in sight...

Very disappointing. Epic FAIL.

Thankfully, most of my customers seem willing to go the PayPal IPN route for the time being.

[gchalk]

Linkpoint is down. Actually, tech support said it was "sporadic", which mathces their Gateway Status Page. Something about a platform change they attempted. No announced eta from level 2. Big FAIL.

I'm having the same trouble, starting sometimes yesterday linkpoint started failing to connect to the gateway.

I called my webhost and they claim not to have touched the firewall/router settings.

I just got off the phone with link-point and what i found out is that over the weekend, they chaged the IP address of the gateway. The new gateway IP address is 208.72.248.102.

The IP address listed in the log file is your customers IP address.

I'm working with my webhost, but what I think has happened, is the pinholes they put in their firewall/router port forwarding setup for me is IP based, not hostname based and they will have to go in an setup the new linkpoint IP address to make it work.

This is my first guess.....I will advise of any success