topic Re: Authorize Retiring IP, Email to Update in Integration and Testing

Authorize Retiring IP, Email to Update

stevelolz — Thu, 18 Sep 2014 22:36:19 GMT

One of my clients received an e-mail that their Authorize.Net IP, 64.94.118.33, will expire and we need to update to a URL -- I am connecting to the gateway using WooCommerce and I'm unsure of where to swap the I.P. for the URL? Any advice would be helpful, thanks.

Re: Authorize Retiring IP, Email to Update

launchbrigade — Fri, 19 Sep 2014 18:39:53 GMT

The same thing happened to us. Troubleshooting the issue has so far been fruitless:

A thorough search through the files and databes for that IP address (64.94.118.33) did not return any results.
The only authorize.net URLs in the files are as they are expected - secure.authorize.net and a few dev URLs.
Pinging secure.authorize.net from both the server and my local computer both show 64.94.118.32.

Could it be on the router level? The post by @stevelolz makes me think that it is more likely due to something WooCommerce related.

Re: Authorize Retiring IP, Email to Update

RichardH — Fri, 19 Sep 2014 21:15:06 GMT

If you are connecting with a domain name in the URL and it's resolving correctly, you should be fine. It's only when there is a hard-coded IP address specified for the connection that will fail.

Also, if you have any monitoring tools set to that IP Address, those should be changed as well.

Richard

Re: Authorize Retiring IP, Email to Update

selwyn — Tue, 23 Sep 2014 21:43:53 GMT

My requests are going out through the old retiring IP, because my web application is hosted on a unix server and the following entry is been added to /etc/hosts 64.94.118.33 secure.authorize.net Questions ----------------- 1. Will I need to remove/comment this entry in /etc/hosts? 2. After removing this entry from /etc/hosts will the URL - https://secure.authorize.net/gateway/transact.dll get resolved automatically? 3. Or do I need to replace the new IP 64.94.118.32 in /etc/hosts

Re: Authorize Retiring IP, Email to Update

RichardH — Tue, 23 Sep 2014 21:58:56 GMT

Hello selwyn,

You should remove all authorize.net entries from /etc/hosts and use DNS to resolve the hostname.

Richard

Re: Authorize Retiring IP, Email to Update

lowellalleninc — Thu, 25 Sep 2014 16:12:59 GMT

Same as launchbrigade, client received notice about retiring IP address "which we noticed you are connecting to directly either for monitoring purposes or for your transaction processing" and search of our code shows transaction processing connects to https://api.authorize.net/xml/v1/request.api.

Could "monitoring purposes" refer to Authorize.Net account interface?

Re: Authorize Retiring IP, Email to Update

RichardH — Thu, 25 Sep 2014 18:03:26 GMT

Hello @lowellalleninc

In this context, website monitoring refers to using a 3rd party tool that periodically connects to Authorize.Net and determines if it is responding.

If your application connects to https://api.authorize.net/xml/v1/request.api, no further changes should be required.

Richard

Re: Authorize Retiring IP, Email to Update

LazDev — Fri, 26 Sep 2014 13:27:02 GMT

Is their a tutorial or some more information on how to check if my website is using this IP? Im using Woocommerce with Authorize AIM. Thanks in advanced for the help!

Re: Authorize Retiring IP, Email to Update

RichardH — Fri, 26 Sep 2014 16:02:19 GMT

Hello @LazDev

I would encourage you to contact the developer of Woocoommerce with Authorize AIM and check with them.

Richard

Re: Authorize Retiring IP, Email to Update

LazDev — Fri, 26 Sep 2014 16:37:07 GMT

Thanks for the reply. In case anyone wants to know who is using woocommerce AIM, I have contacted the developer and this is his reponse:

The Authorize.net gateway doesn't use direct IPs so your gateway will continue to function after September 30th :)