Experiencing issues with your ArcGIS Online application displaying a blank or White Screen Online? This can often be attributed to proxy configuration problems. Let’s delve into a specific scenario and explore potential causes behind 500 and 403 errors when setting up a proxy for ArcGIS Online.
The configuration outlined below mirrors a user’s experience attempting to access a public ArcGIS Online map through a local server proxy. Initially, the application loads correctly without a proxy, but errors arise as soon as proxy directives are introduced.
Here’s a breakdown of the observed issues:
Scenario 1: 500 Internal Server Error with User Credentials
When the config.json file includes a username and password for the ArcGIS Online organization (http://myorg.maps.arcgis.com) within the proxy configuration, a 500 Internal Server Error is encountered.
The error message indicates a failure to load a resource, specifically pointing to the proxy endpoint:
Failed to load resource: the server [http:// /proxy/proxy.ashx?http://myorg.maps.arcgis.com/sharing/rest/portals/self?f=json&doj...] responded with a status of 500 (Internal Server Error).This suggests a server-side issue occurring within the proxy itself when attempting to authenticate or handle the request with the provided credentials.
Scenario 2: 403 Forbidden Error without User Credentials
Conversely, removing the username and password from the proxy configuration for http://myorg.maps.arcgis.com results in a 403 Forbidden Error.
The error message in this case is:
Failed to load resource: the server [http:// /proxy/proxy.ashx?http://myorg.maps.arcgis.com/sharing/rest/portals/self?f=json&doj...] responded with a status of 403 (Forbidden).A 403 error typically signifies that the server is refusing to fulfill the request, likely due to missing or incorrect authentication. In this context, without credentials provided in the proxy config, the request is being rejected by ArcGIS Online.
Context and Further Questions
To further diagnose these proxy issues, consider the following context points and questions:
-
Public Map Accessibility: The ArcGIS Online map in question is confirmed to be shared publicly (“Everyone”). This eliminates basic sharing restrictions as a potential cause.
-
ArcGIS Online Organization Setup: The organization utilizes ArcGIS Online (not Portal for ArcGIS) and has publicly shared content. There are no apparent organizational settings blocking public access.
-
Publicly Accessible Service Layer: The map incorporates a layer from a publicly accessible ArcGIS Server service hosted by the organization. Direct access to this service endpoint through the website proxy is confirmed to be working.
-
Authentication Methods: Attempts were made using both username/password and client ID/client secret within the proxy configuration, both leading to the 500 error.
Moving Forward
Based on these observations, troubleshooting should focus on:
- Proxy Configuration Review: Double-check the
proxy.config(or equivalent) for syntax errors, correct URL entries, and accurate credential placement if required. - Proxy Server Logs: Examine the proxy server’s logs for detailed error messages corresponding to the 500 errors. These logs can provide specific insights into what’s failing during the proxy request.
- ArcGIS Online Service Status: While less likely given the public nature of the resources, verify the overall health and status of ArcGIS Online services.
- Network Connectivity: Rule out any basic network connectivity issues between the local server, proxy server, and ArcGIS Online.
By systematically investigating these areas, you can pinpoint the root cause of the proxy errors and resolve the issue preventing your ArcGIS Online application from loading correctly and displaying content instead of a white screen online.
