openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-21 19:25:25 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

Managed browser time out issue #93

New Issue
Open
opened 2026-02-15 17:15:38 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:15:38 -05:00
Owner
Copy Link
Copy Source

Originally created by @Sunshinenow on GitHub (Feb 7, 2026).

I’m trying to enable the OpenClaw‑managed browser on a fresh VPS so my agent can browse the web without Brave Search API limits. The gateway and model are healthy, but the managed browser never reaches running: true and openclaw browser ... start always times out.

Environment
OpenClaw version: 2026.2.6-3 (85ed6c7)

OS: Ubuntu 24.04 (noble) on Vultr

Gateway:

Bind: loopback (127.0.0.1)

Port: 18789

Status: Runtime: running, RPC probe: ok, Listening: 127.0.0.1:18789

Agent: using Gemini 2.0 Flash via Google AI Studio (works fine via Discord and Web UI).

What I’m trying to do
Follow the docs for Browser (OpenClaw‑managed):

Enable the browser and set a default profile.

Point it at a real Chrome binary, with sandbox disabled (per Linux troubleshooting guidance).

My current browser config (from openclaw config get browser) is effectively:

json
{
"enabled": true,
"defaultProfile": "openclaw",
"executablePath": "/usr/bin/google-chrome",
"headless": false,
"noSandbox": true
}
Chrome is installed from the official .deb:

bash
which google-chrome

/usr/bin/google-chrome

Browser status JSON
After running:

bash
openclaw browser --browser-profile openclaw start
openclaw browser --browser-profile openclaw status --json
I consistently get:

json
{
"enabled": true,
"profile": "openclaw",
"running": false,
"cdpReady": false,
"cdpHttp": false,
"pid": null,
"cdpPort": 18800,
"cdpUrl": "http://127.0.0.1:18800",
"chosenBrowser": null,
"detectedBrowser": "custom",
"detectedExecutablePath": "/usr/bin/google-chrome",
"detectError": null,
"userDataDir": null,
"color": "#FF4500",
"headless": false,
"noSandbox": true,
"executablePath": "/usr/bin/google-chrome",
"attachOnly": false
}
And the CLI prints:

text
Error: gateway timeout after 15000ms
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /root/.openclaw/openclaw.json
Bind: loopback
What already works
openclaw gateway status shows a healthy gateway on 127.0.0.1:18789 with RPC probe: ok and the dashboard reachable via SSH tunnel.

Discord integration and Web UI chat are working with Gemini 2.0 Flash as the model.

browser.enabled, browser.defaultProfile, and browser.executablePath are set as in the current docs.

What I’ve already tried
Initially used Ubuntu’s chromium-browser package (from apt install chromium-browser), but the managed browser still showed running: false.

Switched to a real Chrome binary via the official .deb and updated browser.executablePath to /usr/bin/google-chrome.

Set browser.noSandbox = true, browser.headless = false, and restarted the gateway after each config change.

Repeated openclaw browser --browser-profile openclaw start and status --json many times — always running: false, cdpReady: false, with the gateway timeout after 15000ms error on the CLI.

Question
Is there a known issue or additional config needed for the managed openclaw browser profile on:

Ubuntu 24.04 (noble)

OpenClaw 2026.2.6-3

Chrome at /usr/bin/google-chrome

when the gateway is loopback‑only on 127.0.0.1:18789?

In particular:

Is there a way to increase logging or run the browser control server in verbose mode so we can see why the Chrome/CDP launch fails or why the CLI→gateway handshake is timing out?

Are there any environment variables or flags I should set (for example to force a specific browser type, CDP port, or to work around Ubuntu 24.04’s sandboxing)?

My goal is to use the managed browser (not remote CDP and not Brave search) so my agent can browse with no API rate limits. Any guidance or patches would be hugely appreciated.

Originally created by @Sunshinenow on GitHub (Feb 7, 2026). I’m trying to enable the OpenClaw‑managed browser on a fresh VPS so my agent can browse the web without Brave Search API limits. The gateway and model are healthy, but the managed browser never reaches running: true and openclaw browser ... start always times out. Environment OpenClaw version: 2026.2.6-3 (85ed6c7) OS: Ubuntu 24.04 (noble) on Vultr Gateway: Bind: loopback (127.0.0.1) Port: 18789 Status: Runtime: running, RPC probe: ok, Listening: 127.0.0.1:18789 Agent: using Gemini 2.0 Flash via Google AI Studio (works fine via Discord and Web UI). What I’m trying to do Follow the docs for Browser (OpenClaw‑managed): Enable the browser and set a default profile. Point it at a real Chrome binary, with sandbox disabled (per Linux troubleshooting guidance). My current browser config (from openclaw config get browser) is effectively: json { "enabled": true, "defaultProfile": "openclaw", "executablePath": "/usr/bin/google-chrome", "headless": false, "noSandbox": true } Chrome is installed from the official .deb: bash which google-chrome # /usr/bin/google-chrome Browser status JSON After running: bash openclaw browser --browser-profile openclaw start openclaw browser --browser-profile openclaw status --json I consistently get: json { "enabled": true, "profile": "openclaw", "running": false, "cdpReady": false, "cdpHttp": false, "pid": null, "cdpPort": 18800, "cdpUrl": "http://127.0.0.1:18800", "chosenBrowser": null, "detectedBrowser": "custom", "detectedExecutablePath": "/usr/bin/google-chrome", "detectError": null, "userDataDir": null, "color": "#FF4500", "headless": false, "noSandbox": true, "executablePath": "/usr/bin/google-chrome", "attachOnly": false } And the CLI prints: text Error: gateway timeout after 15000ms Gateway target: ws://127.0.0.1:18789 Source: local loopback Config: /root/.openclaw/openclaw.json Bind: loopback What already works openclaw gateway status shows a healthy gateway on 127.0.0.1:18789 with RPC probe: ok and the dashboard reachable via SSH tunnel. Discord integration and Web UI chat are working with Gemini 2.0 Flash as the model. browser.enabled, browser.defaultProfile, and browser.executablePath are set as in the current docs. What I’ve already tried Initially used Ubuntu’s chromium-browser package (from apt install chromium-browser), but the managed browser still showed running: false. Switched to a real Chrome binary via the official .deb and updated browser.executablePath to /usr/bin/google-chrome. Set browser.noSandbox = true, browser.headless = false, and restarted the gateway after each config change. Repeated openclaw browser --browser-profile openclaw start and status --json many times — always running: false, cdpReady: false, with the gateway timeout after 15000ms error on the CLI. Question Is there a known issue or additional config needed for the managed openclaw browser profile on: Ubuntu 24.04 (noble) OpenClaw 2026.2.6-3 Chrome at /usr/bin/google-chrome when the gateway is loopback‑only on 127.0.0.1:18789? In particular: Is there a way to increase logging or run the browser control server in verbose mode so we can see why the Chrome/CDP launch fails or why the CLI→gateway handshake is timing out? Are there any environment variables or flags I should set (for example to force a specific browser type, CDP port, or to work around Ubuntu 24.04’s sandboxing)? My goal is to use the managed browser (not remote CDP and not Brave search) so my agent can browse with no API rate limits. Any guidance or patches would be hugely appreciated.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#93
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?