Bug: device token mismatch after container recreation (2026.2.15)
Bug: device token mismatch after container recreation (2026.2.15)
After recreating my Docker container (docker compose down/up), the agent can't authenticate with its own gateway. Every tool call fails with:
What I've tried:
- Deleted /identity and /devices directories (from host volume while container stopped)
- Updated from 2026.2.14 to 2026.2.15
- Multiple docker compose down/up cycles
- Manually editing paired.json
- Running
Fresh device.json generates on each boot, no devices/ directory exists, no cached deviceToken anywhere on disk — but agent still gets rejected by its own gateway.
Setup: Docker container, gateway + agent same process, Tailscale networking, explicit auth token configured.
Anyone seen this? Is there a way to force re-pairing the internal agent
gateway connection?
After recreating my Docker container (docker compose down/up), the agent can't authenticate with its own gateway. Every tool call fails with:
gateway closed (1008): unauthorized: device token mismatch (rotate/reissue device token)What I've tried:
- Deleted /identity and /devices directories (from host volume while container stopped)
- Updated from 2026.2.14 to 2026.2.15
- Multiple docker compose down/up cycles
- Manually editing paired.json
- Running
openclaw devices listFresh device.json generates on each boot, no devices/ directory exists, no cached deviceToken anywhere on disk — but agent still gets rejected by its own gateway.
Setup: Docker container, gateway + agent same process, Tailscale networking, explicit auth token configured.
Anyone seen this? Is there a way to force re-pairing the internal agent
gateway connection?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
