Docs

When something is stuck

Each entry is written as what you see, then what to do.

Last updated September 9, 2026

The console says "registered, not connected"

The machine has a registration but has never reached us, or is not running right now. Check three things on it, in this order:

  1. Did the install command finish? Run it again and read the last few lines. It is safe to repeat.
  2. Can the machine reach the internet outbound? Nothing has to reach it, but it has to be able to reach out.
  3. Was the token copied in full? A truncated token registers nothing. If in doubt, revoke it in the console and register the machine again.

If the console says "connected before, offline now" instead, the machine is installed but not running. Start it there and it reconnects on its own.

Sessions will not start

Almost always the Claude sign-in: the machine is connected, but the account that runs sessions has never authorized. Connect your Claude subscription. Note that it has to be the service account, not root and not your own user.

The other cause is memory. A machine with no room left refuses a new session rather than slowing everything down. Close a session, or give the machine more memory.

You hit the concurrency limit

A new session is refused the moment it would exceed the limit. Sessions already running are not affected. Close one, or run it on a machine of your own. How the limit works.

Still stuck?

Write to us with what you see on the screen and we will answer within one business day. Enterprise self-hosting goes through the same address.

support@roamai.cloud

Or add us on WeCom. The QR code is at the bottom of every page.