Connection issues via SSH Tunnel - Error 1008 (Invalid request frame)
Hey team, I'm looking for some help with a handshake issue in a distributed environment.
My Setup:
Gateway: Remote (Ubuntu on AWS).
Local: MacBook Air running node run and browser serve.
SSH Tunnel: ssh -L 18789:localhost:18789 -R 18793:localhost:18793 <USER>@<REMOTE_IP>
The Problem: The extension connects for a split second (turns ON) and then immediately drops. I'm seeing the following in the Gateway logs:
Plaintext
[ws] closed before connect ... origin=chrome-extension://epjlkfdoibhaaefilkilimkinmhmnagl host=127.0.0.1:18789 code=1008 reason=invalid request frame
[ws] invalid handshake ...
Troubleshooting steps performed:
Confirmed the tunnel is active and ports 18789 and 18793 are correctly bound.
Manually injected the gateway.auth.token into the extension's background.js.
Verified with grep that the connection URL includes the token: ws://127.0.0.1:18789/extension?token=<MY_TOKEN>.
Reloaded the extension in chrome://extensions and refreshed the target page (Wikipedia).
Despite sending the token, the Gateway continues to reject the frame with code 1008. Is there any additional configuration required in clawdbot.json or a specific security restriction in the extension's handshake that I might be missing?
Thanks!
My Setup:
Gateway: Remote (Ubuntu on AWS).
Local: MacBook Air running node run and browser serve.
SSH Tunnel: ssh -L 18789:localhost:18789 -R 18793:localhost:18793 <USER>@<REMOTE_IP>
The Problem: The extension connects for a split second (turns ON) and then immediately drops. I'm seeing the following in the Gateway logs:
Plaintext
[ws] closed before connect ... origin=chrome-extension://epjlkfdoibhaaefilkilimkinmhmnagl host=127.0.0.1:18789 code=1008 reason=invalid request frame
[ws] invalid handshake ...
Troubleshooting steps performed:
Confirmed the tunnel is active and ports 18789 and 18793 are correctly bound.
Manually injected the gateway.auth.token into the extension's background.js.
Verified with grep that the connection URL includes the token: ws://127.0.0.1:18789/extension?token=<MY_TOKEN>.
Reloaded the extension in chrome://extensions and refreshed the target page (Wikipedia).
Despite sending the token, the Gateway continues to reject the frame with code 1008. Is there any additional configuration required in clawdbot.json or a specific security restriction in the extension's handshake that I might be missing?
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?
