Can't get a Linkpoint connection on cloned server

I'm currently running ZC 1.3.6 on arc-zone.com with no issues. I have built a new server, which is a clone of the live server, running on arc-zone.info (closed to the public) that runs concurrently with the live server. Basically we just wanted to upgrade the hardware and the OS and have a place to test before going live.

Anyway, Zen Cart (same version) functions fine on the new server except that Linkpoint transactions don't go through. I can get shipping estimates. It forwards transactions to Paypal without incident. But the message onscreen from Zen Cart after I hit "confirm" in step 3 is: "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." This happens in testing or live mode.

FYI: I have port 1129 open, the pem file is exactly where it was (same file) on the live server, using the same store id and curl is working. And the server can connect to any other site on the internet (it's not a general connectivity issue).

When I run the curltest script with the linkpoint option this is what comes back:

7 Failed to connect to 208.72.248.102: Permission denied
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] => 0.006236
[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
)

Obviously, it's not getting an HTTP response which is bad. I'm thinking either it's being rejected because my IP is different than the live server or there are two active, duplicate pem files.

Any ideas?

openvista:

7 Failed to connect to xxxxxxx: Permission denied
Error #7 means "failed to connect"
"Permission denied" seems to be the "cause" of the #7 error, and thus appears to be the issue you need to sort out.

I suspect it's a restriction in your server's SELinux configuration:

• • http://www.lightenna.com/news/tech_report/selinux_will_mess_with_your_curl
• • http://lists.ofbiz.org/pipermail/users/2006-February/010058.html
• • http://forum.nusphere.com/viewtopic.php?t=3748#19129 (last 2 posts)

Sure enough. Gosh, I should have thought of that. As soon as I disabled SELinux, the curl test went right through. Now, I've just got to figure out how to make a policy for it in SEL because I don't like leaving it disabled.

Thanks for the help, though!!

The first link I posted above gives an idea of a setting to adjust in SELinux config: > By default 'Allow HTTPD scripts and modules to connect to the network' is unticked in 'system-config-securitylevel' ('SELinux' tab). Relaxing this security restriction solved the problem.

Actually, for me, using CentOS 5.4, I don't have the option mentioned in my system config network tui. He's using Fedora. I had to manually enter the following command: "setsebool -P httpd_can_network_connect=1" which accomplishes the same thing. Again, thanks for your help!!