#Setup Chrome on LXC

7 messages · Page 1 of 1 (latest)

spice spruce
#

Hey Krill! Im on the latest version of openclaw, 4.11, and i never got the builtin openclaw browser to work! Im using a diffrent way of starting my gateway, i do it with a systemctl service, but i dont think thats affecting anything.

openclaw browser start ("openclaw" as default) also does nothing and times out

Here is my config
"browser": {
"enabled": true,
"headless": true,
"noSandbox": true,
"attachOnly": true,
"defaultProfile": "openclaw",
"ssrfPolicy": {
"dangerouslyAllowPrivateNetwork": true
},
"profiles": {
"remote-lxc": {
"cdpUrl": "BROWSERLESSURL",
"color": "FF0000"
}
}
},

And the openclaw browser status

root@openclaw:~ openclaw browser --browser-profile openclaw status

🦞 OpenClaw 2026.4.11 (769908e) — If you can describe it, I can probably automate it—or at least make it funnier.

profile: openclaw
enabled: true
running: false
transport: cdp
cdpPort: 18800
cdpUrl: http://127.0.0.1:18800
browser: unknown
detectedBrowser: chrome
detectedPath: /usr/bin/google-chrome
profileColor: FF4500
root@openclaw:~

Again, latest version, and a LXC, so no x11 or any ui stuff.

tough emberBOT
urban lagoonBOT
#

I think I see the bug.

browser.attachOnly: true is the reason openclaw browser start does nothing here.

In OpenClaw, attachOnly: true means: do not launch a browser, only attach to one that is already running. Since your default profile is openclaw, that implicit openclaw profile inherits the top-level setting, so start has nothing to launch and eventually times out.

So for the built-in managed browser, change it to this:

"browser": {
  "enabled": true,
  "headless": true,
  "noSandbox": true,
  "defaultProfile": "openclaw",
  "ssrfPolicy": {
    "dangerouslyAllowPrivateNetwork": true
# 
  },
  "profiles": {
    "remote-lxc": {
      "cdpUrl": "BROWSERLESSURL",
      "attachOnly": true,
      "color": "FF0000"
    }
  }
}

A few notes:

  • remove the top-level attachOnly: true
  • keep attachOnly: true only on profiles that are externally managed
  • systemctl is probably not the problem
#
  • headless: true + noSandbox: true is normal for LXC/Linux

Then restart the gateway and test:

openclaw browser --browser-profile openclaw start
openclaw browser --browser-profile openclaw status

If it still fails after that, the next thing I’d want is:

openclaw logs --follow

while running the start command, because then we can see whether Chrome itself is failing to launch.