#I'm back again - old man who cant code !

1 messages · Page 1 of 1 (latest)

full bay
#

Subject: Persistent "Can't reach browser control service" & "pairing required" (UPDATE: doctor output & SKILL.md issue)

With the help of my OC whatsapp ... Hello OpenClaw Support Team,

I am encountering a critical and persistent issue with the browser tool on my headless Ubuntu VPS, which is preventing deep web interaction. Despite multiple troubleshooting steps, the problem persists. I have new diagnostic information from openclaw doctor and an observation regarding SKILL.md access.

Problem Description:
The browser tool consistently fails to start with the error: "Can't reach the OpenClaw browser control service (timed out after 15000ms). Restart the OpenClaw gateway... Do NOT retry the browser tool — it will keep failing."

Additionally, attempts to run openclaw status --deep from the CLI continue to report "gateway connect failed: Error: pairing required", indicating a deeper communication problem for certain OpenClaw CLI commands with the Gateway.

My Setup:

  • Operating System: Ubuntu (Linux 6.8.0-90-generic x64) on a headless VPS in Germany.
  • Node.js Version: 22.22.0
  • OpenClaw Version: 2026.2.21-2 (latest after update)
  • Gateway Status: openclaw gateway status reports running (pid ... , state active, sub running, last exit 0, reason 0) and RPC probe: ok.
  • Web Tools: web_search is working (Brave API key configured), and sessions_spawn (sub-agents) are working (confirmed by successful agent runs).

Detailed Troubleshooting Steps Taken (with outcomes):

  1. Initial browser(action='status'):
    • Output: "enabled": true, "profile": "chrome", "running": false, "cdpReady": false.
    • Observation: Browser tool enabled, but using 'chrome' profile which is unsuitable for headless VPS.
sick plankBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

full bay
#

  1. Attempted browser(action='start', headless=True, profile='openclaw') (prior to Chromium install):

    • Output: "error": "No supported browser found (Chrome/Brave/Edge/Chromium on macOS, Linux, or Windows).".
    • Observation: Chromium not installed.

  2. Installed Chromium:

    • Command: sudo snap install chromium
    • Outcome: Installation reported as successful.

  3. OpenClaw Client and Gateway Restarts (multiple times after Chromium install):

    • Commands: Ctrl+C for OpenClaw client, openclaw tui to restart client, openclaw gateway restart, sudo reboot (full VPS reboot).
    • Outcome: While these cleared the initial "pairing required" error for sessions_spawn, they did not resolve the browser control service timeout.
#

  1. Attempted gateway(action='config.patch') to configure browser.profiles:

    • Multiple attempts failed with "error": "invalid config".
    • Observation: Direct config.patch for nested browser.profiles structure appears problematic.

  2. Manual openclaw.json Edit (to configure browser section):

    • I manually edited ~/.openclaw/openclaw.json to include:
       ⁠json
      "browser": {
      "headless": true,
      "defaultProfile": "openclaw",
      "profiles": {
      "openclaw": {
      "driver": "clawd",
      "color": "#00AAFF"
      }
      }
      },
#
  • Crucially: A missing comma was identified and corrected during the manual edit: "defaultProfile": "openclaw",
    • Outcome: File saved, Gateway restarted, OpenClaw client restarted.

  1. Final browser(action='start', headless=True, profile='openclaw') attempt:

    • Output: "error": "Can't reach the OpenClaw browser control service (timed out after 15000ms).".
    • Observation: The issue persists even after manual config and restarts.

  2. openclaw status --deep (latest attempt):

    • Output: gateway connect failed: Error: pairing required (for the CLI itself).
    • Observation: Confirms persistent communication instability for deeper CLI operations, likely linked to the browser control service failure.
       ⁠
#
  1. openclaw doctor Output (Latest):
     ⁠
    ┌ OpenClaw doctor
    │
    ◇ State integrity ──────────────────────────────────────────────────╮
    │ │
    │ - 4/5 recent sessions are missing transcripts. Check for deleted │
    │ session files or split state dirs. │
    │ │
    ├────────────────────────────────────────────────────────────────────╯
#

│
◇ Session locks ──────────────────────────────────────────────────────────────╮
│ │
│ - Found 1 session lock file. │
│ - ~/.openclaw/agents/main/sessions/287b76db-9ad2-42f7-90d8-01e48b3679f0.js │
│ onl.lock │
│ pid=3279428 (alive) age=8s stale=no │
│ │
├──────────────────────────────────────────────────────────────────────────────╯
│
◇ Security ─────────────────────────────────╮
│ │
│ - No channel security warnings detected. │
│ - Run: openclaw security audit --deep │
│ │
├────────────────────────────────────────────╯
│
◇ Skills status ────────────╮
│ │
│ Eligible: 4 │
│ Missing requirements: 47 │
│ Blocked by allowlist: 0 │
│ │

#

0 │
│ │
├────────────────────────────╯
│
◇ Plugins ──────╮
│ │
│ Loaded: 6 │
│ Disabled: 30 │
│ Errors: 0 │
│ │
├────────────────╯
Telegram: not configured
WhatsApp: linked (auth age 6m)
Web Channel: +35386814XXXX(redacted) (...)
Agents: main (default)
Heartbeat interval: 30m (main)
Session store (main): /home/johnbroaders/.openclaw/agents/main/sessions/sessions.json (10 entries)
- agent:main:main (0m ago)
... (other session entries)
Run "openclaw doctor --fix" to apply changes.
│
└ Doctor complete.

#

Observation: doctor reports "Missing requirements: 47" for skills, which likely includes the browser tool. However, attempts to read the browser SKILL.md file (e.g., ~/.npm-global/lib/node_modules/openclaw/skills/browser/SKILL.md) resulted in "ENOENT: no such file or directory", preventing me from identifying the specific missing requirements.

Conclusion:
The browser tool, crucial for deep web automation, remains unavailable. The issue seems to be a complex interplay of the browser control service failing to launch/connect to Chromium, and an underlying "pairing required" instability affecting deeper CLI diagnostics. The high number of "Missing requirements" for skills, coupled with my inability to access SKILL.md files, suggests potential unmet system-level dependencies for browser operation.

Request:
I urgently need assistance in diagnosing and resolving the "Can't reach the OpenClaw browser control service" error in this headless Ubuntu VPS environment. Specifically, guidance on:

  1. Identifying the exact system dependencies required for the clawd browser driver.
  2. Troubleshooting the browser control service startup/connection within OpenClaw.
  3. Understanding why openclaw status --deep still shows "pairing required" and why SKILL.md files are inaccessible.
full bay
#

nobody 🙁

full bay
#

I've deleted my project and all keys etc. Best of luck guys. I'm outta here.