Forum

Hi GMow,

We investigated and found two issues:

1. Your first sandbox browser service is down

You have two browser services. The first one (openclaw-sandbox-browser) is not running — no pod exists for it. This is the one your config points to, which is why the connection fails.

The second one (openclaw-sandbox-browser1) is running and healthy — we verified CDP is responding on it.

2. The CDP URL in your config doesn't match the running service

Your OpenClaw config currently uses local Chrome (executablePath) instead of the remote CDP URL. The config update you pasted may not have been applied correctly.

To fix this:

1. Delete the broken first browser service (openclaw-sandbox-browser) from Dashboard — it's not running anyway
2. Update your OpenClaw browser config to point to the working service. The correct internal DNS name is openclaw-sandbox-browser-untal (not openclaw-sandbox-browser). Use this config:

"browser": {
 "enabled": true,
 "attachOnly": true,
 "defaultProfile": "remote",
 "profiles": {
 "remote": {
 "cdpUrl": "http://openclaw-sandbox-browser-untal:9222"
 }
 }
}

3. You can find the correct DNS name for any service in Dashboard → Service → Networking → Internal Hostname

After updating the config, the browser should connect successfully. Let us know if you need help.

Hi,

Good news on the first question — the broken openclaw-sandbox-browser service has already been deleted. It's no longer visible in the Dashboard because it's gone (not because it's hidden).

On the second question: We checked your OpenClaw config and found that the browser configuration was NOT updated. Your config still contains the OLD local Chrome settings:

"browser": {
 "executablePath": "/usr/bin/google-chrome-stable",
 "headless": true
}

This means OpenClaw is still trying to use a local Chrome, not the remote sandbox browser — that's why the error persists.

We verified that the remote sandbox (openclaw-sandbox-browser-untal) IS reachable from OpenClaw (Chrome 144 responds on CDP port).

To fix this, you need to actually update the browser config. Two ways to do it:

Option A — via OpenClaw Control UI:

1. Open OpenClaw Control UI (via rhclaw.zeabur.app or wherever your OpenClaw is accessed)
2. Go to Settings → Browser configuration
3. Replace the current config with:

{
"enabled": true,
"attachOnly": true,
"defaultProfile": "remote",
"profiles": {
"remote": {
"cdpUrl": "http://openclaw-sandbox-browser-untal:9222"
}
}
}

4. Save and restart OpenClaw

Option B — via OpenClaw CLI (chat with the agent):

You can directly tell the OpenClaw agent in chat:

Please add a remote browser config to my OpenClaw with cdpUrl http://openclaw-sandbox-browser-untal:9222 set as the default profile, attachOnly enabled.

The agent will update the config file (/home/node/.openclaw/openclaw.json) for you and apply the changes automatically.

Important: Make sure the old executablePath and headless fields are removed entirely — only the new browser config block as shown above.

If you can't save it via either method, let us know — we can guide you to edit /home/node/.openclaw/openclaw.json directly in the terminal.

This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.