Portal apps incorrectly pointing to 7443 url

[Anonymous User]

Hi,

We have an Enterprise deployment where the Portal apps are failing to load. When loading the apps, they're trying to load resources (esri.css, js) from the 7443 internal URL to the Portal. Due to self-signed cert on the 7443 URL, these apps fail to load.

For example opening: https://serverDEV/portal/apps/Minimalist/index.html fails as it tried to load https://serverDEV:7443/arcgis/jsapi/jsapi/esri/themes/calcite/esri/esri.css and https://serverDEV:7443/arcgis/jsapi/jsapi/ 

The strange thing, in our environment we also have a Test deployment, which has been configured exactly the same and all the apps load properly. That is, these apps load without the 7443 port, thus go through the WA and make use of the proper certs. Ie, the apps properly reference/load: https://serverTEST/arcgis/jsapi/jsapi/esri/themes/calcite/esri/esri.css

I've done a side-by-side compare of URLs and configuration inside the portaladmin. Both these deployments are configured exactly the same.

Any ideas which may account for how/why the apps are trying to load with the internal URL/port?

Before I unregister / re-register the WA, can anyone confirm that this process would update the references inside these apps?

[JonathanQuinn · Accepted solution]

Hey Kevin

The URL for any of those built-in applications should be updated once you register the web adaptor or web context URL, but that doesn't seem to have happened. You could just append /edit to the WA URL and then hit Edit Web Adaptor without making any changes. This should trigger the logic to update the URL and then reindex, then take a look at the URLs for the applications again.

[Anonymous User]

The simple /edit was enough to get the WA URL into these apps.

Thanks for the help, Jon!