CURL Error 28

[astm0652]

Orders that are paid by credit card are not showing in new orders in admin, but PayPal has the order information and not me.

[DrByte]

Orders that are paid by credit card are not showing in new orders in admin, but PayPal has the order information and not me.

That's symptomatic of whatever PHP errors are occurring when submitting the transaction. If PayPal has the details (ie: the payment) but your store does not then it means a PHP fatal error happened after/during the transaction response and the store wasn't able to finish saving the order or sending the emails.

Normally Zen Cart will log fatal PHP errors in the /logs/ directory.
If those logs are indicating CURL problems, you'll probably need to work with your hosting company to sort that out.

[astm0652]

I'm going to check the error the logs. Does this help to solving the problem?

ACK=Failure&L_ERRORCODE0=81002&L_SHORTMESSAGE0=Unspecified%20Method&L_LONGMESSAG E0=Method%20Specified%20is%20not%20Supported&L_SEVERITYCODE0=Error


Thank You DrByte

[DrByte]

I'm going to check the error the logs. Does this help to solving the problem?

ACK=Failure&L_ERRORCODE0=81002&L_SHORTMESSAGE0=Unspecified%20Method&L_LONGMESSAG E0=Method%20Specified%20is%20not%20Supported&L_SEVERITYCODE0=Error

Not really.

81002 is a very generic PayPal error that suggests the request being transmitted is malformed and doesn't make sense to them.
But that would be completely different from a CURL error 28 which means connection timed out, because if it's timed out then it's not getting a response.

[DrByte]

If this happened "out of the blue", (ie: was working and then suddenly isn't) then there are numerous things to check ... because obviously "something" changed.

Between the time when things were "working", and now they're "not" ...
- what software updates has the hosting company installed on the server?
- did they change PHP versions? Apache version? These could have changed default configuration settings in php.ini
- who has had access to your server's control panel?
- have they made any changes to anything, especially PHP/Apache settings?
- who has had FTP or filesystem access to your server?
- have the uploaded/edited anything? Are you sure?

Have you been making regular backups of your server's files and your store database?

It's worth taking a copy of your server's current files and database, and comparing them against a backup from before the problem happened. This can help identify unexpected/unauthorized changes. In short, it's worth proving nothing's been tampered with, by going through these steps until you've verified that nothing unauthorized has happened: https://www.zen-cart.com/wiki/index....ing_From_Hacks

[astm0652]

This is the error i'm getting from my log, hope this helps.

PHP Warning: Illegal string offset 'cost' in /home/pkpoker/public_html/includes/classes/order.php on line 355


Thank You DrByte

[swguy]

This is a mod. There's no such field in vanilla Zen Cart.

[DrByte]

This is a mod. There's no such field in vanilla Zen Cart.

Actually, yes there is. The OP said they're using v1.5.1.

[DrByte]

This is the error i'm getting from my log, hope this helps.

PHP Warning: Illegal string offset 'cost' in /home/pkpoker/public_html/includes/classes/order.php on line 355

in v1.5.1 the line reads:

                        'shipping_cost' => $_SESSION['shipping']['cost'],

in v1.5.7 it's using the following, which you can safely use in v1.5.1 as well:

                        'shipping_cost' => !empty($_SESSION['shipping']['cost']) ? $_SESSION['shipping']['cost'] : 0,

While this isn't technically a "bug", there have been some bugs fixed in various Zen Cart versions associated with mixed ways of representing that $_SESSION['shipping'] array.

If you're going to stay on v1.5.1 then you should also keep watching for all bugs fixed in newer versions and backport them to your old version.

That said, this "PHP Warning" is just a warning. Warnings sometimes do point to underlying issues. I don't think this one is affecting/causing your CURL issues or the issue of orders not completing. I would expect that a "PHP Fatal error" is happening somewhere to cause the issues you were reporting.

[yueli7]

Hi, jumping in here as I also have the same issue since start of July,
Connecting to PayPal Express/Pro Server ... Error 28: Connection timed out after 5000 milliseconds
Connecting to PayPal TLSTest Server ... Error 51: SSL: no alternative certificate subject name matches target host name 'tlstest.paypal.com'

Apart from hosting issues, I'm wondering if this has got anything to do with Paypal's NVP deprecation to REST?