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, resolution 1600x1200x24, 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).
x11vnc -nopw: VNC is unauthenticated. It's bound to all interfaces (0.0.0.0:5901 and [::]: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/-rfbauth if this hasn't been a deliberate choice.