Sporadic issue with Classic Web Maps not working in Chrome v.142.0.7444.60

[JackBovee]

Our Chrome web browsers happened to update overnight to version 142.0.7444.60.  Now, whenever we try to access an WAB using the Classic Web Map Viewer (or any map using the Classic Web Map Viewer), none of our hosted layers are available.  Everything is visible and functional still if you open the map in the new Map Viewer, but anything build with Classic seems to be broken atm.

We still haven't finished converting all our WAB applications over to Experience Builder yet, as I had assumed they would continue to work until next spring.

[cepsgis]

It is. Trust me.

[Jamie_Leitch_CNF]

yes this solved my issue, thank you!

[JackBovee]

The Chrome settings were in the browser itself, just to the left of the address bar.

[cepsgis]

This is impacting all services in web maps consumed by our EAM solution. Dashboards, surveys, and Experience Builders are also affected, and field staff are now reporting issues accessing data. 

[MichaelB25]

I've been working on a similar problem this afternoon. Only in updated Chrome browser several of our imagery basemaps weren't displaying. Enabling "local network access" (either from pop-up, or "site information" icon to left of URL) resolves problem.

I'm guessing that AGOL apps are referencing what Chrome sees as the local network. This is a broad list, I'm guessing a local loopback may be to blamed, but unsure. See: https://wicg.github.io/local-network-access/#non-public-ip-address-blocks