#Gateway token mismatch

1 messages · Page 1 of 1 (latest)

night fiber
#

I used openclaw doctor --generate-gateway-token but can't see any token.

henan@DESKTOP-BL34404:~$ openclaw config get gateway.auth.token

🦞 OpenClaw 2026.3.8 (3caab92) — Your personal assistant, minus the passive-aggressive calendar reminders.

OPENCLAW_REDACTED

low inletBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

jovial elmBOT
#

That __OPENCLAW_REDACTED__ output is expected: openclaw config get now redacts sensitive values, so it will never print your gateway token in plaintext.

So two useful takeaways:

  1. Your token does exist (otherwise you’d get “path not found” / empty).
  2. If you need to actually use it, don’t rely on config get.

What to do instead (pick one):

Option A (easiest): open the dashboard with the token automatically

Run this on the gateway host:

openclaw dashboard
# or: openclaw dashboard --no-open

Docs: https://docs.openclaw.ai/cli/dashboard and https://docs.openclaw.ai/web/dashboard

#

Option B: look in the actual config file (not via config get)

openclaw config file

Open that file and find gateway.auth.token (don’t paste it into Discord).

Option C: rotate to a new token you know (recommended if you need to paste it somewhere)

TOKEN="$(openssl rand -hex 32)"
openclaw config set gateway.auth.mode "token"
openclaw config set gateway.auth.token "$TOKEN"
openclaw gateway restart
echo "$TOKEN"

Also: openclaw doctor --generate-gateway-token only generates a token if one is missing (and it won’t overwrite SecretRef/env-managed setups), so it’s normal to not “see” anything new after running it.