Local Network Access Permission: Browser Requirements for Ranger Remote (2026)
A number of browsers, including Chrome, Edge, Firefox are gradually introducing stricter permission requirements for web applications and websites that access the local network and user devices.
Going forward, users may be prompted by their browser to explicitly allow the website or web application to access the device. This permission is required for the application to communicate with the local Ranger Remote service.
Recommendation
We recommend users upgrade to the Chrome and Edge versions 147+ if they are already above version 142.These new measures are being introduced broadly and affect any application that attempts to access a physical device connected to the user’s workstation through the local network. These changes do not indicate a security vulnerability. Instead, they introduce an additional security control for users.
Please consider the following regarding how this might affect the Ranger Remote service:
1. Users should only be prompted once and the decision should persist between sessions for the application. To be able to communicate with the Ranger Remote service, the end user will need to select "Allow" for Apps on Device
|
Example prompt seen in Google Chrome and Microsoft Edge |
2. Users can also change the Apps on Device permission, by clicking the site information icon.
| |
Google Chrome example | Microsoft Edge example |
Recommendation
For those that do not get prompted by their browsers, please check the site information icon on the left, to make sure a previous decision did not inadvertently disable the "Apps on Device" access
The tab might need to be restarted if the Apps on Device permission is changed via this option, before the new permissions take effect.
3. Your specific Policy or HTTP use (instead of HTTPS) can block browsers from prompting you:
- It is important that there is no policy blocking you to receive the prompt.
- You can verify the policies by Chrome://policy or Edge://policy section
- Browsers might block prompting you about Apps on Device IF the browser communicates with the app over HTTP instead of HTTPS
4. Users can also permanently disable the new Local Network Access for WebSockets restriction measures by disabling the flag via the browsers settings. We don't recommend this as a permanent solution, but as a temporary work around until the browser update.
|
| Google Chrome example |
|
Microsoft Edge example |
Related Articles
Secure communications with Ranger Remote
RangerRemote involves inter-process communication between a Ranger host application (Ranger Remote server) and a Ranger client running in a browser. The most commonly used method of portable inter-process communication with a browser is a websocket ...
What is Ranger Remote?
Ranger® Remote is Silver Bullet's cross-platform/cross-browser solution for the Ranger Universal Check Scanner API™ family. Ranger Remote is a powerful tool, available on both Windows and MAC OS platforms, allowing browser-based applications to ...
What are Ranger's minimum PC system requirements?
What are Ranger's minimum PC system requirements? Ranger has the same system requirements as the check scanner it is used with. The minimum system requirements for a particular check scanner are available from the scanner manufacturer. Operating ...
How do I capture and send an internet browser's log to support?
Here are the steps to capture and send a browser console log to Silver Bullet technical support. Start console logging: Open the Developer Tools for your browser. This can be done so in the following ways: Access it through Options>Tools Press F12 ...
How to point Ranger at a Ranger Remote service running on a different PC
By default, an insecure loopback URL is used for the socket connection between Ranger and Ranger Remote, listening on port 9002. The IP Address for local loopback is ?127.0.0.1?. In order to override the target IP address of the Ranger Remote ...