With the release of Chrome version 142, Google has introduced a new permission prompt for websites that attempt to connect to devices on a user’s local network. This change, part of the Local Network Access specification, is designed to enhance security by preventing unauthorized requests to devices within your network.
As a result, direct access to local IP addresses from public websites is now deprecated. Instead, Chrome v142 will require users to explicitly grant permission when a website attempts to access local network resources.
Our Embedding SDK, which is integrated into your web page, sends requests to the Library server. If your Library server is hosted on your local network, previous versions of Chrome allowed this connection seamlessly. However, starting with Chrome v142, the browser will prompt you to grant permission the first time you use this feature.
What to Expect:
You need to click “Allow” button, then the embedding SDK can work correctly.
On the contrary, if you click “Block”, or close the pop-up, the iframe embedding will fail as below:
If you had blocked local network access on Chrome v142 for this website before, the pop-up will not appear, and you will get the error directly.
If you encounter this error, you can still modify the Chrome settings to resolve it.
For a specific website’s permission change, you can enter in chrome://settings →
Privacy and security→
Site settingsto change. Find the target site and change its specific settings:
Clicking the “Allow“ above is the same as clicking “Allow“ on the pop-up, which only grants local network access permission to this public website.
If you want to revert to the original Chrome’s behavior, you can change the setting for all websites in Chrome by disabling the flag
local-network-access-checkin chrome://flags.
