Troubleshooting

The application cannot reach the coordinator

1. Confirm the coordinator URL in Settings.
2. Use https:// and wss:// when the coordinator is not loopback.
3. Check that DNS, the certificate, and the coordinator port are reachable from this machine.
4. If this is a private network, confirm that the coordinator allows the machine or invitation being used.

The node is connected but does not execute work

Connection and execution are separate states.

1. Open This machine and confirm contribution is enabled.
2. Check the local runtime status and any repair message.
3. Confirm that a verified model deployment is attached to the node.
4. Inspect whether the scheduler selected another route with better memory, latency, or availability.

Do not infer active GPU execution from hardware detection alone.

No models appear

GET /v1/models returns registered deployments, not every model file visible on disk. Confirm that the runtime:

• loaded the configured model revision;
• passed health and generation canaries;
• registered with the same coordinator the client is querying;
• remains within its heartbeat and capacity limits.

The browser worker stops

Mobile and desktop browsers can suspend background tabs.

• Keep the worker page visible.
• Accept the wake-lock request when the platform offers it.
• Disable battery-saving restrictions for a temporary test.
• Use the native application for persistent contribution.

The operating system warns about the installer

Early builds may not yet carry the final platform signature or notarization. Download the package only from mycellios.com or the official GitHub release. If the checksum or origin cannot be verified, do not run the package.

A request times out

Reduce the prompt or max_tokens, increase deadline_ms only when the caller can still use a later response, and inspect the selected route for an unhealthy stage. A longer timeout does not repair a route with failed health checks.