- 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
2.8 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Headless Server | system | active | 2026-07-22 | 2026-11-11 | 2026-11-11 | high |
|
|
Headless Server
Purpose
Headless X11 environment backing Hermes's browser automation and any GUI tooling.
Location
- Host: this container (ct460,
hermes), no separate VM/LXC — headless stack runs directly alongside the agent. - Display:
Xvfb :99, resolution1600x1200x24, started with-ac -nolisten tcp
Current configuration (verified via ps aux, 2026-07-22)
| Process | Detail |
|---|---|
Xvfb |
:99 -screen 0 1600x1200x24 -ac -nolisten tcp |
fluxbox |
window manager on :99 |
x11vnc |
-display :99 -forever -shared -rfbport 5901 -rfbportv6 5901 -noxdamage -quiet -nopw — no VNC password set |
websockify ×2 |
127.0.0.1:6080 → 127.0.0.1:5900 and 127.0.0.1:6081 → 127.0.0.1:5901, serving noVNC (/usr/share/novnc) |
Re-verified 2026-10-20. Two websockify instances still run (6080→5900 and 6081→5901), but
only one Xvfb exists (:99). Port 5900 has no listener at all — the 6080 websockify points
at a dead port, so it is a leftover from an earlier display, not a second live one. The 6080
pair is the Camofox noVNC front door (/home/hermes/services/camofox-browser/plugins/vnc/vnc-watcher.sh),
which proxies to 5900; Camofox's REST API is separately live on :9377 (HTTP 200).
The live chain is therefore :99 → x11vnc 5901 → websockify 6081.
Also confirmed still true in 2026-10-20: x11vnc still runs with -nopw (no VNC password) and
still binds all interfaces — 0.0.0.0:5901 and [::]:5901 — while both websockify ports
are correctly loopback-only (127.0.0.1:6080, 127.0.0.1:6081).
Re-verified 2026-11-11 via
ps aux+ss -ltnp— the live chain is exactly as recorded. OneXvfb :99(-screen 0 1600x1200x24 -ac -nolisten tcp), onex11vnc -display :99 … -rfbport 5901 -nopwbound to0.0.0.0:5901/[::]:5901, onefluxbox, and twowebsockifyinstances (127.0.0.1:6080→5900,127.0.0.1:6081→5901). Port 5900 still has no listener — the 6080 pair still points at a dead port. Camofox's own listener is separately live on*:9377.
Connected systems
- systems/hermes-agent (browser backend uses this display — see systems/browser-backend / comparisons/camoufox-vs-chrome)
- infrastructure/hosts
Known issues
x11vnc -nopw: VNC is unauthenticated. It's bound to all interfaces (0.0.0.0:5901and[::]:5901), not just loopback — reachable from the LAN and, if any tunnel/firewall rule forwards it, potentially beyond. Worth restricting to loopback or adding-passwd/-rfbauthif this hasn't been a deliberate choice.