Skip to content
AnglinAI Docs

ERR_NETWORK_OFFLINE — Network Offline

HTTP Status: 0 (no HTTP response) Retryable: Yes Automatic retry: None. This is a client-side error — the request never reached the server.

What the User Sees

You appear to be offline. (ERR_NETWORK_OFFLINE)

What Causes This Error

The browser’s fetch() call threw a TypeError with “Failed to fetch” or “Load failed”, indicating the request could not be sent at all. This is detected entirely on the client side — no request reached the API server.

Common causes include: the user’s internet connection dropped (Wi-Fi disconnected, ethernet unplugged), a VPN connection was disrupted, a corporate proxy or firewall is blocking the request, the user’s DNS resolver cannot resolve the API domain, or the device is in airplane mode.

The error is distinguished from other network errors by the specific TypeError message pattern. A “Failed to fetch” error with no HTTP status code is the browser’s way of indicating a complete network failure, as opposed to a server returning an error status code.

Resolution Steps

For Users

  1. Check your internet connection. Try loading another website to confirm you have connectivity.
  2. If using Wi-Fi, verify you are connected to a network and have internet access.
  3. If using a VPN, try disconnecting it temporarily. Some VPNs block certain domains or have connectivity issues.
  4. If on a corporate network, check if a firewall or proxy may be blocking access to the API domain.
  5. Try refreshing the page after restoring connectivity.
  6. If on mobile, check that you have cellular data or Wi-Fi enabled.

For Administrators

  1. No admin action is needed — this is a client-side network issue.
  2. If many users report this simultaneously, check that the API domain’s DNS records are correctly configured and propagated.
  3. Verify the API is accessible from different networks to rule out a DNS or routing issue.
  4. If the error correlates with a CDN or DNS provider issue, check Cloudflare status.