curl connection test error on setup (invalid address)

reply from my server admins:

I have looked into the issue and one thing I am now sure of is that this issue is not related to the Lunarpages server itself. It appears that ZenCart when running its self-diagnostic is attempting to use CURL to open a connection to 64.202.165.130:3128 - The reason it fails is because 64.202.165.130 is not responding. It's not an issue with our server; in fact the IP address does not respond from any location I tested from. From what I could ascertain it was at one point a GoDaddy proxy address, however at this time it does not respond to any proxy requests. I would recommend ignoring the error and attempting to install anyway. If that doesn't work, you might try locating the setting that controls what IP address is used as the proxy or in the self-diagnostic and changing that to a valid IP address. If you have any questions or further issues regarding this matter please let us know.

error:

# CURL problems detected: 28 => connect() timed out! more info...
# CURL requires SSL support. Please notify webmaster or hosting company. 7 => couldn't connect to host more info...
# CURL problems detected: 28 => connect() timed out! more info...
# CURL requires SSL support. Please notify webmaster or hosting company. 7 => couldn't connect to host more info..

The installer does a test for CURL availability as part of its pre-flight install checks.

1. It tries to connect over CURL to http://www.zen-cart.com
2. Then it tries over SSL to https://www.zen-cart.com (because many servers have been found to work okay without SSL, but break when trying to do secure communications over SSL ... hence the need to test it)
3. IF THE TEST #1 ABOVE FAILS, then it tries the (now obsolete) GoDaddy proxy server .... because a couple years ago before GoDaddy finally smartened up and dumped the need for a proxy server to use CURL, this was the only way to test that.
4. IF THE TEST #2 ABOVE FAILS, it attempts, again, the GoDaddy CURL proxy, but over SSL.

So ... you can go back to your host and tell them that there would be no attempts to go to the GoDaddy address if their server was allowing the first 2 CURL tests to work properly. Most likely they have a firewall rule blocking the outbound communications over CURL.

(FYI, the tests against the GoDaddy proxy are removed in the upcoming v1.3.9 and subsequent versions. But that's irrelevant to your particular situation.)

ok thanks