#Error after updated
1 messages · Page 1 of 1 (latest)
First thing: please paste the output of:
openclaw --version
openclaw status --all
openclaw gateway status
After a jump from 4.20 to current, also run:
openclaw doctor
openclaw gateway restart
openclaw logs --follow
If logs --follow can’t connect, use:
tail -n 120 "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)"
Docs for the update/triage path:
https://docs.openclaw.ai/install/updating
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/gateway/troubleshooting
Paste the first real error stack or redacted status --all output and we can narrow it down.
i cant paste here cause its too much
No worries. Don’t paste the whole thing.
Please run these and paste only the output/error lines:
openclaw --version
openclaw status
openclaw gateway status
openclaw doctor
For logs, grab just the recent errors:
openclaw logs --json --plain | tail -n 300 | rg -i "error|fatal|exception|failed|cannot|denied|1008|eaddr|enoent"
If that’s still huge, upload it as a .txt file here, or paste only the first error stack and the last ~40 lines before the gateway stops/restarts. Make sure to redact tokens/API keys if you see any.
i cant paste .txt hre
Got it. Then shrink it on your machine and paste only the tiny filtered result:
openclaw --version
openclaw status | head -n 80
openclaw gateway status | head -n 80
openclaw doctor | tail -n 80
For logs, this should produce a much smaller chunk:
tail -n 500 "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)" | rg -i "error|fatal|exception|failed|cannot|denied|1008|eaddr|enoent" | tail -n 80
If even that is too much, paste just:
- your
openclaw --version
- the first line that says
error/fatal - the 20 lines immediately after it
15:03:02 [gateway] loading configuration…
15:03:02 [gateway] resolving authentication…
15:03:02 [gateway] starting...
15:03:03 [gateway] wrote stability bundle: /Users/eve/.openclaw/logs/stability/openclaw-stability-2026-05-15T07-03-03-642Z-63054-gateway.startup_failed.json
15:03:03 Gateway failed to start: Invalid config at /Users/eve/.openclaw/openclaw.json.
channels.discord.streaming: invalid config: must be object
channels.discord.accounts.default.streaming: invalid config: must be object
That one is a config migration issue. Your config has old Discord streaming values as a scalar/string/boolean, but current startup validation wants an object.
Try the safe repair first:
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak.$(date +%Y%m%d-%H%M%S)
openclaw doctor --fix
openclaw gateway restart
If it still fails, manually edit ~/.openclaw/openclaw.json and change both of these if present:
channels: {
discord: {
streaming: { mode: "off" },
accounts: {
default: {
streaming: { mode: "off" }
}
}
}
}
If yours currently says something like streaming: "partial", use streaming: { mode: "partial" } instead. If it says streaming: true, use { mode: "partial" }; if false, use { mode: "off" }.
Then run:
openclaw doctor
openclaw gateway restart
Config reference: https://docs.openclaw.ai/gateway/configuration-reference#discord
is there a way i can rewind my version?
Yes. First check how it’s installed:
openclaw --version
which openclaw
If it’s a global package install, pin the older version:
pnpm add -g openclaw@4.20.0
openclaw doctor
openclaw gateway restart
If 4.20.0 is not the exact published version you had, list available versions with:
pnpm view openclaw versions --json
If it’s a source/git install, rewind the checkout instead:
cd /path/to/openclaw
git fetch origin
git checkout <old-commit-or-tag>
pnpm install
pnpm build
openclaw doctor
openclaw gateway restart
I’d still keep the config backup you made, because newer versions may have already migrated ~/.openclaw/openclaw.json. Rollback docs: https://docs.openclaw.ai/install/updating#rollback
how do i know which version i updated from?
A few places to check:
openclaw --version
That only shows the current version. For the previous one, try:
# shell history often has the install/update command
history | rg "openclaw|npm|pnpm|update|install"
# if you used pnpm globally, check store/package-manager traces
pnpm view openclaw versions --json | rg "4\.20"
# if you have a source/git install
cd /path/to/openclaw
git reflog --date=iso | head -40
Also check whether OpenClaw wrote a stability/update bundle around the time you updated:
ls -lt ~/.openclaw/logs/stability | head
rg -i "version|update|4\.20|openclaw@" ~/.openclaw/logs ~/.openclaw/logs/stability
From your first message, it sounds like you were on 4.20.x. If you don’t know the exact patch, run:
pnpm view openclaw versions --json | rg '"4\.20'
Then pin the closest one, for example openclaw@4.20.0 or whatever exact 4.20.x exists.
no i forgot which version i updated from
You may not be able to recover the exact old version if there’s no history/log entry. That’s okay — you usually don’t need the exact one.
Since you remember “4.20”, find the available 4.20 releases and install the newest patch in that line:
pnpm view openclaw versions --json | rg '"4\.20'
Then pick the highest one shown, for example:
pnpm add -g openclaw@4.20.x
openclaw doctor
openclaw gateway restart
Replace 4.20.x with the exact version from the list.
If you want one last chance to identify what you had before, check shell history and OpenClaw logs:
history | rg "openclaw|pnpm|npm|install|update"
rg -i "openclaw@|version|update" ~/.openclaw/logs ~/.openclaw/logs/stability
But if those don’t show it, just pin the newest 4.20.x release.
ok i know its 4.2 version, how should i rewind
If you mean 4.2.x exactly, do this:
# 1. Back up config first, because the newer version may have migrated it
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak.$(date +%Y%m%d-%H%M%S)
# 2. See exact 4.2 versions available
pnpm view openclaw versions --json | rg '"4\.2'
# 3. Install the highest exact 4.2.x shown, example:
pnpm add -g openclaw@4.2.x
# 4. Repair/check and restart
openclaw doctor
openclaw gateway restart
openclaw --version
Replace 4.2.x with the exact version from the list, like 4.2.3 if that’s what exists.
Small warning: if you meant 4.20.x instead of 4.2.x, don’t install 4.2.x — that’s much older. Use the same command but search/install 4.20:
pnpm view openclaw versions --json | rg '"4\.20'
pnpm add -g openclaw@4.20.x
its "2026.4.2" how should i use the command
Use the exact version after the @:
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak.$(date +%Y%m%d-%H%M%S)
pnpm add -g openclaw@2026.4.2
openclaw doctor
openclaw gateway restart
openclaw --version
If pnpm add -g says the version doesn’t exist, check the exact published spelling:
pnpm view openclaw versions --json | rg '"2026\.4\.2'
If your original install was npm-global instead of pnpm-global, the equivalent is:
npm i -g openclaw@2026.4.2
openclaw doctor
openclaw gateway restart
But use pnpm first unless you know you installed with npm.
eve@Eves-Mac-mini ~ % openclaw onboard
Invalid config at /Users/eve/.openclaw/openclaw.json:\n- agents.defaults.models.openai/gpt-5.4: Unrecognized key: "agentRuntime"
- agents.defaults.models.openai/gpt-5.1-codex-mini: Unrecognized key: "agentRuntime"
- agents.defaults.models.openai/gpt-5.3-codex: Unrecognized key: "agentRuntime"
- agents.list.0: Unrecognized key: "models"
- agents.list.1: Unrecognized key: "models"
- agents.list.2: Unrecognized key: "models"
- agents.list.3: Unrecognized key: "models"
- messages.groupChat: Unrecognized key: "visibleReplies"
- channels.discord.threadBindings: Unrecognized key: "spawnSessions"
🦞 OpenClaw 2026.4.2 (d74a122) — I can run local, remote, or purely on vibes—results may vary with DNS.
Config invalid
File: ~/.openclaw/openclaw.json
Problem:
- agents.defaults.models.openai/gpt-5.4: Unrecognized key: "agentRuntime"
- agents.defaults.models.openai/gpt-5.1-codex-mini: Unrecognized key: "agentRuntime"
- agents.defaults.models.openai/gpt-5.3-codex: Unrecognized key: "agentRuntime"
- agents.list.0: Unrecognized key: "models"
- agents.list.1: Unrecognized key: "models"
- agents.list.2: Unrecognized key: "models"
- agents.list.3: Unrecognized key: "models"
- messages.groupChat: Unrecognized key: "visibleReplies"
- channels.discord.threadBindings: Unrecognized key: "spawnSessions"
Run: openclaw doctor --fix
eve@Eves-Mac-mini ~ %
That means the rollback worked, but your openclaw.json is now from the newer version. Older 2026.4.2 doesn’t know those newer config keys.
Do this first:
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.newer-backup.$(date +%Y%m%d-%H%M%S)
openclaw doctor --fix
openclaw doctor
openclaw gateway restart
If doctor --fix can’t repair it, restore the config backup from before you updated. Check what backups you have:
ls -lt ~/.openclaw/openclaw.json*