cURL / Authorize.net AIM solution for Wild West Reseller hosting

[bradymc]

After pulling my hair out for the past 3 days (which is HARD to do since I shave my head!), I've finally discovered the problem I was having with trying to get the Authorize.net AIM module working correctly. Before it would just sit there and spin it's wheels and eventually tell me that it couldn't find the page. No Authorize error messages or anything, just a 404 message from the browser.

If you host with a Wild West Reseller (they are the reseller of GoDaddy products and their stores typically look similar to this), here's what you need to do:

1. Go to Admin - Configuration - My Store and set cURL Proxy Status to True.
2. Call their tech support to verify the cURL Proxy address and don't forget to ask about the port number. When I called the first time, I was told it was "proxy.shr.secureserver.net" so that's all I used. If I was paying attention to the details it asked for in ZC, I would've noticed that it wants the port number following it. So I called back and was told to use "proxy.shr.secureserver.net:3128". You may notice that 3128 is the same port used for people with GoDaddy accounts.
3. You do not need to configure Response/Receipt URLS in your Authorize account. I verified this info with Authorize. I was told that they should be left blank.
4. You do not need to modify your authorizenet_aim.php file unless you are having problems with your SSL. I am using their Turbo SSL on a UNIX / economy hosting account.

I hope this helps at least one person looking for the same answers I was.

[Ajeh]

Thanks for the update ... this is always a help to others to know these little tidbits of information for when they run into similar issues ...

[issy]

I just want to say that I was having problems with this as well, the page would just hang and do nothing; after following your instructions bata bim!! it worked just fine.

Thank you very much Brady for looking into this.

Have a great day

[DrByte]

It's interesting to note that "proxy.shr.secureserver.net" is the very same address that GoDaddy uses ... it resolves to: 64.202.165.130 -- so it's fine to use the name or the IP address.