Notice: Chrome Version 142 Restricts Web-to-Local Communication, Affecting SASE Client Detection
  

David Hong Lv1Posted Nov-07-2025 17:33



Background:
Starting from Chrome version 142.0.xx.xx., Google introduced an experimental security feature that restricts communication between web pages and the local network (for example, localhost or 127.0.0.1).
When a webpage attempts to communicate with a local service, Chrome now displays a popup prompt asking users whether to allow or block the connection.
This change affects systems or portals that rely on local client interaction, including the SASE client detection and login process.


Impact:
During the SASE client login or authentication process, the webpage attempts to detect and communicate with the local SASE client installed on the user’s device.
However, with Chrome 142’s new restriction enabled, this behavior may be blocked by default, resulting in:
  · The browser being unable to recognize the SASE client status
  · Login or authentication pages remaining stuck at “Client not detected”
      

Temporary Workarounds:
Solution 1: Use Edge or other non-Chrome browsers
We recommend temporarily using Microsoft Edge, Firefox, or any non-Chrome browser to access the SASE login portal or related resources.
  
Solution 2: Adjust Chrome settings to allow “Local Network Access”
Method 1: Allow the prompt during login
When accessing the SASE login page, Chrome will display a popup asking whether to allow local network access.
Since the default Chrome behavior is “Ask (default)”, simply click “Allow” when prompted.
This will enable the page to connect to your local SASE client successfully.
   
Method 2: Manually enable the setting in Chrome
If you previously blocked the connection or did not see the popup, follow these steps:
1. Open the SASE login page in Chrome.
2. Click the “Site settings” icon next to the address bar.
3. In the Site settings page, scroll down to the “Local network access” option.
4. Change the setting to “Allow.”
  
Solution 3: Restrict Chrome Auto-Update at the Network Level
For organizations with a centralized internet gateway or unified network egress, IT administrators can temporarily prevent Chrome from auto-updating to version 142 or later.
This can be achieved by blocking the following update service domains at the network level:
https://tools.google.com
https://update.googleapis.com
https://packages.google.com
Blocking these domains will prevent Google Chrome from automatically downloading or installing newer versions until the issue is fully resolved or verified as compatible.
  
Frequently Asked Questions (FAQ):
Q1: Does changing this Chrome setting create any security risks? Why does the SASE page need to access the local network?
A: No, this setting does not introduce any security or privacy risks.
The SASE webpage only connects to the SASE client running locally on your computer through a secure local network interface.
It does not read other data on your device or connect to other devices on your network.
  
Q2: Is this setting permanent, or must users allow it each time?
A: This configuration is site-specific and device-specific.
Each device only needs to allow the setting once per SASE access URL.
If multiple SASE access addresses are used, you must enable the setting once for each.
  
Q3: What if a user accidentally clicked “Block”?
A: If you previously selected “Block”, you can fix it by following Solution 2, Method 2 above to manually set the “Local network access” option to “Allow.”
  
Q4: Will this issue be resolved automatically in future versions?
A: This restriction is currently part of Chrome’s experimental features, and Google may modify or enforce it in future updates.
We will continue to monitor upcoming Chrome releases and provide compatibility updates as needed.
  

Like this topic? Like it or reward the author.

Creating a topic earns you 5 coins. A featured or excellent topic earns you more coins. What is Coin?

Enter your mobile phone number and company name for better service. Go

David Hong Lv1Posted Nov-13-2025 10:28
  
For more details can refer: https://developer.chrome.com/blog/local-network-access
You may use this link to open and check:  chrome://flags/#local-network-access-check

Moderator on This Board

13
4
0

Started Topics

Followers

Follow

913
182
94

Started Topics

Followers

Follow

Trending Topics

Board Leaders