Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ on:
push:
branches:
- master
# - preview
- preview

# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
Expand Down
23 changes: 13 additions & 10 deletions _articles/faq/chromium-142-local-network-access-issue.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,11 @@ last_modified: 2025-11-04 17:21:42 +0800
> [!IMPORTANT]
> This is a newly developing issue, and as such the information in this article may change over time.

## Error message - Access to fetch at `https://127.0.0.1:18623` or `http://127.0.0.1:18622` has been blocked by CORS policy: Permission was denied for this request to access the unknown address space.
## Error message - CORS Errors caused by local network access permissions when using Chromium 142 and later

### Symptom

When using Chromium-based browsers version 142 or later (released on October 28th, 2025), including Chrome, Edge, Brave, and Opera, the Dynamsoft Web TWAIN Service may fail to function properly:
When using **Chromium-based browsers version 142 or later** (released on October 28th, 2025), including Chrome, Edge, Brave, and Opera, the Dynamsoft Web TWAIN Service may fail to function properly:

- Phenomenon 1: the browser prompts users to download the service installer even though it is already installed.

Expand All @@ -41,22 +41,29 @@ This affects the Dynamic Web TWAIN Service which relies on local services for co

### Resolution

***Step 1: (For All End Users)***
***1. To Manually Correct This in Chrome***

- Navigate to your Dynamic Web TWAIN web interface

- Click the lock icon (or settings icon) next to your site URL in the browser’s address bar.

- Ensure that **Local Network Access** is enabled.

![local-network.png](/assets/imgs/local-network.png)

> [!NOTE]
> If you're unable to restore functionality after enabling 'Local Network Access,' please contact [Dynamsoft](https://www.dynamsoft.com/contact/).

***Step 2: (For Developers Only)***
***2. (For Administrators) To Apply This Setting Across an Enterprise***

Enterprise administrators can deploy a Chrome and/or Edge policy to set the "Local Network Access" setting to "Allow" for your website.

Please Refer to:
* [Chrome Enterprise Policy List & Management Documentation](https://chromeenterprise.google/policies/#LocalNetworkAccessAllowedForUrls)
* [Microsoft Edge Browser Policy Documentation](https://learn.microsoft.com/en-us/deployedge/microsoft-edge-browser-policies/localnetworkaccessallowedforurls)

**Option 1:**


***3. (For Developers) To Manually Check the Permission on Local Network Access***

You can check the permission programmatically:

Expand All @@ -74,10 +81,6 @@ If the permission is not granted, prompt users to manually enable it (Chrome set
<iframe src="..." allow="local-network-access *"></iframe>
```

**Option 2: (For Enterprise Users)**

Enterprise administrators can allow specified URLs to access local resources through Chrome’s Enterprise Policy configuration.
Refer to: [Chrome Enterprise Policy List & Management | Documentation](https://chromeenterprise.google/policies/#LocalNetworkAccessAllowedForUrls)

### Planning

Expand Down