Browser tool consistently fails on VPS
✅Solved
Log snippet: [:tools] browser failed: Can't reach the OpenClaw browser control service (timed out after 15000ms). ...
Chrome extension relay: No tab connected
Tried:
Multiple full gateway restarts
Cleared devices/pairing/auth/cache folders
doctor --fix (multiple times)
controlUi allowInsecureAuth: true (didn't help browser)
Confirmed no port bind issues (gateway listens on 127.0.0.1:18789)
Headless Ubuntu server (no desktop, no real Chrome tab/extension attached)
It seems the browser subsystem is waiting for a client-side Chrome extension to attach a tab, which doesn't exist on a pure VPS setup.
Running 2026.2.15 on a DigitalOcean Ubuntu VPS (headless, loopback gateway).
Thx
Chrome extension relay: No tab connected
Tried:
Multiple full gateway restarts
Cleared devices/pairing/auth/cache folders
doctor --fix (multiple times)
controlUi allowInsecureAuth: true (didn't help browser)
Confirmed no port bind issues (gateway listens on 127.0.0.1:18789)
Headless Ubuntu server (no desktop, no real Chrome tab/extension attached)
It seems the browser subsystem is waiting for a client-side Chrome extension to attach a tab, which doesn't exist on a pure VPS setup.
Running 2026.2.15 on a DigitalOcean Ubuntu VPS (headless, loopback gateway).
Thx
Solution
On a headless VPS you’re seeing two different things mixed together:
1) “Chrome extension relay: No tab connected”
That’s only for the
2) “Can’t reach the OpenClaw browser control service (timed out …)”
The browser control service is a separate loopback port from the gateway: by default it’s gateway port + 2.
So if your gateway is on 18789, browser control should be on 18791 (and the relay is 18792). You only checking 18789 wouldn’t confirm browser control is up.
A) Switch default profile to managed mode
1) “Chrome extension relay: No tab connected”
That’s only for the
chrome2) “Can’t reach the OpenClaw browser control service (timed out …)”
The browser control service is a separate loopback port from the gateway: by default it’s gateway port + 2.
So if your gateway is on 18789, browser control should be on 18791 (and the relay is 18792). You only checking 18789 wouldn’t confirm browser control is up.
What to do on a VPS (recommended)
Use the managed browser profile and run it headless:A) Switch default profile to managed mode
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
129,194Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
