'NETWORK_CHANGED' error and 'TypeError: Failed to fetch'

Mon, 01 Jan 0001 00:00:00 +0000

During some operations such as starting an app, browsers may report a NETWORK_CHANGED or TypeError: Failed to fetch error. This is expected behavior and does not indicate a failed operation.

Why this happens

Quollix runs inside a Docker container and dynamically connects to and disconnects from app-specific Docker networks during certain operations. If a browser request is in flight while Docker reconfigures the container’s network, the browser may abort the request and report one of the above errors, even though the backend operation completes successfully.

OpenCloud integration issues

Mon, 01 Jan 0001 00:00:00 +0000

Quollix acts as the reverse proxy in front of OpenCloud. OpenCloud uses a mandatory OpenID Connect (OIDC) authentication flow. Even when using local users (IDM), OpenCloud always authenticates via its internal OIDC provider. Because of this, OpenCloud must be able to reach its own OIDC discovery endpoint at the URL defined by OC_URL.

During authentication, OpenCloud performs OIDC discovery and token validation requests from its own container to the URL defined by OC_URL. These requests are routed through the reverse proxy (Quollix) and then forwarded back to the OpenCloud service itself. This internal request loop only happens during authentication, but it is the source of most issues in local, containerized setups.

Special Cases on Quollix

'NETWORK_CHANGED' error and 'TypeError: Failed to fetch'

Why this happens

OpenCloud integration issues