升级后持续 pairing required：按 token/模式/进程三层排查并准备回滚

问题/场景：升级到 2026.2.19-2 后，CLI 普遍报 `gateway closed (1008): pairing required`，即使网关进程存活。前置条件：已启用 token 鉴权且本地 gateway 正常启动。实施步骤：先核对 `gateway.auth.mode/token` 与运行时一致 → 执行 stop/start + install + doctor --fix 验证是否仅服务层异常 → 用最小配置重启并隔离旧会话/旧 token 影响 → 仍失败则按版本回滚并附环境信息提交 issue。关键命令：`openclaw gateway status`、`openclaw doctor --fix`。验证：`openclaw health/status/sessions_send` 均恢复成功。风险：跨版本 token/状态迁移可能异常，生产升级需保留回滚窗口。来源：Issue #21236 + related #21267/#16305。

GITHUBDiscovered 2026-02-20Author rpalma

Prerequisites

OpenClaw has just been updated to 2026.2.19-2 or nearby builds and previously worked with token auth.
You can run local diagnostics and inspect gateway config/service status.

Steps

Confirm process vs auth state separately: `openclaw gateway status`, `openclaw status`, `openclaw health`.
Restart gateway lifecycle end-to-end (`stop/start/install/doctor --fix`) and compare whether only doctor path fails.
Re-validate `gateway.auth.mode=token`, token length/value source, and local bind mode (`gateway.mode=local`, `bind=loopback`).
If still blocked, isolate with minimal config and test `sessions_send`; then rollback to last known good version and collect repro logs.

Commands

openclaw gateway status

openclaw health

openclaw doctor --fix

openclaw gateway stop && openclaw gateway start

Verify

`openclaw health` no longer returns pairing errors, and inter-agent/session commands succeed after restart.

Caveats

Do not overwrite production token/config blindly; back up current config before rollback.
Root cause is still under issue investigation and may vary by environment（需验证）.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post