Network and proxy (my browser works but Omniscio doesn't)
If your browser works and Omniscio cannot reach anything, the network is blocking the app's own outbound calls. Omniscio needs direct HTTPS access; ask IT to allow the hosts listed below, or use a network that has direct access.
What it is
A network — usually a work laptop, a corporate proxy, or a firewall that inspects HTTPS traffic — that lets your browser out but blocks the addresses Omniscio calls. Every session and AI helper then fails with a network error while everything else on the machine looks fine.
This is not the same as being offline. The offline banner watches whether your computer has a working internet connection; when the connection is healthy and only the app's calls are refused, the banner correctly stays quiet. That silence is why this page exists.
What you will see
- The browser loads normal websites, and other apps on the machine work.
- Every session fails with a network or connection error, often within seconds.
- AI helpers (Ask Omniscio, summaries, voice) fail the same way.
- The amber "You are offline" banner never appears, because you are not offline.
- Signing in, or anything that reaches Omniscio's own servers, may fail on a different machine than at home, while working at home and failing at the office.
Why it happens
Omniscio makes its own calls to the internet, separately from your browser, and it has no proxy setting. Those calls go through the standard Node HTTPS stack, which does not use the operating system's proxy configuration. So on a machine where a proxy is the only route out, the browser succeeds and Omniscio cannot connect at all.
What the app needs to reach
If you are the person who can change the network rules, allow these over HTTPS (443), with no HTTPS inspection or TLS break-and-inspect on them:
api.anthropic.com— the Claude API every session runs on.identitytoolkit.googleapis.comandsecuretoken.googleapis.com— Omniscio sign-in and token refresh.firestore.googleapis.com— synced data, Team Chat, and shared records.us-central1-agentmc-shares.cloudfunctions.net— Omniscio's backend functions.amcback.jls.dev— Help Desk and Team Chat relay.releases.omniscio.comanddl.omniscio.com— updates and installers.
A network that only allows a fixed list should allow the whole set; allowing the browser's addresses alone is not enough, because the app never uses the browser's connection.
What to do
- Try a different network first. Join a phone hotspot or a home connection and start a session. If it works there, the network is the cause and the rest of this page applies.
- Ask IT to allow the hosts above, or to give this machine direct outbound HTTPS on 443. This is the fix that keeps everything else on the network unchanged.
- If IT cannot allow them, run Omniscio on a machine or network that has direct access. Sessions, sign-in and updates all need the same route out, so a partial exception usually shows up as a different failure later.
- Do not spend time reinstalling. A blocked network reinstalls the same way it installed: the app is fine, and the connection is the problem.
If the allow-list is in place and sessions still fail, the network is inspecting HTTPS traffic rather than blocking it. Ask IT to exempt the hosts above from inspection; an intercepting proxy replaces the certificates and the app will refuse those connections on purpose.
Related
See also
- Offline banner — the honest "your connection is down" signal, and why it stays quiet here.
- Something's not working? Start here — the symptom router if this does not match what you see.
Last verified 2026-11-10