Local Network Access (LNA) Issues Affecting Simpplr

Overview

Chromium-based browsers have rolled out a stricter Local Network Access (LNA) policy. Simpplr itself does not rely on local network access, but some security tools intercept user requests and reroute them through a local or loopback address. When this happens, the browser may treat the request as a potential local network access attempt and block it. As a result, Simpplr may fail to load or behave unpredictably.

What changed

Chromium-based browsers now require explicit user approval whenever a website tries to access a local or loopback address. If the user does not grant this permission, the browser blocks the request. Security software that reroutes network traffic to a local address can unintentionally trigger this rule, causing Simpplr to load incorrectly.

Chromium based browsers

The new policy is effective in the following browsers.

• Google Chrome 142 
  • Announcement
  • Administrator policy
• Microsoft Edge 143
  • Announcement
  • Administrator policy
• Brave
  • Announcement
• Any other Chromium based browsers

What you can do

If users experience loading issues caused by Chromium’s Local Network Access (LNA) restrictions, administrators can address the problem using one of the following approaches.

Option 1: Prevent Simpplr traffic from being classified as Local Network Requests

This requires configuration changes by your organization’s system administrators or network security team.
This is the recommended solution because it avoids weakening browser security policies.
Simpplr cannot provide guidance on customer-specific network configurations.

Option 2: Whitelist your intranet URL in the Chromium LNA policy

If preventing local classification is not feasible, administrators can whitelist the intranet URL.
Important: Users will not benefit from Chromium’s enhanced permission controls when this exception is applied.

System administrators can distribute the appropriate policy using standard Mobile Device Management (MDM) tools. Refer to the official policy documentation for each supported browser.

Example: Google Chrome (macOS) Plist configuration

Replace https://example.com with the URL your organization uses to access Simpplr or your intranet
for example:

• https://example.org
• https://subdomain.example.com 
• https://example.app.simpplr.com or 
• https://example.eu.simpplr.com

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>LocalNetworkAccessAllowedForUrls</key>
    <array>
        <string>https://example.com</string>
    </array>
</dict>
</plist>

The above policy can be loaded by running the command

defaults import com.google.Chrome ~/chrome_policy.plist

When the policy is applied correctly it can be observed in the site settings.

Option 3: End users can grant Local Network Access

Google Chrome

If the user is seeing the prompt for the first time they can click “Allow”.

If the user has already blocked the access, they can click on the site settings and toggle “Local network access” to enabled.

Edge

If the user is seeing the prompt for the first time they can click “Allow”.

If the user has already blocked the access, they can click on the site settings and change “Local network access” to “Allowed".