--- title: "Troubleshooting" description: "Errors you can see from ochost and in the browser, and what to do for each." --- > Documentation Index > Fetch the complete documentation index at: https://oc-workers.mdick85.workers.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting An `ochost` error is one line: `Failed: — fix: `. ## From the CLI | You see | Do this | |---|---| | `Node 22.18 or later is needed` | Install Node 22.18 or later, check with `node -v`, and rerun. | | `Docker is not running` | Start Docker, check with `docker info`, and rerun. | | `wrangler is not logged in` | Run `npx wrangler login`, then rerun `ochost init`. | | `account is not on Workers Paid` | Upgrade at the link in the line (the plan is $5 a month), then rerun. | | `R2 is not enabled on this account` | Enable R2 in the dashboard, then rerun. | | `no workers.dev subdomain` | Rerun with `--subdomain `. | | `an oc-host install already runs as ` | Run `ochost init --adopt`, or pick another `--name`. | | `gateway does not exist` | Rerun with `--gateway default`, which Cloudflare makes on first use, or with `--gateway none`. | | `anthropic/ did not answer through the gate ()` (from `ochost model set`) | The gateway has no Anthropic key. Add it with the steps below, then rerun. | | `the gate did not answer (404)` | The Worker is older than this CLI. Run `ochost deploy`. | | `the OpenClaw config still calls the AI Gateway with the old AI token` (from `ochost deploy`) | The install was made before oc-workers stopped using an AI token. Run `ochost ai-gateway setup --restart`, which points the model at the gate. | | `the token lacks AI Gateway: Run` (only with `--ai-token-file`) | Add that permission to the token, or drop the flag. | | `retry n of 3: blob unknown` | Nothing; `init` retries. | | `image push kept failing (3 retries)` | Rerun `ochost deploy`. Pushed layers are kept. | | `the install did not start in 10 min` | Run `ochost status`, then rerun `ochost init`. A rerun is safe. | | `config changed elsewhere (base N, current M)` | Run `ochost config pull`, then set again. | | `Telegram rejected the token` | Copy the token from @BotFather again. | | `a second Telegram bot is not supported in v1` | Run `ochost channels remove telegram` first (it also accepts `--yes`). | | `Telegram webhook not set after 3 min` | Run `ochost logs --source ocsup`, then `ochost restart`. | | `no pairing request in 10 min` | Send a direct message to the bot, then run `ochost pairing approve telegram `. | | ` is a channel secret` or ` is a managed secret` (from `ochost secrets set`) | Use the command in the fix line. | | ` changes the state schema` | Stay on the pinned version. See [Upgrades](https://oc-workers.mdick85.workers.dev/docs/upgrades/). | | `image contract failed for ` | The new image failed its contract test, so the upgrade stops. Stay on your version. The test is in the `image/test` folder of the repo. | | `rolled back to (upgrade failed: ...)` | Run `ochost logs --source rt` and `ochost upgrade check`. | | `no oc-host install in ` | Run `ochost init`, or `ochost init --adopt`. | | Any other `Failed:` line | Rerun with `OCHOST_DEBUG=1` and report the output. | ### Add an Anthropic key to the gateway 1. Open `https://dash.cloudflare.com/?to=/:account/ai/ai-gateway`. 2. Select your gateway (`default` unless you chose another), then **Provider Keys**. 3. Select **Add API Key**, choose **Anthropic**, paste your key and give it the alias `default`. Only the `default` alias is used on this path. 4. Select **Save**. 5. Run `ochost model set anthropic/`. It sends one test message and refuses the change if the gateway has no key. ## In the browser | You see | Do this | |---|---| | The page "Link used or expired" | A login link works once and lasts 5 minutes. Run `ochost open`. | | "OpenClaw is waking up. Reload in a few seconds." | Nothing. The page shows the wake phase and reloads when the install runs. | | "offline" in an idle Control UI tab | Reload the page. The OpenClaw UI shows this when a tab was closed for being idle. | | Error 1101 on a page while the install sleeps | See [The 1101 page](#the-1101-page). | | `bad origin` when you log in with Firefox | See [Firefox login](#firefox-login). | ### The 1101 page An older Worker could fail with Cloudflare Error 1101 on a proxied path while the install went to sleep. The current Worker answers with the waking page instead (status 503 with `Retry-After: 5` for non-page requests), so update your clone and run `ochost deploy`. ### Firefox login An older Worker refused the login form post from Firefox with 403 `bad origin`, because Firefox sent `Origin: null`. The current Worker accepts a missing or `null` Origin when `Sec-Fetch-Site` is `same-origin`, so update your clone and run `ochost deploy`. Until then, run `ochost open` and use the link. ## Known rough edges | You see | Meaning | |---|---| | `alerts db-unclassified (warn)` in `status` on a new install | Harmless: the image scan flags a temp file. | | `status`: `degraded (disk-full)` | The container disk is 95 % full. Free space or raise the disk size. The state clears when use drops under 90 %. `disk-high` (80 %) is a warning only. | | A Telegram update shows as `dead` in `status` | The gateway answered it with 404 or 501 five times over at least 5 minutes. A dead row no longer keeps the install awake. | | `doctor`: `state WARN running, start ladder level 1` | No action. The start ladder counts failed starts, and a normal first start can leave it at level 1. | | `.oc-host/wrangler.jsonc` has absolute paths into the clone | Keep the clone where it is. If you move it, rerun `ochost init`. | | `ochost status` shows one cost value on a new install, not a range | Normal until the install has history. | | Deploy fails with `Timed out while preparing the container image` or `Unauthorized` | A registry problem. Rerun `ochost deploy`. | ## Logs ```sh ochost logs --source ctl ochost logs --source rt ochost logs --source ocsup ochost logs --source gate ochost logs --source alert ``` `ctl` is the Control DO, `rt` the Runtime DO that runs the container, `ocsup` the supervisor in the container, `gate` container log lines and gate events, and `alert` the alerts sent. To see alerts in the browser, open the Alerts and log tab of the owner console. ## npm warns about blocked install scripts `npm install -g oc-workers` can print `install scripts blocked` for `esbuild` and `workerd`, because npm 12 blocks post-install scripts it has not seen. The CLI and wrangler work without them. To clear the warning: ```sh npm install-scripts approve esbuild workerd ``` ## Next Go to [CLI reference](https://oc-workers.mdick85.workers.dev/docs/cli-reference/). Source: https://oc-workers.mdick85.workers.dev/docs/troubleshooting/index.mdx