On Checkout, message displayed: "(28) connect() timed out!" Checkout fails

I'm getting inconsistent errors. Started off occasionally getting them, but the frequency now is now much closer to constant.

It's affecting checkout with PayPal and also rate lookup with CEON Advanced Shipper module, so requests to web services is timing out?

I see others have gotten this in the past. I'm haven't seen any solutions posted to this. Anybody familiar with the cause of this?

http://www.zen-cart.com/showthread.php?195025-Paypal-has-stopped-working

Been running the same version of Zen Cart for at least a year, but the problem has cropped up without any changes being applied to zen-cart.

Here is the output of running /extras/ipncheck.php.

IPNCHECK.PHP - Version 1.3.9

CURL ERROR: Attempted connection on: https://www.paypal.com/cgi-bin/webscr

(28) connect() timed out!

Trying direct HTTP on port 80 instead ...

CURL RESPONSE RECEIVED - Communications OKAY
IPN TESTING - Response Received via CURL -- COMMUNICATIONS OKAY

IPN TESTING - Confirmation/Validation response with fsockopen(): FSOCKOPEN() RESPONSE RECEIVED - Communications OKAY

Default method likely to be used for communications is: CURL, with the fallback method being FSOCKOPEN if possible.

Script finished.

Actually the first time I ran it, it looked OK without the errors. I ran it again, and got this error. It's the same error my customers are seeing when they try to check out.

My host (1and1.com) looked into it, duplicated the problem, but they are telling me that their server is fine and that I should be looking for a solution with Zen Cart. They referred me back to this forum. Though I do think the problem is on their end.

Anybody have any thoughts about resolving this? I'm contemplating moving my zen-cart store to another host to see if that resolves the issue.

Search this forum for "1and1.com" and see that they are not conducive to ecommerce/ZenCart

Might try a different host

After posting this, ran the ipncheck.php again, and got different results, more errors:

IPNCHECK.PHP - Version 1.3.9

CURL RESPONSE RECEIVED - Communications OKAY
IPN TESTING - Response Received via CURL -- COMMUNICATIONS OKAY

Warning: fsockopen() [function.fsockopen]: unable to connect to ssl://www.paypal.com:443 (Connection timed out) in /homepages/36/.../zen/extras/ipncheck.php on line 128

IPN ERROR :: Could not establish fsockopen:

Host Details = ssl://www.paypal.com:443 (110) Connection timed out

Trying again with HTTPS over 443 ...

Warning: fsockopen() [function.fsockopen]: unable to connect to https://www.paypal.com:443 (Unable to find the socket transport "https" - did you forget to enable it when you configured PHP?) in /homepages/.../zen/extras/ipncheck.php on line 134

IPN ERROR :: Could not establish fsockopen:

Host Details = https://www.paypal.com:443 (2142582588) Unable to find the socket transport "https" - did you forget to enable it when you configured PHP?

Trying again directly over 443 ...

Warning: implode() [function.implode]: Invalid arguments passed in /homepages/.../zen/extras/ipncheck.php on line 177

IPN TESTING - Confirmation/Validation response with fsockopen(): FAILED

Default method likely to be used for communications is: CURL, with the fallback method being FSOCKOPEN if possible.

Script finished.

kobra:

Search this forum for "1and1.com" and see that they are not conducive to ecommerce/ZenCart

Might try a different host

Ya, the plan is to get off of 1and1. I'm working on that this week. I am just trying to keep zen-cart alive on 1and1 for the rest of the week at least. ;-)

Anyway, was working OK for a few years, until this month then the problem cropped up once or twice earlier in the month, but has built up to become a big disaster for business.

Sounds like the server hasn't been configured correctly to use SSL. Port 443 is SSL, which is https.
And to communicate to outside resources using SSL it is necessary for the webserver to have OpenSSL (or equivalent) compiled into PHP.

So, based on your posts it sounds like your hosting company recently changed the PHP configuration (maybe upgraded PHP?) and neglected to include OpenSSL support in the process. A pretty big mistake in this day.

It looks like OpenSSL is enabled when I pull up the Server Info

Registered Stream Socket Transports tcp, udp, unix, udg, ssl, sslv3, sslv2, tls

openssl
OpenSSL support enabled
OpenSSL Version OpenSSL 0.9.8o 01 Jun 2010

cURL support enabled
cURL Information libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.15 libssh2/1.2.6

Fine. So maybe it's installed. But it's not working.

At least not according to the test output you posted earlier. That shows that all attempts to access https URLs are failing with a timeout.

Your host will need to fix their problem. This is not something you can fix.

I just discovered curltest.php.

Both of these seem to work well:

https://store.brickovenbaker.com/extras/curltester.php
https://store.brickovenbaker.com/extras/curltester.php?ssl=1

This test, (28) timed out...

https://store.brickovenbaker.com/extras/curltester.php?paypal=1

Who's your hosting company? It's definitely their problem.

Someone last week posted about having the very same symptoms, specifically when accessing PayPal ... and they're hosted with FastHosts.

It was determined to be a problem with Fasthosts network/firewall.

It's on 1and1.com (I mentioned that above, but realize I buried it in the details.)

Sorry, I missed that detail while reading tons of posts.

Regardless, it's a hosting issue. They'll need to fix it for you.

DrByte:

Sorry, I missed that detail while reading tons of posts.

Regardless, it's a hosting issue. They'll need to fix it for you.

It was my fault. I buried it. I wasn't trying to be snarky. I appreciate your thoughts on the issue.

Giving them the output of the ipncheck script should arm them with more than enough info for them to investigate and fix quickly. They can even look at the code in that file (it's a standalone script, with no dependencies on any other files being present) and use it to do their own tests in an account that doesn't affect your live site.