Skip to main content

Troubleshooting

Accessing the console​

The console is stuck loading​

If the Onehouse console (https://cloud.onehouse.ai) loads but never finishes — you see a blank screen or an endless loading spinner — and this happens while you are connected to a corporate VPN or running endpoint-security / zero-trust (ZTNA) software, you are most likely hitting a browser security feature called Local Network Access, introduced in Google Chrome 142 (and Chromium-based browsers such as Microsoft Edge).

This affects any console page when it is reloaded, not just the sign-in page, because every page load re-contacts the Onehouse API.

What is happening​

The console calls the Onehouse API at https://cloudapi.onehouse.ai. Some VPN, zero-trust, or endpoint-security tools — for example Zscaler, Netskope, Cisco Umbrella, Cloudflare WARP, Palo Alto GlobalProtect, or Jamf Trust — intercept this traffic and route it through a local address on your machine. Starting in Chrome 142, a public website is not allowed to reach a local network address without your permission, so the API call is blocked and the page never finishes loading.

To confirm, open your browser developer tools (View → Developer → Developer Tools, then the Console tab) and reload. You will see an error similar to:

...has been blocked by CORS policy: Permission was denied for this request to access the local address space.

How to fix it​

Try these in order:

  1. Allow the permission prompt. If Chrome shows a prompt asking to allow access to your local network, click Allow, then reload the page.
  2. Add Onehouse to your security software's bypass list. Ask your IT team to exclude *.onehouse.ai (or at least cloudapi.onehouse.ai) from interception in your VPN, zero-trust, or endpoint-security agent. This is the most reliable fix and resolves it for everyone on your network.
  3. Confirm the cause. Try the console from an incognito/private window with extensions disabled, a different browser, or off the corporate network (for example, a phone hotspot). If it loads in any of these, your network-security software is the cause and step 2 is the fix.

If the console still does not load after trying these steps, contact Onehouse Support and include a screenshot of the browser console error above.