Files
agent-estate-wiki/runbooks/restart-browser.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

3.5 KiB

title, type, status, created, updated, verified_on, last_tested, confidence, tags, sources
title type status created updated verified_on last_tested confidence tags sources
Restart Browser Helper runbook active 2026-07-22 2026-11-11 2026-11-11 2026-10-20 high
runbook
browser
cua-driver
camofox

Restart Browser Helper

Purpose

Restart the computer-use browser stack that Hermes uses for web automation, screenshots, and VNC/noVNC access.

Symptoms that match this runbook

  • Browser screenshots are failing
  • cua-driver MCP tools return errors
  • VNC/noVNC is unreachable on 5901 / 6081

Prerequisites

  • Display helper already running: Xvfb :99, x11vnc on 0.0.0.0:5901, noVNC at 127.0.0.1:6081
  • cua-driver binary installed — the release directory has moved on. The path this runbook used to hardcode (.../releases/0.9.0-x86_64-unknown-linux-gnu/cua-driver) no longer exists; /home/hermes/.cua-driver/packages/releases/ now holds 0.19.3, 0.22.2, 0.23.2, 0.24.0 and 0.28.2, and /home/hermes/.local/bin/cua-driver reports cua-driver 0.28.2. Prefer the stable /home/hermes/.local/bin/cua-driver path over a versioned release path.
  • Browser VM/desktop helper is expected but not mandatory

Procedure

1. Inspect current browser helpers

ps aux | grep -E "cua-driver serve|x11vnc|fluxbox|vnc-watcher" | grep -v grep

2. Stop cua-driver only

pkill -f "cua-driver serve"

3. Start cua-driver

/home/hermes/.local/bin/cua-driver serve

Run in background or a tmux/screen session if needed.

4. Verify ports remain available

nc -z 127.0.0.1 5901 && echo "x11vnc ok" || echo "x11vnc missing"
curl -s -o /dev/null -w "%{http_code}" http://127.0.0.1:6081/

5. Restart full browser VM stack only if step 4 fails

pkill -f "Xvfb :99"
pkill -f "x11vnc"
pkill -f "fluxbox"
/home/hermes/.local/bin/cua-driver serve

Procedure re-checked against live state 2026-11-11. Xvfb :99, x11vnc -display :99 -forever -shared -rfbport 5901 -rfbportv6 5901 -noxdamage -quiet -nopw, fluxbox and both websockify instances are running; cua-driver serve is up (PID 4176) and /home/hermes/.local/bin/cua-driver --version reports 0.28.2, matching the newest entry in /home/hermes/.cua-driver/packages/releases/ (0.19.3, 0.22.2, 0.23.2, 0.24.0, 0.28.2). 5900 still has no listener — the 6080 websockify still points at a dead port. All as recorded.

Verification

  • cua-driver serve process is present in ps
  • 5901 and 6081 are reachable
  • No zombie accumulation in browser/desktop processes

Rollback

  • If browser automation is not mission-critical, skip full VM restart and continue without it
  • Do not stop gateway or dashboard unless necessary

Notes

  • This runbook assumes the standalone desktop helper is running separately from Hermes core
  • The browser backend path can work without browser automation; this stack is optional depending on task

Last tested

2026-07-22 — procedure re-checked against live processes 2026-10-20. Xvfb :99, x11vnc -display :99 -forever -shared -rfbport 5901 -rfbportv6 5901 -noxdamage -quiet -nopw, fluxbox and both websockify instances (6080→5900, 6081→5901) are running, and the vnc-watcher.sh helper (/home/hermes/services/camofox-browser/plugins/vnc/vnc-watcher.sh) is up. Note 5900 has no listener — the 6080 pair points at a dead port (Camofox's front door); the live display chain is :99 → 5901 → 6081. See systems/headless-server.