Experience Builder Apps Not Working After Upgrade to 11.5

[ag-maile]

Hello,

After the recent upgrade AGE to 11.5, the Experience Builder (ExB) app in Portal is not functioning correctly. Accessing https://test-int.azso.com/portal/apps/experiencebuilder (provided here as an example, since the original address would only work on the internal network) returns a URL like:

https://test-int.azso.com/portal/apps/experiencebuilder/cdn/365/cdn/365/cdn/365/jimu-core/init.js

instead of the expected:

https://test-int.azso.com/portal/apps/experiencebuilder/cdn/365/jimu-core/init.js

The WebContextURL is correctly configured as https://test-int.azso.com/portal

There is a load balancer in place, but I don’t manage it and don’t have access to it. It seems unlikely that the LB is causing the issue, since everything else on the portal—server, datastore, and other applications—is working correctly. ExB appears to be the only affected application.

Interestingly, ExB works correctly when accessed via the local address (FQDN + port 7443).

Could you please advise on what might be causing this behavior and how to resolve it?

Thank you.

[Joshua-Young]

Are you using a ArcGIS Web Adaptor or your own reverse proxy? I ran into a similar issue with ArcGIS Monitor when I tried to create my own reverse proxy and I got a regex expression wrong.

I do not think this would be the issue, but have you installed Portal for ArcGIS 11.5 Web Applications Patch? 

https://support.esri.com/en-us/patches-updates/2025/portal-for-arcgis-11-5-web-applications-patch 

[ag-maile]

We are using our own reverse proxy.

Regarding the patch, the Portal for ArcGIS 11.5 Web Applications Patch was successfully applied, and all services were restarted afterward.

However, Experience Builder (ExB) is not working, neither before nor after applying the patch.

[Joshua-Young]

We have been running ArcGIS Enterprise 11.5 since June on Windows Server, and we have not encountered that particular issue. We are using ArcGIS Web Adapters for our reverse proxies. It sounded like when you access the internal URL the issue does not occur and the issue only happens from the external URL. That to me sounds like the issue is in the reverse proxy.