authorize.net AIM problem with GoDaddy ...

[Hell Guapo]

1.3.9h GoDaddy host and SSL in Testing Mode using Automatic Approval Credit Card Numbers

I've seen a few threads regarding this type of problem but none seem to solve my problem.

When I press CONFIRM ORDER I get the error:
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.


I put the payment module in Debug mode and the log I received said this: ("######" symbols replace personal information)

Nov-02-2011 02:19:06
=================================

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] => 6.95
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXX0027
[x_exp_date] => 1211
[x_card_code] => ****
[x_email_customer] => TRUE
[x_email_merchant] => TRUE
[x_cust_id] => 2
[x_invoice_num] => TEST-1-tQRwwK
[x_first_name] => ######
[x_last_name] => ######
[x_company] => ######
[x_address] => ######
[x_city] => ######
[x_state] => ######
[x_zip] => ######
[x_country] => United States
[x_phone] => ######
[x_email] => ######
[x_ship_to_first_name] => ######
[x_ship_to_last_name] => ######
[x_ship_to_address] => ######
[x_ship_to_city] => ######
[x_ship_to_state] => ######
[x_ship_to_zip] => ######
[x_ship_to_country] => United States
[x_description] => test fake mask (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => ######
[x_po_num] => Nov-02-2011 02:19:06
[x_freight] => 5.95
[x_tax_exempt] => FALSE
[x_tax] => 0.00
[x_duty] => 0
[x_allow_partial_Auth] => FALSE
[Date] => November 2, 2011, 2:19 pm
[IP] => 67.162.99.172
[Session] => c5rtgbr23id83uejuid0g30kd3
[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] => #######################
[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.019653
[connect_time] => 0.020413
[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:

The above log means nothing to me as far as ME being able to identify the problem.

Can somebody please help?

[Hell Guapo]

Found the problem.

The default install when using GoDaddy as a host contains a setting under CONFIGURATION > MY STORE > cURL Proxy Address to: proxy.shr.secureserver.net:3128

The helper at GoDaddy said, as of 2008, Authorize.net does not require GoDaddy to use this proxy, but apparently the default install still contains this information.

I made an order in Testing Mode and received a positive result and an order email!

[DrByte]

GoDaddy was supposed to have removed that setting from their default one-click install several months ago.
If that was a fresh install, call them up and complain.