nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Survey123 connection blocked in Chrome after Nov 2025 update

mattkramer

Hello,

I was wondering if anyone else is experiencing issues with survey123 forms embedded in dashboards. Users who are using Google Chrome and have installed the most recent (Nov, 5th 2025) update have not been able to access forms via ArcGIS Dashboards. They are getting connection blocked and CORS errors. These issues are not present when accessing the forms/dashboards in Edge.

If anyone has any information on this, it would be appreciated!

Encuentra más publicaciones etiquetadas con

Accepted answers

TonghuiMing

Hi all,

The legacy patches are now pushing to public for 11.1, 11.3, 11.4 (coming soon), 11.5, and 12.0:

https://support.esri.com/en-us/patches-updates/2026/portal-for-arcgis-web-app-embedded-element-patch

You can follow this site for more information and updates on Enterprise 11.4.

Thanks,

Tonghui

All comments

BenClark

I can't offer any advice but we've been dealing with the same behavior for embedded surveys in Experiences. Very annoying...

Annie_K

Following the Chrome 142 update, we have been logging various defects addressing the CORS errors the Chrome update is causing, associated with embedded apps (Survey123, etc.) in our Dashboards, Experience Builder, and other iframes.

One defect is closely related to your issue, but was specifically logged for surveys embedded in Experience Builder. The workaround will be the same for Dashboards and I'll provide it below. I would recommend that you create a case with Esri Technical Support so that we can log a defect specific for the Dashboards product.

Experience Builder defect: BUG-000180686

Known workarounds:

-Use Firefox or Edge

-Go to chrome://flags/ and set “Local Network Access Checks” from Default to ‘Disabled’ (the equivalent of what it would have been before the Chrome upgrade to 142.x)

mattkramer

Hey Annie, thank you for the quick response and solution! I will get that ticket created so that can be logged for Dashboards.

Thanks!

Annie_K

Thank you @mattkramer!

JennaWalz3

We are having the same issue. Does anyone know of a workaround revolving an agency-wide policy to allow access? If you could point me in the right direction that would be great!

Daniel_Perkins

For what it's worth our IT department has advised us that a similar "update" is forthcoming to Edge and the same problems will occur there.

To access the settings in Edge: edge://flags/#local-network-access-check

Ruth_JiatengXu

Hi @mattkramer @BenClark @JennaWalz3 @Daniel_Perkins ,

The survey widget in ArcGIS Experience Builder has been resolved by updating the archived Survey123 JS API, but the survey designer in Experience Builder and embedded surveys in ArcGIS Dashboard are still affected and will require an additional patch to the Enterprise.

Thanks,

Ruth

Daniel_Perkins

Hi @Ruth_JiatengXu I am still seeing the issues with the Survey123 web app in ArcGIS Enterprise.

Ruth_JiatengXu

Hi @Daniel_Perkins ,

The fix only applies to the surveys loaded using the Survey widget. It does no resolve the issue for surveys loaded using the Embed widget.

If you are still experienving the issue with the survey loaded using the Survey widget, could you please help me check whether the "locale-network-access" keyword is present in the iframe of the Survey widget, as shown in the screenshot below?

Also, could you let me know which version of Enterprise you are using?

Thanks,

Ruth

Geoeki

@Ruth_JiatengXu I can confirm...embedded Survey123 component in our custom app doesn't work either due to this:

That's a big issue...Chrome will soon require this and using Firefox or Edge as a workaround isn't working either in a company of 80k employees, when Chrome is the standard group-wide browser.

Ruth_JiatengXu

Hi @Geoeki ,

Thanks for sharing here. According to the screenshot your provided, the iframe does not appear to be one created by the Survey123 JS API. The "allow" attribute needs to be added when the iframe is initialized; otherwise, it won't work.

You can use the Survey123 JS API to embed Survey123 form as follows:

Survey123 JS API blog: https://community.esri.com/t5/arcgis-survey123-blog/introducing-the-survey123-web-app-javascript-api/ba-p/896667.

If it is still not working for you, could you please share a sample app with us so we can investigate? You can send it by email as well.

Thanks,

Ruth

Bernd_Loigge

Hi @Ruth_JiatengXu

I am an colleague of @Geoeki . I have posted here as well: https://community.esri.com/t5/arcgis-survey123-questions/survey123-webform-in-iframe-blocked-by-chrome/m-p/1669034#M64878

We are initializing the Survey123WebForm in an Angular App using the same concept like described in the blog post.

How to set the allow attribute on the iframe correctly?

          const formObj = {
            clientId: GisExplorerSurvey123FormComponent.CLIENT_ID,
            container: this.survey123?.nativeElement,
            portalUrl: this.strManagerService.getPortalUrl(),
            hideElements: ["field:location", "topbar", "submit"],
            version: surveyItemInfo.version,
            jsApiVersion: surveyItemInfo.version,
            itemId: surveyItemInfo?.itemId,
            mode: undefined as string | undefined,
            globalId: undefined as string | undefined,
            token: this.strManagerService.getToken(),
          };

          this.survey123WebForm = new Survey123WebForm(formObj);
          const container = this.survey123WebForm.getContainer();
          const iframe = container.querySelector("iFrame");
          iFrameDiv.setAttribute("allow", "geolocation self https://survey123.arcgis.com; camera self https://survey123.arcgis.com; microphone self https://survey123.arcgis.com; local-network-access *");

Thanks,

Bernd

Ruth_JiatengXu

Hi @Bernd_Loigge ,

This code can be removed, as the Survey123 JS API automatically adds the allow attribute to the iframe.

const iframe = container.querySelector("iFrame");
iFrameDiv.setAttribute("allow", "geolocation self https://survey123.arcgis.com; camera self https://survey123.arcgis.com; microphone self https://survey123.arcgis.com; local-network-access *");

Thanks,

Ruth

EricKriener

this isn't just a survey123/iFrame thing... it's happening for dashboards, arcade, and wab apps that are hosted/built on AGOL and are trying to get at our public arcgis server REST services

ctalleygreenville

Yes, we are having issues with this as well. Especially embedded web maps/apps using the Embed code that are using our Stand alone arcgis Server Rest Services. I will likely submit to Esri especially if Edge will no longer work as well.

DavidFlack

I am having this problem in Edge 143.0.3650.66. The fix suggested by @Daniel_Perkins appears to be viable.

To access the settings in Edge: edge://flags/#local-network-access-check and set this to Disabled. Then restart the browser.

BenClark

Any word on a permanent fix for surveys nested within Experiences using the Embed widget? My organization is just about to deploy a public-facing initiative that includes two Experience/Survey123 combinations that no longer work. I don't think we can move forward now without an actual fix that doesn't require client-side actions or outright re-designing the affected resources.

ctalleygreenville

Ben,

In my checks, these issues do not affect the public users! It appears to be mostly for our intranet users who are on the local network. If you aren't on the local network, the apps work(so far in my short term tests) Is this was everyone else is discovering? I am testing with a laptop for which I am switching between a city wireless network and a non-city wireless network. If I am on the city's network, the CORS errors appear. If I switch to the non-city wireless network, and refresh the page, the data appears.

So, our intranet users think the apps are not working but they are.

The fix to change the flag setting to "disable" appears to work but I am not sure I can talk our network admins into pushing out the "disable" option to override these new security settings to our city network users.

BenClark

Oh, cool. Yeah, sure enough it does work off-network. Thanks for the info! That's a huge help.

ToddW_stl

good find - I've reported this internally as I ran into it today (again) on an internal only project.
Chrome 143, Survey123 embedded in a dashboard, ArcGIS Enterprise 11.5

Jaivik_P

It seems Microsoft Edge is also being impacted by this for ArcGIS Dashboard embedded surveys at 10.9.1 version! Can someone confirm this?

If thats the case, Firefox is the only browser which is still working.

JohnZepeda2

Ran into this problem about a month ago too and switched to Edge. As of today, I had similar issues with Edge where it said the Survey was inaccessible or did not exist.

Similar work around does the trick for Edge, type in edge://flags/#local-network-access-check and set “Local Network Access Checks” from Default to ‘Disabled’

Both Chrome and Edge are now working for the Dashboards with embedded Survey123 forms.

Thanks Annie!

MichaelB25

Sorry- replied to wrong topic.

Ruth_JiatengXu

Hi @Jaivik_P @ToddW_stl @BenClark @DavidFlack @ctalleygreenville @EricKriener @Daniel_Perkins ,

This issue is caused by a new local network permission introduced in the latest Chromium update. It affects both Chrome and Edge users, as embedded local resources (such surveys, web maps, etc.) are now blocked unless the "local-network-access" attribute is added to the iframe.

The fix has already been implemented in the Survey widget within ArcGIS Experience Builder and the Survey123 JS API, but the remaining issues are still being worked on.

Relevant support cases:

Experience Builder embed widget: https://support.esri.com/en-us/bug/the-arcgis-experience-builder-embed-widget-with-an-embe-bug-000181346
Dashboard embedded content: https://support.esri.com/en-us/bug/in-arcgis-dashboards-the-embedded-content-element-conta-bug-000180846

Workaround:

The current workaround for this issue is to disable Local Network Access Checks:

Chrome: chrome://flags/#local-network-access-checks
Edge: edge://flags/#local-network-access-checks

I also encourage you to contact Esri Support with your Enterprise version and the affected app. Our Support team will attach your case to the existing bug report, which helps us better assess the impact.

Thanks,

Ruth

Cat_Boyes

Just checking in to say I am also experiencing this issue. https://community.esri.com/t5/arcgis-dashboards-questions/chrome-amp-edge-blocking-embedded-survey123-form/m-p/1672905#M11694

JakeMatthys

We are also experiencing this issue with Surveys embedded in dashboards. We are also observing the issue with social media links on a Sites page that is embedded in an Exp Builder.

Daniel_Perkins

appears resolved in updates https://support.esri.com/en-us/bug/in-arcgis-dashboards-an-embedded-content-element-contai-bug-000180846

Jaivik_P

Exciting! However, it says fixed at Portal 12.1 version.

Lets hope they have patch release planned to support the previous versions.

BenClark

My thoughts too, @Jaivik_P. Fingers crossed for a legacy patch...

Ruth_JiatengXu

Hi @BenClark @Jaivik_P @JakeMatthys @Cat_Boyes ,

The issues will be fixed for Dashboard and Experience Builder in Enterprise 12.1. For the earlier versions, please contact Esri Support with your Enterprise version so we can work on a patch.

Thanks,

Ruth

TonghuiMing

Hi all,

The legacy patches are now pushing to public for 11.1, 11.3, 11.4 (coming soon), 11.5, and 12.0:

https://support.esri.com/en-us/patches-updates/2026/portal-for-arcgis-web-app-embedded-element-patch

You can follow this site for more information and updates on Enterprise 11.4.

Thanks,

Tonghui

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.