Proxy Error - Status 0

[JillianStanford]

Hi All,

I am attempting to deploy a Web AppBuilder 2.15 app to a production server using the latest proxy from Releases · Esri/resource-proxy · GitHub .

I get the following error (the item ID is for the web map) when I load the app:

Unable to load https://[web server]/DotNet/proxy.ashx?https://[AGOL Org]/sharing/rest/content/items/[item ID]?f=json status: 0

However, when I browse directly to that URL outside of the app, I get no errors and the JSON description of the web map looks correct to me. Browsing to the item without the proxy gives me a 403 error, so proxy.config seems to be configured correctly.

What does "Status: 0" mean?

The proxy is good. I'm using it successfully for other WAB apps. The main difference is that those apps were created in WAB 2.8 and this new app is created in WAB 2.15. Is there a change to how apps are deployed that I'm not aware of?

Thanks for any help you can give troubleshooting this.

Jill

[YaoMo2]

Any updates on this? I'm having exactly the same issue.

Trying to access a private map and services on AGOL though WAB and resources proxy. 

http://localhost/DotNet/proxy.ashx?https://[myAGOLaccount].maps.arcgis.com/sharing/rest/portals/self... 

The proxy page worked if I visit the link directly and get JSON response. But if the link is accessed through web appbuilder, then I got error message stating "unable to load <url>, status: 0". 

In Fiddler, I can see that the proxy request gets proper JSON response. 

[JillianStanford]

Hi,

For me, it was a mixed content problem.

When I accessed the Web AppBuilder app using https instead of http the error was resolved.

I hope that helps!

Jill

[PrithvirajShunmugham]

Hi @JillianStanford im new to esri community, could you please help me out.

im getting above error with status 0 

[JillianStanford]

Hi,

This was a long time ago so I don't remember the details but did you try the solution that worked for me?

I was trying try to access an encrypted web map ("https") from unsecured Web AppBuilder ("http"). Once I switched to running WAB from https://localhost the error resolved.

Hope that helps.