09-18-2014 03:36 PM
One of my clients received an e-mail that their Authorize.Net IP, 220.127.116.11, 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.
09-19-2014 11:39 AM
The same thing happened to us. Troubleshooting the issue has so far been fruitless:
Could it be on the router level? The post by @stevelolz makes me think that it is more likely due to something WooCommerce related.
09-19-2014 12:22 PM - edited 09-19-2014 02:15 PM
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.
09-23-2014 02:43 PM
09-25-2014 09:12 AM
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?
09-25-2014 11:03 AM
09-26-2014 06:27 AM
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!
09-26-2014 09:37 AM
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 :)