Reply
Member
Posts: 3
Registered: ‎06-13-2015

api.authorize.net not communicating with our server since June 2nd - help please!

Since June 2nd our server is not receiving any api calls fired by Automated Recurring Billing (ARB) transactions. The ARB transactions are taking place each day successfully and we can see that in our Auth.net backend. However we cannot find any evidence that these transactions are reaching our server. There are no permission denied messages, and certainly no errors inside our system at our silent post url. 

 

Our system is Drupal/Civicrm, and our silent post url is /sites/all/modules/civicrm/extern/authorizeIPN.php

 

We are at a complete loss about what to do, and Auth.net tech support have so far not replied to us in nearly a week. That's a lot of transactions not recorded!

 

At a minimum we need to know the IP address api.authorize.net originates from so we can see if those calls are reaching us in the first place. 

 

We have of course checked that the Silent Post URL is correct for our account, and further, we have checked that we can access that URL. 

 

We've also updated our root certificates according to the recent blog posts for the May 27th upgrade of server certificates. At least our hosting company assures us these certificates have been installed correctly.

 

We'd be very very grateful for any ideas of what to do next! Thanks

Posts: 2,765
Topics: 57
Kudos: 251
Blog Posts: 67
Registered: ‎12-05-2011

Re: api.authorize.net not communicating with our server since June 2nd - help please!

Hello @andrew55

 

Sorry to hear your having difficulties with your system.  You can view a list of whitelist addresses used by Authorize.Net to perform Silent Posts here: https://community.developer.authorize.net/t5/Integration-and-Testing/Authorize-Net-Whitelist-IP-Addr...

 

Please note that your URL must be publicly available on a standard port 80 or 443.

 

Richard

Member
Posts: 3
Registered: ‎06-13-2015

Re: api.authorize.net not communicating with our server since June 2nd - help please!

Thanks so much for this.

 

We've whitelisted your IP addresses and confirmed that our silent post URL is accessible:
https://druyoga.com/sites/all/modules/civicrm/extern/authorizeIPN.php

However we are still not receiving information from you.

A traceroute to your IPs suggest that traffic to us is being blocked somewhere in Arizona:

root@cloud [~]# nmap -F 198.241.162.104

Starting Nmap 5.51 ( http://nmap.org ) at 2015-06-14 10:14 BST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds

Tracing to this IP, the traffic appears to be dropped at an American IP address owned by Internap Network Operations - see below:

Starting Nmap 5.51 ( http://nmap.org ) at 2015-06-14 10:14 BST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
root@cloud [~]# traceroute 198.241.162.104 -n
traceroute to 198.241.162.104 (198.241.162.104), 30 hops max, 60 byte packets
1 62.255.175.254 0.635 ms 0.645 ms 0.648 ms
2 82.0.199.250 0.795 ms 0.979 ms 1.077 ms
3 149.11.44.49 7.803 ms 7.825 ms 7.966 ms
4 154.25.4.165 8.070 ms 154.25.4.161 8.027 ms 8.075 ms
5 154.54.39.21 7.798 ms 154.54.39.101 7.711 ms 7.829 ms
6 130.117.50.201 8.071 ms 154.54.39.129 7.960 ms 130.117.50.205 8.115 ms
7 130.117.51.158 7.878 ms 154.54.37.66 8.041 ms 8.042 ms
8 149.14.8.78 9.220 ms 8.821 ms 149.6.185.42 8.893 ms
9 212.118.240.40 9.360 ms 212.118.240.104 9.484 ms 212.118.240.40 9.545 ms
10 212.118.254.106 9.715 ms 10.079 ms 10.014 ms

http://who.is/whois-ip/ip-address/212.118.254.106

Would it be possible for Authorize.net to provide a trace in the opposite direction or confirm that our IP address (46.17.89.44) isn't firewalled or null routed inside their network?

Thanks - we're really suffering by not being able to receive api info from ARB transactions on our silent post URL!!!

Member
Posts: 3
Registered: ‎06-13-2015

Re: api.authorize.net not communicating with our server since June 2nd - help please!

We're still not having any luck, even after upgrading our server to every security benchmark we can think of - we now get A+ from ssllabs.

 

Is it possible you can tell us the method you are using to post from api.authorize.net to help us troubleshoot?

 

Best wishes!