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

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

Ocelot-Cloud 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.

When this occurs

This behavior has been observed in the following situations:

• when starting or stopping an app (including related operations such as backups, restores, or updates)
• when performing backup server settings operations that use a dedicated Docker container with SSH-related tools installed. The container must temporarily connect to and disconnect from Ocelot-Cloud Docker networks.

How this is handled

Because these Docker network changes are sometimes required, this behavior cannot be reliably avoided. To prevent these expected network interruptions from surfacing as user-facing errors, Ocelot-Cloud provides dedicated frontend request helpers for such operations. These helpers intentionally treat network-abort errors as a successful outcome and should be used for operations that may trigger Docker network reconfiguration.