Skip to main content
Failed to fetch is a browser-level network error — it means your browser blocked or dropped a request before it reached Omni. If a page refresh fixes it, the cause was likely a brief internet drop. If the error is consistent or reproducible, work through the steps below to find the cause.

Scope the problem first

Before troubleshooting, answer these questions — they’ll tell you which step to start with and what to tell support if you need to escalate.
QuestionWhy it matters
Is it one user or multiple?Multiple users points to a network or Omni configuration issue, not a browser extension
Is it one dashboard or everywhere in Omni?Scoped to one dashboard suggests a specific query or data connection; everywhere suggests a browser or network issue
Is it in an embedded context or directly on omniapp.co?Embed adds iframe and cookie restrictions that can trigger this error
Is it consistent or intermittent?Intermittent errors often indicate network instability (VPN drops, weak Wi-Fi); consistent errors point to a blocked request

Steps

1

Disable browser extensions

Ad blockers, privacy tools, and VPN browser extensions are the most common cause of Failed to fetch errors. They intercept network requests and can silently block calls to Omni’s servers.
  1. Open a private or incognito window — extensions are disabled by default in most browsers’ private modes.
  2. Log in to Omni and reproduce the action that caused the error.
  3. If the error is gone, a browser extension is the cause. Re-enable your extensions one at a time in a normal window to identify the specific culprit.
Common offenders include uBlock Origin, Privacy Badger, Ghostery, and any extension marketed as an ad blocker or tracker blocker.
2

Test on a different network

Corporate networks — including firewalls, proxies, and content filters — can block requests to Omni’s servers even when Omni is working correctly.
  1. Connect to a mobile hotspot or a non-corporate network.
  2. Log in to Omni and reproduce the action.
  3. If the error is gone on a different network, the issue is with your corporate network. Your IT team will need to allowlist Omni’s IP addresses in your firewall or proxy.
Omni’s IP addresses are listed on each connection’s settings page. Navigate to Settings > Connections, click a connection, and copy the IP addresses shown. See Allowlisting Omni’s IP addresses for details.
VPNs can cause intermittent Failed to fetch errors even outside a corporate network. If the error appears and disappears, try disabling your VPN first.
3

Inspect the browser Network tab

If the first two steps don’t resolve the error, use your browser’s developer tools to capture exactly which request is failing and why.To open the Network tab:
  • Chrome / Edge: Press F12 (or Cmd+Option+I on Mac), then click the Network tab
  • Firefox: Press F12, then click Network
  • Safari: Enable the Develop menu under Safari > Settings > Advanced, then press Cmd+Option+I and click Network
What to look for:
  1. Clear the Network tab log, then reproduce the error.
  2. Filter by XHR or Fetch requests.
  3. Look for requests with a red status, (canceled), (blocked), or status codes in the 4xx/5xx range.
  4. Click the failing request and open the Headers tab.
What to capture for escalation:
  • The full request URL
  • The response status (or the error message if blocked)
  • Any net::ERR_* message shown in the status column (e.g. net::ERR_BLOCKED_BY_CLIENT typically indicates a browser extension or firewall block)

Escalating to support

If the steps above don’t resolve the error, contact Omni support with the following:
  • Browser and version (e.g. Chrome 125, Safari 17.4)
  • List of browser extensions installed, or a screenshot of your extensions list
  • Network tab screenshot showing the failing request, with the Headers panel open (request URL, response status, and any error message visible)
  • Scope: whether the error is on one dashboard or everywhere, and whether it affects one user or multiple
  • Network context: whether it reproduces on a different network or with VPN disabled

Next steps