WSL2 Gateway + Windows Node Host: Chrome extension relay and node pairing still not working after po
Hi OpenClaw team,
I’m struggling to get a Windows Node Host to properly connect to a Gateway running inside WSL2, and Chrome extension relay still reports connected: false.
Environment
Gateway: WSL2 (Ubuntu 24.04) on Windows 11
OpenClaw: 2026.2.21-2
Gateway bind: loopback, port 18789, token auth enabled
Browser + Node Host: Windows 11 on the same machine
Node Host command:
$env:OPENCLAW_GATEWAY_TOKEN = "<gateway.auth.token>"
openclaw node run --host 127.0.0.1 --port 18789 --display-name "Windows Browser Node"
What I see
Gateway logs: listening on ws://127.0.0.1:18789, browser service ready.
openclaw devices list (in WSL2) shows a paired device: Windows Browser Node (role=node).
Node Host on Windows starts without errors.
But:
openclaw nodes pending is always No pending pairing requests.
openclaw nodes status --connected shows no connected nodes.
Chrome extension relay (127.0.0.1:18792/extension/status) stays {"connected": false}.
What I’ve tried
SSH tunnel: ssh -L 18789:127.0.0.1:18789 user@<WSL_IP>
Windows portproxy from 127.0.0.1:18789 → <WSL_IP>:18789
Added WSL IP to gateway.trustedProxies.
Ran Gateway both as systemd service and via openclaw gateway run --bind loopback --port 18789.
Questions
With Gateway in WSL2 and Node Host on Windows (same machine), what is the correct minimal setup so that:
the node appears in openclaw nodes pending / nodes status, and
Chrome extension relay can attach to a tab?
Given that openclaw devices list already shows Windows Browser Node as paired, is there a way to reset or re‑pair the node so the Gateway sees it as a connected node again?
Thanks in advance for any guidance!
I’m struggling to get a Windows Node Host to properly connect to a Gateway running inside WSL2, and Chrome extension relay still reports connected: false.
Environment
Gateway: WSL2 (Ubuntu 24.04) on Windows 11
OpenClaw: 2026.2.21-2
Gateway bind: loopback, port 18789, token auth enabled
Browser + Node Host: Windows 11 on the same machine
Node Host command:
$env:OPENCLAW_GATEWAY_TOKEN = "<gateway.auth.token>"
openclaw node run --host 127.0.0.1 --port 18789 --display-name "Windows Browser Node"
What I see
Gateway logs: listening on ws://127.0.0.1:18789, browser service ready.
openclaw devices list (in WSL2) shows a paired device: Windows Browser Node (role=node).
Node Host on Windows starts without errors.
But:
openclaw nodes pending is always No pending pairing requests.
openclaw nodes status --connected shows no connected nodes.
Chrome extension relay (127.0.0.1:18792/extension/status) stays {"connected": false}.
What I’ve tried
SSH tunnel: ssh -L 18789:127.0.0.1:18789 user@<WSL_IP>
Windows portproxy from 127.0.0.1:18789 → <WSL_IP>:18789
Added WSL IP to gateway.trustedProxies.
Ran Gateway both as systemd service and via openclaw gateway run --bind loopback --port 18789.
Questions
With Gateway in WSL2 and Node Host on Windows (same machine), what is the correct minimal setup so that:
the node appears in openclaw nodes pending / nodes status, and
Chrome extension relay can attach to a tab?
Given that openclaw devices list already shows Windows Browser Node as paired, is there a way to reset or re‑pair the node so the Gateway sees it as a connected node again?
Thanks in advance for any guidance!
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
