macOS Node Host: "unauthorized: gateway token missing" despite CLAWBOT_AUTH_TOKEN set
Hello Clawdbot community,
I'm trying to connect my macOS Node Host to my AWS Clawdbot Gateway, but facing persistent authentication issues.
Setup:
• Gateway (AWS EC2): Running clawdbot gateway --bind lan manually. Status shows listening on ws://0.0.0.0:18789. Port 18789 open in AWS Security Groups.
• Node Host (macOS): Running clawdbot node run --host <YOUR_AWS_PUBLIC_IP> --port 18789
• Problem: Node Host consistently fails with: unauthorized: gateway token missing (provide gateway auth token).
• Token Status: CLAWBOT_AUTH_TOKEN is verified as set in the macOS Terminal session (echo $CLAWBOT_AUTH_TOKEN returns the token). I've tried setting it via export, inline, and .zprofile without success. Token not shared publicly for security.
• Chrome Extension: Installed, but shows "!" (not connected).
Any insights why clawdbot node run isn't using the token? How can I debug this?
I'm trying to connect my macOS Node Host to my AWS Clawdbot Gateway, but facing persistent authentication issues.
Setup:
• Gateway (AWS EC2): Running clawdbot gateway --bind lan manually. Status shows listening on ws://0.0.0.0:18789. Port 18789 open in AWS Security Groups.
• Node Host (macOS): Running clawdbot node run --host <YOUR_AWS_PUBLIC_IP> --port 18789
• Problem: Node Host consistently fails with: unauthorized: gateway token missing (provide gateway auth token).
• Token Status: CLAWBOT_AUTH_TOKEN is verified as set in the macOS Terminal session (echo $CLAWBOT_AUTH_TOKEN returns the token). I've tried setting it via export, inline, and .zprofile without success. Token not shared publicly for security.
• Chrome Extension: Installed, but shows "!" (not connected).
Any insights why clawdbot node run isn't using the token? How can I debug this?
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?
