Communications Error following a "Security Hash Error" Fix

[DrByte]

If all the info in the CURL Communcation section comes back as mostly 0, then your problem is with your server's ability to talk to the authnet server properly. The "http_code" value needs to be 200. If it's not, then there's a communication problem (either authnet's server isn't responding or *your* server can't connect to it).
Fixing that will fix your Hash problem.

[ssjenson]

Thanks. I am passing along this information but my web host still believes the issue is on my end. Any verbage I can use to tell them what to do?

Thanks!

[DrByte]

What results do you get when using the curltest.php tool discussed here: http://www.zen-cart.com/forum/showpo...2&postcount=13
(use the ?authnet=1 parameter)

(If you're using Zen Cart v1.3.8a then curltest.php will already be in your /extras/ folder, so saves you a step.)

[ssjenson]

results from curltest.php & ?ssl=1 were "Data validation Good"
result from ?paypal=1 was an array of numbers
result from ?authnet=1 was an array of zeros...

I am beginning to think the problem is with authorize.net. Read a tweet about 7 hours ago that said authorize.net may be having DNS issues causing storefront payment processing issues. I can't find anything else to support this but I also can't figure out what my "out of the clear blue sky" problem would be. Frustrating that authorize.net doesn't have 24 hour support...

Where now Doc?

[dirtypants]

results from curltest.php & ?ssl=1 were "Data validation Good"
result from ?paypal=1 was an array of numbers
result from ?authnet=1 was an array of zeros...

I am beginning to think the problem is with authorize.net. Read a tweet about 7 hours ago that said authorize.net may be having DNS issues causing storefront payment processing issues. I can't find anything else to support this but I also can't figure out what my "out of the clear blue sky" problem would be. Frustrating that authorize.net doesn't have 24 hour support...

I'm dealing with the same thing totally out of the blue, too. No clue. I'm also pretty outraged about the lack of support, because it seems squarely an Authorize.Net problem. No problems with any other payment modules.

Even Authorize.net is timing out from my pings at times, and sometimes giving me a "Destination net unreachable" error. Totally timing out to secure.authorize.net....



Here is my curltest result. Looks like Authorize.net to me....


6 name lookup timed out

Array
(
[url] => "https://secure.authorize.net/gateway/transact.dll"
[http_code] => 0
[header_size] => 0
[request_size] => 0
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0
[namelookup_time] => 0
[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
)



EOF

[ssjenson]

The only means of communication I have found with authorize.net is through twitter. I don't know if you have an account but it is quick to create and there are a few of us sending tweets about this, hoping to raise their awareness. They have live responses to the Tweets so someone is listening but still not getting it.

[ssjenson]

Authorize.net sent me tweet saying they had a problem with Internap which provides their connectivity and they have fixed it. I am still having communications issues...anyone else?