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

# Troubleshooting

> Fix common TinyCloud CLI, hosting, and OpenKey problems

Use this page to map a symptom to the next command or config check.

## No profile, key, or session

**Symptom:** `tc doctor` reports a missing profile, missing key, or missing session.

**Fix:** Start with profile setup and sign in.

```bash theme={null}
tc init
tc auth login
```

If you need a non-browser path, use local-key auth:

```bash theme={null}
tc auth login --method local
```

## Browser auth did not open

**Symptom:** `tc auth login` cannot open a browser callback.

**Fix:** Use paste mode or suppress the popup.

```bash theme={null}
tc auth login --paste
tc auth login --no-popup
```

If you are pointing at a self-hosted OpenKey instance, verify `TC_OPENKEY_HOST` or the profile's `openkeyHost`.

## Node health check fails

**Symptom:** `tc node health` says the node is unreachable.

**Fix:** Confirm the host and check the health endpoint.

```bash theme={null}
tc node health
curl http://localhost:8000/healthz
```

If you changed the node URL, check `TC_HOST` and the profile's `host` value.

## `tc doctor` and `tc node health` disagree

**Symptom:** `tc doctor` reports the node as unreachable, but `tc node health`
or a direct `/healthz` request succeeds.

**Cause:** The current CLI commands probe different paths: `tc doctor` checks
the legacy `/health` path, while `tc node health` checks the node's implemented
`/healthz` endpoint.

**Fix:** Use `tc node health` or `/healthz` as the node-health check and treat
the `tc doctor` node result as CLI drift. Continue using `tc doctor` for its
local profile, key, session, and space checks.

## Space is not hosted

**Symptom:** `tc kv` or `tc sql` reports that the target space is not hosted.

**Fix:** Host the owned space before retrying the data command.

```bash theme={null}
tc space create applications
tc space create secrets
```

Use `tc space info` or `tc space list` to confirm the resolved space URI.

## Secrets network is missing

**Symptom:** `tc secrets doctor` reports that the encryption network does not exist.

**Fix:** Create or reuse the default network.

```bash theme={null}
tc secrets network init
tc secrets network show
```

## A permission request is waiting

**Symptom:** You created a request artifact, but the action still fails.

**Fix:** Inspect local state and retry once the requested capabilities are covered.

```bash theme={null}
tc status
tc auth caps
tc auth retry --last
```

If a request still is not covered, grant or import the matching delegation artifact first.

## Where to look next

* `tc doctor` for a quick local diagnostic pass
* `tc status` for local profile and permission state
* `tc auth caps` for coverage details
* `tc secrets doctor` for secrets-specific checks

<Note>
  These fixes are based on the CLI's actual error hints and command behavior, not on hypothetical error codes.
</Note>