CURL problem

[jennya]

Hello,
We are now using LinkPoint API for our cart. To test the cart (with a real cc number)I tried to submit the credit card number for payment, but received the following message:
"We're sorry, but our payment processor has returned an error, and cannot process this transaction.

Specific error returned: Could not execute curl

Please try this transaction later. If this problem persists, please email us, and we will assist you"

How should I proceed from here? Is a problem with my host?

thanks,
Jenny

[jennya]

Hello,
We are now using LinkPoint API for our cart. To test the cart (with a real cc number)I tried to submit the credit card number for payment, but received the following message:
"We're sorry, but our payment processor has returned an error, and cannot process this transaction.

Specific error returned: Could not execute curl

Please try this transaction later. If this problem persists, please email us, and we will assist you"

How should I proceed from here? Is a problem with my host?

thanks,
Jenny

Hi again,
I asked my host about this issue. They said it "looks like your software cannot find the 'curl' executable. The path to curl on our systems is /usr/bin/curl."

If this is the case, where can I edit the CURL path?

Our server info:
OS Linux
Kernel Version 2.4.21
Apache Version 1.3.28 (Unix)
PHP Version: 4.3.3
MySQL Version: 4.0.15-standard
CURL Version: libcurl/7.10.5 OpenSSL/0.9.6b zlib/1.1.4


thank you!
Jennya

[Jamie]

Hi Jenny,

I don't think that is the problem. Squirrelcart just uses the built in PHP curl functions. It does not specify the path to CURL, as PHP should know where it is.

The problem may be with your linkpoint payment gateway file (squirrelcart/payment_gateways/linkpoint.php).

What version of Squirrelcart are you running? I believe the linkpoint file was updated to fix a similar problem in v1.3.0.

Thanks,
Jamie

[jennya]

Hi Jenny,

I don't think that is the problem. Squirrelcart just uses the built in PHP curl functions. It does not specify the path to CURL, as PHP should know where it is.

The problem may be with your linkpoint payment gateway file (squirrelcart/payment_gateways/linkpoint.php).

What version of Squirrelcart are you running? I believe the linkpoint file was updated to fix a similar problem in v1.3.0.

Thanks,
Jamie

Hi Jamie,
We are using cart version v1.3.1. I upgraded yesterday before trying to enable the linkpoint api.

Thanks for your reply.

Jenny

[Jamie]

OK. That rules an old linkpoint file out then. We will need a helpdesk ticket for this. Please include FTP and cart login info in the ticket.

Thanks,
Jamie

[jennya]

OK. That rules an old linkpoint file out then. We will need a helpdesk ticket for this. Please include FTP and cart login info in the ticket.

Thanks,
Jamie

Thanks, Jamie. I will do that.

[jennya]

Hey Jamie,
I opened up the Help Desk ticket on Wednesday as you suggested. Any ideas on this yet?

Thanks,
Jenny

[Jamie]

Hi Jenny,

Nothing yet. We are going to incorporate the new LinkPoint API and see if it fixes the problem.

Thanks,
Jamie

[jennya]

Hi Jenny,

Nothing yet. We are going to incorporate the new LinkPoint API and see if it fixes the problem.

Thanks,
Jamie

Thanks, Jamie.
If this doesn't work, I will try LinkPoint Basic (now called LinkPoint Connect).

I appreciate your help,
Jenny

[jennya]

Thanks, Jamie.
If this doesn't work, I will try LinkPoint Basic (now called LinkPoint Connect).

I appreciate your help,
Jenny

Hi Jamie,
Our cart has been down for 4 days now so I am going to go ahead and try to just use LinkPoint Basic for now. Our year of support & updates ends on 12/18/03. If you do not have the LinkPoint API update out before the 18th can we still download that update?

Thank you,
Jenny

[Rich]

Hi Jamie,
Our cart has been down for 4 days now so I am going to go ahead and try to just use LinkPoint Basic for now. Our year of support & updates ends on 12/18/03. If you do not have the LinkPoint API update out before the 18th can we still download that update?

Thank you,
JennyHi Jenny,

Jamie is working on the LinkPoint issue. Regardless of your support status when the update is complete, we'll make sure you get the file(s).

Regards,
Rich

[royc]

I am getting the same error on a cart running 1.5.4

Specific error returned: Could not execute curl.

Do you have a fix or is this a server problem with CURL?

thnx

[royc]

sorry to bother you

[rikym]

I have the same problem but it looks intermittant. I had it working this morning and then all of a sudden the server started not getting responses back from my ECHO gateway.

The last post mention the PEM file. What is the PEM file and how should it be named correctly?

Thanks!

[royc]

The PEM file is an encrypted key file that sends data between the gateway and squirrelcart. In my case it is used in linkpoint. Linkpoint sends a block of text that is a security key. much like "einf93y64tytagwr8iyerqwe". When a transaction is sent, it checks the key for security purposes. Within squirrelcart you set the name and location of the PEM file. In my case I didn't name my file right, so the transactions weren't going through. I don't believe that ECHO uses a PEM file.

[azeerent]

I have the Curl error on checkout as well. I have verified openssl and curl are functioning... am using yourpay api which is same as linkpoint api from what I am told. What direction should I be looking?

[Jamie]

Hi Azeerent,

First, so we understand each other, make sure you read through the setup instructions for LinkPoint on it's record in the admin interface.

I have verified openssl and curl are functioning
Did you do this by testing the secure (2nd) link on the /squirrelcart/diag_curl.php page? If so, then CURL is probably fine, and you are most likely receiving the "could not execute curl" error. That error message comes form LinkPoint's code, and is very deceiving. This most likely indicates one of the following:

1. You are missing your .pem file
2. You did not name the .pem file correctly (should be named XXXXXXX.pem, were XXXXXXX is your storename. Your "storename" is usually actually a number provided by Yourpay/Linkpoint.
3. There are extra lines, extra characters, or missing characters in your .pem file. The contents should look something like this example:
-----BEGIN RSA PRIVATE KEY-----
MIIeXamPlegIBAAKBgQDWbPgN/yHXuWTg3NeXaMPLe3oHT4yKASWMjjnpZ6L9CEX
aU894JdYexaMPlecmK5WYZKFMExtON7vgTqlNtnC4llgqBZkjd 8i333gu3CxbZgo
AqImswg7ewkJ4/CosbW1vAytMREXAMpLEaZvP+Wp4gIj3yXvR0hHRmJs/Xlf5RiI
AoGAYoIVQ3jed1i4u4U8fRJSLICt+sJ/2gwAVpOFUDL/Mcl6sC5jIj7fqquKDC0v
Pvj9Y4ApCyb3ZkdYq2uJXBpcjmZHMReBiEJThLklNXT+EzAm/wy/MCsf0H/R2/36
fV4qi3eAQs0Vreorh1Iw688M2KCvbQyT4nxZpkqNpsSShQECQQ DsOTC0y9SU1RCq
R0dMA7dhzgYkosESPEfC8klHbbZprqRn7d+3ZvKoefvPjMRFmG DzyKiBoQe12fj3
tH1sIsANeXampleZtwn5jZhAkEA6GGaZU7W9X+CUUuE87Pii/mlK1aXo/nA4BSfC
T0HUQydnFBRjpDND02//0ztTWFz2EswfAwJBAKEg9X8tVejbWM29Zv2Lv2egX4JX
3fhxU8W+/IsTZAy8Snp1wFbaiwSuiDvvWeXa5a8EHSSm0ZqSfwdKiztQBaE CQQCY
B+PblgojEeozv8HbI3x7cbgzM3MAj/01XahzL1Ru6QiAG195UVezNPeXaMPlEyGd
owCkC6mHDFBKBn/j6nH7AkEAx6n4XIKQYOdhGS5K3JSAVhqc7+HnXuc+d68Xk7af
YexaMpLECLSE1o5koPmKajtCzNkg58Jh15B6L9MNv3OBqJqqgL A==
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
MIICYjCCAcugAwIBAgIBADANBgkqhkiG9w0BAQQFADB3MQswCQ YDVQQIEwJSSTEQ
MA4GA1UEBxMHV2Fyd2ljazEfMB0GA1UEChMWTGlnaHRob3VzZS BEZXZlbG9wbWVu
dDEWMBQGA1UEAxMNSmFtaWUgV2hpdG5leTEdMBsGCSqGSIb3DQ EJARYOc2FsZXNA
bGRldi5jb20wHhcNMDUwNDEyMTYwNTA0WhcNMzUwNDEwMTYwNT A0WjB3MQswCQYD
VQQIEwJSSTEQMA4GA1UEBxMHV2Fyd2ljazEfMB0GA1UEChMWTG lnaHRob3VzZSBE
ZXZlbG9wbWVudDEWMBQGA1UEAxMNSmFtaWUgV2hpdG5leTEdMB sGCSqGSIb3DQEJ
ARYOc2FsZXNAbGRldi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY 0AMIGJAoGBANZs
AqImswg7ewkJ4/CosbW1vAytMREXAMpLEaZvP+Wp4gIj3yXvR0hHRmJs/Xlf5RiI
AoGAYoIVQ3jed1i4u4U8fRJSLICt+sJ/2gwAVpOFUDL/Mcl6sC5jIj7fqquKDC0v
Pvj9Y4ApCyb3ZkdYq2uJXBpcjmZHMReBiEJThLklNXT+EzAm/wy/MCsf0H/R2/36
BQADgYEAoG3Qh4+ZafUCLfmK9GqOQ5aGVp2jYJoeqhcxsPg/uADm5xP05YqTUr5x
CWBISSTEnym2mvnKqumSxVByHoEMKSU0JZCvJ+Mztwwd7vXjmQ 7BxKu8dbm6Oxjh
wdDYrt3FP+Z/sHnYZT9yTKjnlAFuF2XhuFUwNhEtz0bCmjjoE/s=
-----END CERTIFICATE-----

The code block above shows an extra line after "END CERTIFICATE"...this should not be there. I can't get rid of it in this post. Emphasis here is that the very last line should read "-----END CERTIFICATE-----"

If none of this helps, please open a helpdesk ticket and we would be glad to check it out for you.