Suddenly getting Security Hash Problem AND Communications Error

[Oriontool]

When the guy from HostGator goes to http://www.earphoneguy.com/curltest.php?paypal=1 it works. So it is letting some SSL transactions work.

I am totally confused now.

[DrByte]

When the guy from HostGator goes to http://www.earphoneguy.com/curltest.php?paypal=1 it works. So it is letting some SSL transactions work.

I am totally confused now.

... and that's further proof that there's something amuck between your server and authorize.net's server ... possibly your server's firewall is blocking access ... or perhaps authorize.net is blocking you.

You *could* contact your authorize.net representative or their tech support and ask them to confirm whether your server's IP address is blocked by them or not, and why.

[Oriontool]

... and that's further proof that there's something amuck between your server and authorize.net's server ... possibly your server's firewall is blocking access ... or perhaps authorize.net is blocking you.

You *could* contact your authorize.net representative or their tech support and ask them to confirm whether your server's IP address is blocked by them or not, and why.

That's kinda what I was thinking. If I still can't get anywhere with these guys tonight, I will call A-net tomorrow morning and ask about my IP being blocked on their end.

[DrByte]

the server is running PHP 5.2.13 - which is a really uncommon version that was only stable for a short time from what I can tell.

Do you think it could have anything to do with the php version as I have stated in the post a few up from here?

Unlikely to be an issue. Esp since there's confirmation that CURL can talk to other servers fine.
It appears the blockage is specific to authorize.net.

Also, we were able to get the authorize.net to work using the SIM module - not offsite - but onsite.

What I am not sure of is this - is the SIM module as secure and / or PCI compliant as the AIM module for authorize.net? So... is there a reason not to use the onsite version of SIM?

Also... is he ok to be running it as SIM? Because it works fine that way.

SIM in onsite mode is still collecting CC information directly on your site. In the strictest sense that may not be PCI compliant. That's up to you and your scanning company to decide.
At the very least you need to have SSL enabled if you're going to do that.
Running it in offsite mode is less customer-friendly but doesn't collect CC details directly on your site. Some say that using that method shifts the blame away from you if something bad were to happen.
Again, that's up to you and your PCI company to decide.

SIM is certainly less efficient than AIM. So if you intend to do onsite-collection of card details, AIM is definitely strongly recommended.

[Oriontool]

I'm fixed!

Apparently after being on with a higher tier tech, there was an issue with HostGators Nameservers something or another. Anyway, it was ALL HostGator! Thanks for the help Dr. Byte!

Do you offer a place to donate a few bucks?

[DrByte]

I'm fixed!

Yay!

Do you offer a place to donate a few bucks?

Sure: www.zen-cart.com/donate

[stellarweb]

Thanks for all your help and info about the difference between SIM and AIM Dr. Byte! You are MUCH appreciated!