Dashboard shows "unauthorized: gateway token mismatch" after onboarding
Hey everyone, I'm having trouble connecting to my self-hosted gateway after completing the
onboarding wizard.
Setup:
Fresh install on Hetzner VPS following the deployment tutorial
Built from source using docker compose build
Ran onboarding with docker compose run --rm clawdbot-gateway node dist/index.js onboard
Onboarding completed successfully
SSH tunnel working: ssh -N -L 18789:127.0.0.1:18789 my-server
Problem:
Dashboard shows: disconnected (1008): unauthorized: gateway token mismatch
What I've tried:
Using the token from onboarding output in the URL
Using the token from my .env file (CLAWDBOT_GATEWAY_TOKEN)
Restarting the container with docker compose down && docker compose up -d
Double-checked both tokens match in .env
What I suspect:
There might be a token stored in the config file (~/.clawdbot/config.json or wherever
CLAWDBOT_CONFIG_DIR points) that was created during onboarding, and it's conflicting with the
environment variable token.
How does the gateway determine which token to use? Should the config file token and .env token be
the same? Do I need to regenerate the token or manually edit the config?
Thanks!
onboarding wizard.
Setup:
Fresh install on Hetzner VPS following the deployment tutorial
Built from source using docker compose build
Ran onboarding with docker compose run --rm clawdbot-gateway node dist/index.js onboard
Onboarding completed successfully
SSH tunnel working: ssh -N -L 18789:127.0.0.1:18789 my-server
Problem:
Dashboard shows: disconnected (1008): unauthorized: gateway token mismatch
What I've tried:
Using the token from onboarding output in the URL
Using the token from my .env file (CLAWDBOT_GATEWAY_TOKEN)
Restarting the container with docker compose down && docker compose up -d
Double-checked both tokens match in .env
What I suspect:
There might be a token stored in the config file (~/.clawdbot/config.json or wherever
CLAWDBOT_CONFIG_DIR points) that was created during onboarding, and it's conflicting with the
environment variable token.
How does the gateway determine which token to use? Should the config file token and .env token be
the same? Do I need to regenerate the token or manually edit the config?
Thanks!
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
