Skip to main content

​
Browser Troubleshooting (Linux)

​
Problem: “Failed to start Chrome CDP on port 18800”

Clawdia’s browser control server fails to launch Chrome/Brave/Edge/Chromium with the error: 
{"error":"Error: Failed to start Chrome CDP on port 18800 for profile \"clawd\"."}

​
Root Cause

On Ubuntu (and many Linux distros), the default Chromium installation is a snap package. Snap’s AppArmor confinement interferes with how Clawdia spawns and monitors the browser process. The apt install chromium command installs a stub package that redirects to snap: 
Note, selecting 'chromium-browser' instead of 'chromium'
chromium-browser is already the newest version (2:1snap1-0ubuntu2).
This is NOT a real browser — it’s just a wrapper. Install the official Google Chrome .deb package, which is not sandboxed by snap: 
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo dpkg -i google-chrome-stable_current_amd64.deb
sudo apt --fix-broken install -y  # if there are dependency errors
Then update your Clawdia config (~/.nelsonmuntz-c/clawdia.json): 
{
  "browser": {
    "enabled": true,
    "executablePath": "/usr/bin/google-chrome-stable",
    "headless": true,
    "noSandbox": true
  }
}

​
Solution 2: Use Snap Chromium with Attach-Only Mode

If you must use snap Chromium, configure Clawdia to attach to a manually-started browser:
  1. Update config:
{
  "browser": {
    "enabled": true,
    "attachOnly": true,
    "headless": true,
    "noSandbox": true
  }
}
  1. Start Chromium manually:
chromium-browser --headless --no-sandbox --disable-gpu \
  --remote-debugging-port=18800 \
  --user-data-dir=$HOME/.clawdia/browser/clawd/user-data \
  about:blank &
  1. Optionally create a systemd user service to auto-start Chrome:
# ~/.config/systemd/user/clawd-browser.service
[Unit]
Description=Clawd Browser (Chrome CDP)
After=network.target

[Service]
ExecStart=/snap/bin/chromium --headless --no-sandbox --disable-gpu --remote-debugging-port=18800 --user-data-dir=%h/.clawdia/browser/clawd/user-data about:blank
Restart=on-failure
RestartSec=5

[Install]
WantedBy=default.target
Enable with: systemctl --user enable --now clawd-browser.service

​
Verifying the Browser Works

Check status: 
curl -s http://127.0.0.1:18791/ | jq '{running, pid, chosenBrowser}'
Test browsing: 
curl -s -X POST http://127.0.0.1:18791/start
curl -s http://127.0.0.1:18791/tabs

​
Config Reference

OptionDescriptionDefault
browser.enabledEnable browser controltrue
browser.executablePathPath to a Chromium-based browser binary (Chrome/Brave/Edge/Chromium)auto-detected (prefers default browser when Chromium-based)
browser.headlessRun without GUIfalse
browser.noSandboxAdd --no-sandbox flag (needed for some Linux setups)false
browser.attachOnlyDon’t launch browser, only attach to existingfalse
browser.cdpPortChrome DevTools Protocol port18800

​
Problem: “Chrome extension relay is running, but no tab is connected”

You’re using the chrome profile (extension relay). It expects the Clawdia browser extension to be attached to a live tab. Fix options:
  1. Use the managed browser: clawdia browser start --browser-profile clawd (or set browser.defaultProfile: "clawd").
  2. Use the extension relay: install the extension, open a tab, and click the Clawdia extension icon to attach it.
Notes:
  • The chrome profile uses your system default Chromium browser when possible.
  • Local clawd profiles auto-assign cdpPort/cdpUrl; only set those for remote CDP.