---
title: "Browser Popup - Local Network Access"
canonical: "https://kb.myframeworks.com.au/space/CO/244187139/Browser%20Popup%20-%20Local%20Network%20Access"
format: markdown
---
## Overview of Issue

Google Chrome and Microsoft Edge include security restrictions that require your permission before a website can communicate with software running on your local computer. Frameworks uses QZ Tray, a third-party print service installed on your computer, to connect with local printers and EFTPOS devices. Without this connection, printing documents, generating labels and processing EFTPOS transactions will not work correctly.

From Chrome 147 and Edge 147 onwards, these restrictions now apply to WebSocket connections. This means users may see a new permission popup even if they previously allowed local network access in an earlier browser version (Chrome 142 to 146 or Edge 143 to 146). The new popup specifically asks for permission to connect to apps and services running on the same computer.

If you accidentally click **Block**, or if the Frameworks URL is not in the allowed list, Frameworks cannot communicate with QZ Tray.

> ⚠️ **Info:** This security feature is part of Chrome and Edge's **Local Network Access (LNA)** restrictions, designed to protect users against malicious websites accessing local services without permission. Frameworks needs this permission to communicate with QZ Tray for printing documents, generating labels and processing EFTPOS transactions.

## Understanding the Permission Popup

When you first access Frameworks or Frameworks establishes a WebSocket connection to QZ Tray, your browser displays a popup similar to the following:

*"[your-frameworks-domain] wants to Access other apps and services on this device"*

![image-20260407-061200.png](media://6c061731-71f2-4f8d-b6e8-42020fd7ce6e)

> ℹ️ **Note:** If you previously allowed local network access in Chrome 142 to 146 or Edge 143 to 146, you may still see this new popup. The earlier permission covered standard network requests. The WebSocket permission is separate and needs to be allowed independently.

You have three options to handle this:

> Macro (toc)

---

## Option 1: Prevent the Popup (Add to Allowed List in Advance)

You can configure the browser to allow Frameworks access before you ever see the popup. This is the recommended approach for new installations or when setting up multiple computers.

### Google Chrome

#### Step 1: Open Site Settings for Frameworks

1. Open Google Chrome.
2. Navigate to your Frameworks URL.
3. Click the **tune icon** (the sliders icon) to the left of the URL in the address bar.
4. Click **Site settings**. The site-specific permissions page opens.

#### Step 2: Allow Apps on Your Device

1. Scroll down and find the **Apps on your device** setting.
2. Set the value to **Allow**.
3. If you also see a **Devices on your network** setting, set this to **Allow** as well.
4. Close the Settings tab.
5. Refresh your Frameworks browser tab.

#### Alternative: Add via Chrome Settings

1. Open Google Chrome.
2. Click the three vertical dots in the top-right corner to open the menu.
3. Select **Settings**.
4. In the left sidebar, click **Privacy and security**.
5. Click **Site Settings**.
6. Scroll down and click **Additional permissions**.
7. Click **Apps on your device**.
8. Click **Add** next to "Allowed to access apps on your device".
9. Enter the domain of your Frameworks URL:
  - Cloud hosted environments: `[SiteID].[Environment].myframeworks.com.au`
  - On-premise environments: `[Servername or IP Address]:[port]`
10. Click **Add**.
11. Close the Settings tab.

> ✅ **Tip**: You can use the following wildcard `[*.]myframeworks.com.au` to cover all your Frameworks environments.

Your Frameworks site will now be able to communicate with QZ Tray without showing the permission popup.

### Microsoft Edge

#### Step 1: Open Site Settings for Frameworks

1. Open Microsoft Edge.
2. Navigate to your Frameworks URL.
3. Click the **lock icon** (or **tune icon**) to the left of the URL in the address bar.
4. Click **Permissions for this site**. The site-specific permissions page opens.

#### Step 2: Allow Local Network Access

1. Scroll down and find the **Apps on device** setting.
2. Set the value to **Allow**.
3. If you also see a **Local network** setting, set this to **Allow** as well.
4. Close the Settings tab.
5. Refresh your Frameworks browser tab.

#### Alternative: Add via Edge Settings

1. Open Microsoft Edge.
2. Click the three horizontal dots in the top-right corner to open the menu.
3. Select **Settings**.
4. Select **Privacy, search, and services** from the left sidebar.
5. Scroll down and click **Site permissions**.
6. Click **All permissions**.
7. Find and click **Apps on device** in the permissions list.
8. Click **Add** next to "Allow".
9. Enter the domain of your Frameworks URL:
  - Cloud hosted environments: `[SiteID].[Environment].myframeworks.com.au`
  - On-premise environments: `[Servername or IP Address]:[port]`
10. Click **Add**.
11. Close the Settings tab.

> ✅ **Tip**: You can use the following wildcard `[*.]myframeworks.com.au` to cover all your Frameworks environments.

Your Frameworks site will now be able to communicate with QZ Tray without showing the permission popup.

---

## Option 2: Allow Access from the Initial Popup

When the permission popup appears:

1. Read the message carefully. It should show your Frameworks domain (for example, `siteid.environment.frameworks.com.au`).
2. Click **Allow** to grant permission.
3. The browser remembers your choice. Printing and EFTPOS functionality should work normally.

![image-20260407-061200.png](media://6c061731-71f2-4f8d-b6e8-42020fd7ce6e)

> ⚠️ **Important:** If you previously allowed local network access in an earlier browser version, you may still see this popup for the WebSocket connection. Click **Allow** again. The browser treats the WebSocket permission separately from the earlier local network access permission.

---

## Option 3: Add Frameworks to Allowed List (If You Clicked Block)

If you previously clicked **Block** or need to manually change the setting, follow the steps below for your browser.

### Google Chrome

#### Quick Method: Via Address Bar

1. Navigate to your Frameworks URL in Chrome.
2. Click the **tune icon** (the sliders icon) to the left of the URL in the address bar.
3. Find the **Apps on your device** setting and change it to **Allow**.
4. If you also see **Devices on your network** blocked, change this to **Allow** as well.
5. Refresh the Frameworks browser tab.

#### Full Method: Via Chrome Settings

1. Open Google Chrome.
2. Click the three vertical dots in the top-right corner to open the menu.
3. Select **Settings**.
4. In the left sidebar, click **Privacy and security**.
5. Click **Site Settings**.
6. Scroll down and click **Additional permissions**.
7. Click **Apps on your device**.
8. If your Frameworks URL appears in the "Not allowed to access apps on your device" section, click on the URL.
9. Click **Remove** to delete the entry from the blocked list.
10. Click **Add** next to "Allowed to access apps on your device".
11. Enter the domain of your Frameworks URL:
  - Cloud hosted environments: `[SiteID].[Environment].myframeworks.com.au`
  - On-premise environments: `[Servername or IP Address]:[port]`
12. Click **Add**.
13. Close the Settings tab.
14. Refresh your Frameworks browser tab.
15. Test printing functionality to confirm the connection works correctly.

### Microsoft Edge

#### Quick Method: Via Address Bar

1. Navigate to your Frameworks URL in Edge.
2. Click the **lock icon** (or **tune icon**) to the left of the URL in the address bar.
3. Click **Permissions for this site**.
4. Find the **Apps on device** setting and change it to **Allow**.
5. If you also see **Local network** blocked, change this to **Allow** as well.
6. Refresh the Frameworks browser tab.

#### Full Method: Via Edge Settings

1. Open Microsoft Edge.
2. Click the three horizontal dots in the top-right corner to open the menu.
3. Select **Settings**.
4. Select **Privacy, search, and services** from the left sidebar.
5. Scroll down and click **Site permissions**.
6. Click **All permissions**.
7. Find and click **Apps on device** in the permissions list.
8. If your Frameworks URL appears in the "Block" section, click on the URL.
9. Click **Remove** to delete the entry from the blocked list.
10. Click **Add** next to "Allow".
11. Enter the domain of your Frameworks URL:
  - Cloud hosted environments: `[SiteID].[Environment].myframeworks.com.au`
  - On-premise environments: `[Servername or IP Address]:[port]`
12. Click **Add**.
13. Close the Settings tab.
14. Refresh your Frameworks browser tab.
15. Test printing functionality to confirm the connection works correctly.

---

## Enterprise Policy (For IT Administrators)

For organisations managing Chrome or Edge across multiple devices, the `LocalNetworkAccessAllowedForUrls` browser policy can pre-approve Frameworks for local network access. This suppresses the permission popup for all users on managed devices and is the recommended approach for large deployments.

The policy accepts a list of URL patterns. Add the origin of your Frameworks site (not the local endpoint). For example:

- Cloud hosted environments: `https://[*.]myframeworks.com.au` or `https://[SiteID].[Environment].myframeworks.com.au`
- On-premise environments: `https://[Servername or IP Address]:[port]`

> **Note:** The `LocalNetworkAccessAllowedForUrls` policy applies to all Local Network Access permission types, including standard network requests and WebSocket connections. Setting this policy once covers both.

### Google Chrome

Deploy the `LocalNetworkAccessAllowedForUrls` policy via Group Policy, Intune, or your preferred device management tool.

**Windows Registry example:**

```
Path:   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\LocalNetworkAccessAllowedForUrls
Name:   1
Type:   REG_SZ
Data:   https://[*.]myframeworks.com.au
```

> ✅ For full details, see [Chrome Enterprise policy: LocalNetworkAccessAllowedForUrls](https://chromeenterprise.google/policies/#LocalNetworkAccessAllowedForUrls).

### Microsoft Edge

Deploy the `LocalNetworkAccessAllowedForUrls` policy via Group Policy, Intune, or your preferred device management tool.

**Windows Registry example:**

```
Path:   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\LocalNetworkAccessAllowedForUrls
Name:   1
Type:   REG_SZ
Data:   https://[*.]myframeworks.com.au
```

> ✅ For full details, see [Edge Enterprise policy: LocalNetworkAccessAllowedForUrls](https://learn.microsoft.com/en-us/deployedge/microsoft-edge-browser-policies/localnetworkaccessallowedforurls).

> ❌ **Warning:** The `LocalNetworkAccessRestrictionsTemporaryOptOut` policy (which disables Local Network Access restrictions entirely) is a temporary measure scheduled for removal. Do not rely on this policy as a long-term solution. Use `LocalNetworkAccessAllowedForUrls` instead to allow specific sites.

---

> ✅ # Additional Information
> ✅ 
> ✅ Refer to [Loss of Network due to Sleep](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30532514) for more information about QZ Tray network connectivity issues.
> ✅ 
> ✅ For more details about Chrome's Local Network Access feature, visit [Chrome's official documentation](https://developer.chrome.com/blog/local-network-access).
> ✅ 
> ✅ For more details about Edge's Local Network Access feature, visit [Microsoft's official documentation](https://support.microsoft.com/en-us/topic/control-a-website-s-access-to-the-local-network-in-microsoft-edge-ef7eff4c-676d-4105-935c-2acbcd841d51).
> ✅ 
> ✅ For guidance on deploying Local Network Access policies across managed environments, see [Chrome Enterprise policies](https://chromeenterprise.google/policies/#LocalNetworkAccessAllowedForUrls) and [Edge Enterprise policies](https://learn.microsoft.com/en-us/deployedge/microsoft-edge-browser-policies/localnetworkaccessallowedforurls).

> ⚠️ **Important**: This setting is specific to each browser profile. If you use multiple browser profiles or switch between different computers, you will need to configure this setting for each profile and device. Enterprise policies apply at the machine or user level and override per-profile settings.