Reply
Highlighted
Contributor
Posts: 17
Registered: ‎10-03-2013

Sandbox Accept.js seems to be down

I'm getting a 550 error in the Chrome network monitor. It was working earlier today.

 

XMLHttpRequest cannot load https://apitest.authorize.net/xml/v1/request.api. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://localhost:5000' is therefore not allowed access. The response had HTTP status code 550.

 

Here's the extract Curl command

curl "https://apitest.authorize.net/xml/v1/request.api" -X OPTIONS -H "Pragma: no-cache" -H "Access-Control-Request-Method: POST" -H "Origin: https://localhost:5000" -H "Accept-Encoding: gzip, deflate, sdch, br" -H "Accept-Language: en-US,en;q=0.8" -H "User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" -H "Accept: */*" -H "Cache-Control: no-cache" -H "Referer: https://localhost:5000/" -H "Connection: keep-alive" -H "Access-Control-Request-Headers: content-type" --compressed

 

is also showing 550 

Highlighted
Contributor
Posts: 17
Registered: ‎10-03-2013

Re: Sandbox Accept.js seems to be down

Here's the actual response:

 

$ curl -i "https://apitest.authorize.net/xml/v1/request.api" -X OPTIONS -H "Pragma: no-cache" -H "Access-Control-Request-Method: POST" -H "Origin: https://localhost:5000" -H "Accept-Encoding: gzip, deflate, sdch, br" -H "Accept-Language: en-US,en;q=0.8" -H "User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" -H "Accept: */*" -H "Cache-Control: no-cache" -H "Referer: https://localhost:5000/" -H "Connection: keep-alive" -H "Access-Control-Request-Headers: content-type" --compressed
HTTP/1.1 550 Unknown
Content-Type: text/html
Server: Microsoft-IIS/7.5
Content-Length: 54
Date: Wed, 12 Oct 2016 19:09:14 GMT
Connection: keep-alive

The custom error module does not recognize this error.

Highlighted
Contributor
Posts: 17
Registered: ‎10-03-2013

Re: Sandbox Accept.js seems to be down

Highlighted
Posts: 321
Topics: 5
Kudos: 36
Blog Posts: 5
Ideas: 0
Solutions: 26
Registered: ‎11-09-2011

Re: Sandbox Accept.js seems to be down

@blackbeltdev Thanks. We're investigating right now.

--
"Move fast and break things," out. "Move carefully and fix what you break," in.
Highlighted
Member
Posts: 4
Registered: ‎10-12-2016

Re: Sandbox Accept.js seems to be down

We are also experiencing this.

 

Resolving apitest.authorize.net... 96.16.164.192
Connecting to apitest.authorize.net|96.16.164.192|:443... connected.
HTTP request sent, awaiting response... 550 Unknown
2016-10-12 16:41:35 ERROR 550: Unknown.

Highlighted
Posts: 321
Topics: 5
Kudos: 36
Blog Posts: 5
Ideas: 0
Solutions: 26
Registered: ‎11-09-2011

Re: Sandbox Accept.js seems to be down

We've identified the cause and are currently staging a fix, which I expect will be deployed in the next few hours. If there are any delays I'll update the thread. Thanks.

--
"Move fast and break things," out. "Move carefully and fix what you break," in.
Highlighted
Member
Posts: 2
Registered: ‎10-13-2016

Re: Sandbox Accept.js seems to be down

I am still seeing this error on the Sandbox Server, has the fix been deployed?

Highlighted
Member
Posts: 2
Registered: ‎07-16-2014

Re: Sandbox Accept.js seems to be down

What is the status on this?  This issue is also impacting the soap test service.  Fetching https://apitest.authorize.net/soap/v1/Service.asmx?wsdl results in the same error.

 

 

The custom error module does not recognize this error.

 

Highlighted
Member
Posts: 4
Registered: ‎10-12-2016

Re: Sandbox Accept.js seems to be down

We have a mission critical dev project which was supposed to launch today. It is stopped. Please provide upate as soon as possible so we can inform our clients of the status.

Highlighted
Posts: 321
Topics: 5
Kudos: 36
Blog Posts: 5
Ideas: 0
Solutions: 26
Registered: ‎11-09-2011

Re: Sandbox Accept.js seems to be down

We encountered a delay. We understand this needs to be fixed urgently, but it's critical that we do so correctly. We will be working on getting this fixed today. Many apologies for the inconvenience.

--
"Move fast and break things," out. "Move carefully and fix what you break," in.