> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reliantlabs.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix a Reliant machine that is offline or won't connect

> Get an offline Reliant machine working again: read what the chat says, check the daemon's stream, fix its credentials, and let the paused run resume.

This guide gets a chat's machine connected again and the run it stopped carrying on. Work through it when a chat says its machine is offline, a cloud machine stays on **Waking up…**, or a run has paused.

Every machine runs a daemon that dials out to Reliant and holds one stream open. `reliant daemon status` reports that stream, not just whether a process exists, so it tells you which link is broken ([how a tool call reaches your machine](https://docs.reliantlabs.io/deep-dives/how-tool-calls-reach-your-machine.md)).

## Before you begin

* The name of the chat's machine. The chat shows it, and **Settings → Machines** lists all of yours.
* For your own computer or server: a terminal on it, and the `reliant` CLI ([Installation](https://docs.reliantlabs.io/getting-started/installation.md)).

**1. Read what the chat says**

The message tells you where to look:

| The chat shows | What it means |
| - | - |
| **`<name>` is offline** | The daemon on that machine isn't connected |
| **Waking `<name>`…** | A suspended cloud machine is starting. Wait for it |
| **This chat's machine is no longer available** | The machine was deleted. Start a new chat on one you have |
| **Paused: this chat has been unable to reach its machine for two minutes.** | The run stopped calling tools on a missing machine. It continues by itself once the machine is back |

A run pauses only after three steps in a row failed to reach the machine over at least two minutes, so a short drop never stops it.

**2. On a cloud machine, check Settings → Machines**

Open **Settings → Machines** and look at the machine's status. Click **Resume** on a suspended machine. A machine that failed to start, or stays on **Waking up…** for many minutes, can be restarted from its page, or deleted and created again ([waking and suspending](https://docs.reliantlabs.io/machines/cloud.md#waking-and-suspending)). A cloud machine's logs aren't available to you, so the next steps are for your own computer.

**3. On your own computer, check the daemon's stream**

From the repository the daemon serves (or with `--workspace <path>`):

```bash terminal theme={null}
reliant daemon status; echo "exit=$?"
```

`status` exits `0` only when the stream is established and has held for two minutes. With no daemon running:

```text terminal theme={null}
No daemon running (no runtime record found)
  Record:   ~/.reliant/instances/https-api.reliantapi.com-c9232e15/_default/repo-a9712a99/daemon-state.json
daemon not running
exit=1
```

Start it with `reliant daemon start` ([connect your computer](https://docs.reliantlabs.io/guides/machines/connect-computer-as-machine.md)). A daemon that runs but has no credential says so:

```text terminal theme={null}
Daemon is running but has no usable credentials — waiting for sign-in
  PID:      4165557
  Stream:   awaiting_credentials for 13s
            never connected since this daemon started
  Error:    waiting for credentials to appear on disk
daemon gateway stream is not established (awaiting_credentials) — it can serve no tool calls
exit=1
```

If you run several daemons, `reliant daemon ls` lists every instance on the computer with its stream state:

```text terminal theme={null}
RUNNING  PID      STREAM                UPTIME  INSTANCE
-        4165557  awaiting_credentials  13s     https-api.reliantapi.com-c9232e15/_default/repo-a9712a99
```

**4. Read the daemon's log**

`reliant daemon logs` shows the last 50 lines and follows, but reads only the last 1 MB. For anything older, search the file itself, `logs/tools-daemon.log` beside the record `status` printed:

```bash terminal theme={null}
grep -E 'reconnecting|Gateway stream is dead|Rejected|Fatal error|claimed this daemon' \
  ~/.reliant/instances/*/*/*/logs/tools-daemon.log | tail -20
```

`Session ended; reconnecting` and `Gateway stream is dead` are drops the daemon recovers from by itself. `Rejected: credentials not accepted — retrying`, repeated, usually means the credential was revoked or the machine removed: go to the next step. `Fatal error — not reconnecting` means the daemon stopped, and the line says why.

**5. Re-register a daemon whose credential is refused**

From the repository, stop the daemon, move its credential aside, and pair the computer again:

```bash terminal theme={null}
reliant daemon stop
mv ~/.reliant/daemon.json ~/.reliant/daemon.json.old
reliant daemon start
```

`daemon start` prints a pairing code to approve in the app. On a server with no browser, give it a new token with `--token` instead ([run the daemon on your own server](https://docs.reliantlabs.io/guides/machines/run-agents-on-your-own-server.md)).

**6. Check that the machine is back and the run resumed**

Run `reliant daemon status` again. It now starts with `Daemon is running and its gateway stream is established` and exits `0`, and the machine shows as connected in **Settings → Machines**.

A paused chat resumes on its own when its machine connects. To retry sooner, send a message in the chat, or resume a run from the CLI with `reliant workflow resume <execution-id>`.

## What this does not do

* **Tool calls are not queued for an absent machine.** A call made after the daemon has been gone for 90 seconds fails at once.
* **A crash takes up to 90 seconds to show.** A clean `daemon stop` shows as disconnected immediately; a crashed daemon looks connected until 90 seconds pass without a heartbeat.
* **Tool calls don't wake a cloud machine.** Sending a message, or the check a run makes when it starts, wakes it.

## Troubleshooting

> [accordion] no daemon connected for user
>
> A tool call reached no daemon. Check the machine as above.

> [accordion] the machine this request asked for is not connected
>
> A workflow's `daemon:` names a machine that isn't connected, or that matches none of yours. Check the name and the kind in the workflow ([choose which machine runs each step](https://docs.reliantlabs.io/guides/machines/pin-workflow-to-machine.md)).

> [accordion] Your machine didn't come online within …
>
> The run waited for its machine when it started, and the machine never connected. In a chat the message ends `Your message is queued and will be sent as soon as your machine connects`, so start the machine and the message is delivered.

> [accordion] refusing to start: daemon PID … already runs in data directory …
>
> A daemon for this workspace is already running. Use it, or run `reliant daemon stop` first. To run a second daemon on purpose, give it its own `--data-dir`.

> [accordion] another daemon process claimed this daemon's identity …
>
> Two processes started with the same identity, and only one may hold it, so this one stopped. Run `reliant daemon ls`, stop the copy you don't want, and keep one.

> [accordion] daemon gateway stream is flapping — …
>
> The stream connects and drops again. Look in the log for the `Session ended; reconnecting` lines and their errors. A network that blocks long-lived HTTPS connections to `gateway.reliantapi.com` causes this.

## Next steps

> [card] [How a tool call reaches your machine](https://docs.reliantlabs.io/deep-dives/how-tool-calls-reach-your-machine.md)
>
> Heartbeats, reconnects, and exactly when a run pauses.

> [card] [Choose which machine runs each step](https://docs.reliantlabs.io/guides/machines/pin-workflow-to-machine.md)
>
> Pin a workflow, or one node, to a machine with `daemon:`.

> [card] [Run the daemon on your own server](https://docs.reliantlabs.io/guides/machines/run-agents-on-your-own-server.md)
>
> Keep a machine connected across reboots with systemd.

> [card] [Daemon security model](https://docs.reliantlabs.io/deep-dives/daemon-security-model.md)
>
> What the daemon's credential is and where it lives.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.