Browser relay not starting on Windows node host (remote gateway setup)
✅Solved
Running OpenClaw 2026.2.26 with a remote gateway on a Linux VPS (via Tailscale, port 443 TLS). Node host running on Windows
connecting to the gateway with openclaw node run --host <gateway> --port 443 --tls.
The node connects and pairs fine (shows browser + system caps), but the browser control service/relay never starts locally — no
[browser/service] Browser control service ready line in output, and port 18792 never binds. nodeHost.browserProxy.enabled is set to
true in config.
It worked exactly once on first run, then stopped. No errors in node-error.txt, OPENCLAW_LOG_LEVEL=debug produces no additional
browser-related output.
Is there a way to force the browser relay to start on the node host, or is this a known issue with remote gateway + Windows node
host?
connecting to the gateway with openclaw node run --host <gateway> --port 443 --tls.
The node connects and pairs fine (shows browser + system caps), but the browser control service/relay never starts locally — no
[browser/service] Browser control service ready line in output, and port 18792 never binds. nodeHost.browserProxy.enabled is set to
true in config.
It worked exactly once on first run, then stopped. No errors in node-error.txt, OPENCLAW_LOG_LEVEL=debug produces no additional
browser-related output.
Is there a way to force the browser relay to start on the node host, or is this a known issue with remote gateway + Windows node
host?
Solution
To help others find answers, you can mark your question as solved via
Right click solution message -> Apps -> ✅ Mark Solution
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
Was this page helpful?
