Reply
Highlighted
Member
Posts: 2
Registered: ‎10-02-2015

Re: Access Denied

I'm getting this error now too, it seems to only happen on one particular server of mine. Using a different merchant ID still gives me the error:

 

Access Denied
You don't have permission to access "http://apitest.authorize.net/soap/v1/Service.asmx" on this server.
Reference #18.d1fd4317.1443647142.26a6469

 

However, I don't get the issue on any other server using the same code and credentials. Is my IP the issue? The server's IP is: 174.120.241.66 

 

Thanks.

Highlighted
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: Access Denied

That because apitest.authorize.net  required https , it will not work with http

Highlighted
Member
Posts: 2
Registered: ‎10-02-2015

Re: Access Denied

I'm specifically making the request with https, but yes it does seem to get forced down to http.

Highlighted
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: Access Denied

Then is the software that is calling apitest.authorize.net/soap/v1/Service.asmx

 

Highlighted
Member
Posts: 2
Registered: ‎12-18-2015

Re: Access Denied

I am getting:

response_array returned at [0] = 

Access Denied

You don't have permission to access "http://secure2.authorize.net/gateway/transact.dll" on this server.

Reference #18.9a461160.1450297746.abb1b31

 

While the URL error message comes back as http:// it is using https in the code and Authorize.nets dns is forcing the url to https if you try to drop the suffix s.

 

Different customers have different ref#.

 

But on the same day we will get successful completions. The site is hosted at GoDaddy but not sure of the IPA, SSL is SHA2. We do < 10 transactions/day typically.

 

Any help appreciated.

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

Re: Access Denied

[ Edited ]

Hello @paulmhill88

 

Please report this to developer@authorize.net with the following information:

 

  • The merchant name, Gateway ID, and website, if possible
  • The IP address receiving the Access Denied message
  • The URL they are connecting to—usually given in the Access Denied message
  • The Reference # listed in the Access Denied message
  • A screenshot of the error, if possible
  • The date and time when they first encountered the message
  • What the merchant was attempting to do when they saw the error
  • If the error occurs in a browser, include which troubleshooting steps you attempted first

Richard