authorize.net test mode failure (GoDaddy hosting problem)

[webmiss]

Hi,

I am using zc 1.3.9h. Installed the authorize.net module, entered the API and Transaction Key, but not the MD5 Hash number. This store is installed on godaddy.com hosting.

Authorize.net account is in test mode and the module is in test mode.

Tried to do a test transaction, using the information in the test module such as sample visa cc #, etc.

Got this message when trying to confirm the purchase:

Communications Error - Please notify webmaster. - Your credit card could not be authorized for this reason. Please correct the information and try again or contact us for further assistance

The log file reveals the following information:

Comm results: 56 Received HTTP code 403 from proxy after CONNECT

Response Code: .
Response Text:

Sending to Authorizenet: Array
(
[x_login] => *******
[x_tran_key] => *******
[x_relay_response] => FALSE
[x_delim_data] => TRUE
[x_delim_char] => |
[x_encap_char] => *
[x_version] => 3.1
[x_type] => AUTH_ONLY
[x_method] => CC
[x_amount] => 144.00
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXX0027
[x_exp_date] => 1211
[x_card_code] => ****
[x_email_customer] => FALSE
[x_email_merchant] => TRUE
[x_cust_id] => 1
[x_invoice_num] => TEST-1-jWaBQj
[x_first_name] => Corinne
[x_last_name] => Collins
[x_company] =>
[x_address] => 3859 Boone Park Ave
[x_city] => Jacksonville
[x_state] => Florida
[x_zip] => 32205
[x_country] => United States
[x_phone] => 904-318-3930
[x_email] => [email protected]
[x_ship_to_first_name] => Corinne
[x_ship_to_last_name] => Collins
[x_ship_to_address] => 3859 Boone Park Ave
[x_ship_to_city] => Jacksonville
[x_ship_to_state] => Florida
[x_ship_to_zip] => 32205
[x_ship_to_country] => United States
[x_description] => Basic Home Service Plan (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => 98.82.82.25
[x_po_num] => Jun-29-2011 12:43:14
[x_freight] => 0.00
[x_tax_exempt] => FALSE
[x_tax] => 0.00
[x_duty] => 0
[x_allow_partial_Auth] => FALSE
[Date] => June 29, 2011, 12:43 pm
[IP] => 98.82.82.25
[Session] => 71261c23f631ededf7ab4ab3ca464738
[x_test_request] => TRUE
[url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array
(
[0] => Response from gateway
[1] =>
[Expected-MD5-Hash] => F0CABE934D0DC5EE56DF50618B8A3EEC
[HashMatchStatus] => FAIL
)


CURL communication info: Array
(
[url] => https://secure.authorize.net/gateway/transact.dll
[content_type] =>
[http_code] => 0
[header_size] => 0
[request_size] => 107
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0
[namelookup_time] => 0.020938
[connect_time] => 0.02188
[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
)

Using CURL Proxy: [proxy.shr.secureserver.net:3128] with Proxy Tunnel: On

RAW data received:

It looks like the MD5 Hash failed if I am reading this right. Should I have created one?

Or is there another problem I am not seeing?

Any and all help will be greatly appreciated.

Thanks,

Corinne

[DrByte]

Comm results: 56 Received HTTP code 403 from proxy after CONNECT

Using CURL Proxy: [proxy.shr.secureserver.net:3128] with Proxy Tunnel: On

The problem is that you're using GoDaddy for your hosting.
They constantly screw things up.
I strongly suggest finding a more reliable host whenever you can.

In the meantime, go to Admin->Configuration->My Store->CURL Proxy Status and turn it off.
Zen Cart has that off by default. GoDaddy turns it on because they used to require it due to weird server configurations, which they removed a couple years ago but they STILL turn that switch on anyway, thus causing all their customers to come here asking for support on a problem they've created.
Please tell them they're causing problems. They don't seem to listen to us.

[webmiss]

Dr. Byte,

I do appreciate your response and am aware of godaddy hosting issues, but my client insisted on using godaddy as a host. I tried to persuade him otherwise before he signed up. Some clients, just do not listen.

I just turned the CURL Proxy Status off and ran a test again. It worked.

Thanks so much,

Corinne