error for browser status command
Error: SECURITY ERROR: Gateway URL "ws://openclaw-gateway:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: cli --url
Config: /home/node/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost. after i run docker compose -f ./openclaw/docker-compose.yml run --rm openclaw-cli browser --url ws://openclaw-gateway:18789 --token "394d047f32c0b9e7976dee17ec901ed2d6530dfed71b63f4" --browser-profile openclaw status
?
here?
Error: gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: wss://openclaw-gateway:18789
Source: cli --url
Config: /home/node/.openclaw/openclaw.json
Both credentials and chat data would be exposed to network interception.
Source: cli --url
Config: /home/node/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost. after i run docker compose -f ./openclaw/docker-compose.yml run --rm openclaw-cli browser --url ws://openclaw-gateway:18789 --token "394d047f32c0b9e7976dee17ec901ed2d6530dfed71b63f4" --browser-profile openclaw status
?
here?
Error: gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: wss://openclaw-gateway:18789
Source: cli --url
Config: /home/node/.openclaw/openclaw.json
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
