Overview
If you are using macOS, Chrome 148+, and accessing Olares via an olares.com URL with LarePass VPN enabled, the Olares interface will load successfully, but real-time updates (app status, notifications, task progress, and live panels) will fail to refresh.
Please be assured that your data is completely safe; this issue only affects the browser’s WebSocket connection. We have identified the root cause and a fix will be included in the next Olares release.
Cause
Chrome 148 enforces stricter Local Network Access (LNA) checks for cross-origin requests that resolve to local or private network addresses. For WebSocket upgrades, Chrome now requires the Access-Control-Allow-Private-Network: true header in the 101 Switching Protocols response. If this header is absent, Chrome blocks the connection.
When LarePass VPN routes your olares.com traffic to a local address, Chrome applies these LNA rules to the WebSocket connections. Because the current version of Olares does not include this newly required header in the upgrade response, the connection is rejected. The main page loads over standard HTTPS, which is why the interface appears normal initially but does not receive subsequent updates.
Workarounds
Option 1 — Disable Chrome’s LNA check
-
Open
chrome://flags/#local-network-access-checkin your Chrome browser. -
Set Local Network Access Checks to Disabled.
-
Click Relaunch.
-
Re-open Olares with your usual
olares.comURL.
Note
This disables a built-in browser security feature. We strongly recommend changing this flag back to Default or Enabled once you have upgraded to the fixed Olares version.
Option 2 — Switch to the .local URL
If your Mac is connected to the same local network as your Olares device, you can use the .local domain to access Olares services directly:
-
Replace:
https://<entrance_id>.<username>.olares.com -
With:
http://<entrance_id>.<username>.olares.local
If Chrome refuses to load the .local URL on macOS:
-
From the Apple menu, open System Settings.
-
Navigate to Privacy & Security > Local Network.
-
Enable permissions for Google Chrome (and Google Chrome Helper if present).
-
Restart Chrome and try again.