docs(wiki): correct Steel Browser references across 15 pages — Steel fully removed, Camofox is sole backend

Root cause of the long-standing cloud_provider: steel residue: the 2026-07-30
rollback disabled the browser-steel plugin and set browser.engine: camofox but
left browser.cloud_provider: steel in config.yaml. The split config was
inert-but-wrong, so it survived ~3 months of audits unnoticed.

Corrects pages that still described Steel as present, running or configured:
- systems/browser-backend.md (incl. gateway-restart env-var note)
- comparisons/steel-vs-camoufox.md, comparisons/camoufox-vs-chrome.md
- decisions/rollback-steel-to-camofox.md, decisions/index.md
- infrastructure/docker-services.md, infrastructure/tailscale.md, infrastructure/hosts.md
- systems/homepage-dashboard.md, systems/scheduled-tasks.md
- concepts/browser-automation.md, runbooks/recover-docker-service.md
- current-state.md, index.md, agents/nanobot.md
- log.md (dated entry; supersedes the 00:3x audit's 'endpoint dark' wording)

Also restores the Ignis compose row in infrastructure/docker-services.md, which
the 2026-10-11 revision dropped (verified: /home/hermes/docker/ignis/docker-compose.yml
exists and the ignis container is Up on CT460).

Co-Authored-By: Hermes <hermes@local>
This commit is contained in:
Tony0410
2026-10-29 02:02:49 +08:00
co-authored by Hermes
parent ec0c30fb30
commit 677bb0c959
18 changed files with 757 additions and 592 deletions
+11 -8
View File
@@ -3,8 +3,8 @@ title: Docker Services
type: infrastructure
status: mixed
created: 2026-07-22
updated: 2026-10-11
verified_on: 2026-10-11
updated: 2026-10-29
verified_on: 2026-10-29
confidence: high
tags: [docker, homelab, infrastructure]
sources: [raw/configs/hermes-config-sanitized.txt, live-probe]
@@ -21,7 +21,7 @@ Docker runs on **three hosts**, and CT460's socket is not readable by the agent
| Host | Access | Containers running |
|---|---|---|
| CT200 `docker` (`100.96.150.69`) | `pct exec 200 -- docker ps` via PVE | **~50** — main Docker host |
| CT333 `clawtest` (`100.122.189.81`) | `pct exec 333 -- docker ps` via PVE | 9 (steel-browser, gotify, readlater, kokoro-tts, edge-tts, onecli-postgres, …) |
| CT333 `clawtest` (`100.122.189.81`) | `pct exec 333 -- docker ps` via PVE | 8 (gotify, readlater, kokoro-tts, edge-tts, onecli-postgres, …) — the `steel-browser` container and its image were **removed 2026-10-29** |
| CT460 `hermes` | `sudo docker` — socket is `root:docker srw-rw----`, `hermes` user not in group `docker`; **no passwordless sudo in cron** | `ignis` (confirmed running; inspect requires root) |
## CT200 live inventory (verified 2026-10-11, ~50 containers)
@@ -31,17 +31,15 @@ Docker runs on **three hosts**, and CT460's socket is not readable by the agent
**Note the duplicate Ignis:** `ignis-ignis-1` on CT200 is a separate deployment from CT460's `ignis`. See [[systems/ignis]].
## CT201 runtipi — Tailscale routes (verified 2026-10-11)
## CT201 runtipi — Tailscale routes (verified 2026-10-11; Steel routes removed 2026-10-29)
| Host | Path | Target |
|---|---|---|
| `runtipi.kangaroo-eel.ts.net:8443` (tailnet) | `/` | `http://127.0.0.1:8085` |
| | `/mgr` | `http://127.0.0.1:8084` |
| `runtipi.kangaroo-eel.ts.net` (tailnet) | `/` | `http://127.0.0.1:8085` |
| | `/mgr` | `http://127.0.0.1:8084` |
| | `/steel` | `http://127.0.0.1:5173` |
| | `/steel-api` | `http://127.0.0.1:3000` |
**Correction:** this page previously said "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 there" and listed CT201's `:8443` → `localhost:8082` for Homepage. Live `tailscale serve status` on CT201 shows the target is `127.0.0.1:8085` on both `:8443` and the default host, plus a `/steel` (5173) and `/steel-api` (3000) pair. The `/steel-api` route does not strip the path prefix — use the container IP directly for API calls.
**Correction:** this page previously said "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 there" and listed CT201's `:8443` → `localhost:8082` for Homepage. Live `tailscale serve status` on CT201 shows the target is `127.0.0.1:8085` on both `:8443` and the default host. That table also carried a `/steel` (5173) and `/steel-api` (3000) pair — **both routes were deleted on 2026-10-29** with `tailscale serve --set-path <path> off` when Steel was removed, so CT201's remaining routes are only `/` and `/mgr` on **both** `:443` and `:8443`. (The `/steel-api` route never stripped the path prefix — moot now that it is gone.)
## Confirmed Compose Files
@@ -50,7 +48,12 @@ Docker runs on **three hosts**, and CT460's socket is not readable by the agent
| Hermes Agent | `/home/hermes/.hermes/hermes-agent/docker-compose.yml` | hermes, hermes-dashboard |
| Hermes WebUI | `/home/hermes/hermes-webui/docker-compose.yml` | webui |
| ReadLater | `/home/hermes/workspace/readlater/docker-compose.yml` | readlater, edge-tts, kokoro-tts |
| Steel Browser | `/root/steel-browser/docker-compose.yml` (CT201) | steel-browser-api, steel-browser-ui |
| Ignis | `/home/hermes/docker/ignis/docker-compose.yml` (CT460) | ignis, ignis-data, ignis-obsidian-app |
**Steel Browser — removed 2026-10-29.** The CT201 compose file and Dockerfile are no longer live: the project
dir `/root/steel-browser` was deleted along with its containers, images and network. Both files are archived at
`/root/_archived-steel/` on CT201 (with `/root/_archived-steel/steel-cache-archive-20261029.tgz`), and the
images remain re-pullable from ghcr.io. → [[comparisons/steel-vs-camoufox]]
## Service Definitions (from compose files)
+8 -3
View File
@@ -3,8 +3,8 @@ title: Known Hosts and Paths
type: infrastructure
status: partial
created: 2026-07-22
updated: 2026-10-26
verified_on: 2026-10-26
updated: 2026-10-29
verified_on: 2026-10-29
confidence: medium
tags: [infrastructure, hosts, containers, paths]
sources: []
@@ -20,7 +20,7 @@ sources: []
| litellm | LiteLLM proxy | `http://litellm:4000/v1` | Yes (from config) |
| `custom:Omniroute:20128` | OmniRoute proxy (CT600 node `omniroute`) | `http://omniroute:20128/v1` → `100.88.81.19:20128` | Yes (live probe 2026-10-26: 6,480 models) |
| `custom:omni-101` | OmniRoute proxy (CT101 node `omniroute-1`) — **the live default provider** | `http://100.78.63.20:20128` | Yes (live probe 2026-10-26) |
| CT201 | Steel Browser, Runtipi, Homepage dashboard | `100.96.244.39` (Tailscale), `192.168.178.166` (LAN) | Yes (live probe) |
| CT201 | Runtipi, Homepage dashboard | `100.96.244.39` (Tailscale), `192.168.178.166` (LAN) | Yes (live probe) |
| CT460 | Hermes host, Camoufox, cua-driver | `hermes.kangaroo-eel.ts.net`, `100.118.5.51` (Tailscale) | Yes |
| PVE `pve` | Proxmox VE hypervisor hosting CT460 and the other `pve` guests | `100.96.100.82` (Tailscale), `pve.kangaroo-eel.ts.net` | Yes (live `pct list` 2026-10-26) |
| PVE `m93p` | Second, unclustered Proxmox VE 9.2.10 hypervisor | `100.104.51.98` (Tailscale) | Yes (live `pct list` 2026-10-26) |
@@ -69,5 +69,10 @@ sources: []
- Individual LXCs are verified only when probed directly; the two `pct list` snapshots above are the current authority for what is running
- Guests not present in those `pct list` outputs are **not** running on either hypervisor — do not assume existence from older session notes
> **Note (2026-10-29):** CT201 no longer hosts the Steel Browser — the containers, images, network, project dir
> and Tailscale Serve routes were all removed when Steel was deleted from the estate. CT333's separate,
> orphaned Steel copy was removed at the same time. → [[comparisons/steel-vs-camoufox]]
## Related
- [[docker-services]]
- [[infrastructure/tailscale]]
+9 -5
View File
@@ -3,8 +3,8 @@ title: Tailscale
type: infrastructure
status: active
created: 2026-07-26
updated: 2026-10-28
verified_on: 2026-10-28
updated: 2026-10-29
verified_on: 2026-10-29
confidence: high
tags: [tailscale, vpn, networking, infrastructure]
---
@@ -124,11 +124,15 @@ Verified live on 2026-10-26 via `pct exec 201 -- tailscale serve status` on `pve
| `runtipi.kangaroo-eel.ts.net:8443` (tailnet only) | `/mgr` | `http://127.0.0.1:8084` | `homepage-manager` container — **200** |
| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/` | `http://127.0.0.1:8085` | Same asset proxy — **502** (re-probed 2026-10-26) |
| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/mgr` | `http://127.0.0.1:8084` | `homepage-manager` — **200** |
| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/steel` | `http://127.0.0.1:5173` | Steel Browser UI — **200** on :443 (re-probed 2026-10-26). ⚠ **`/steel` is NOT served on :8443** — it 502s there |
| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/steel-api` | `http://127.0.0.1:3000` | Steel Browser API (path prefix not stripped — use direct IP for API calls) |
**Steel routes removed 2026-10-29.** This table previously carried two more rows on `:443` — `/steel` →
`http://127.0.0.1:5173` and `/steel-api` → `http://127.0.0.1:3000`. Both were deleted with
`tailscale serve --set-path <path> off` when Steel was removed from CT201, so CT201's only remaining routes
are `/` → `127.0.0.1:8085` and `/mgr` → `http://127.0.0.1:8084`, on **both** `:443` and `:8443`.
→ [[comparisons/steel-vs-camoufox]]
Two corrections to the pre-2026-10-25 table:
1. **`:8443` is served by `tailscaled` on CT201, but so is `:443`.** `ss -ltnp` on CT201 shows `tailscaled` bound to `100.96.244.39:443`, and the serve table above lists routes on **both** ports. The old note claiming "Port 443 occupied by Traefik on CT201" is **false as of 2026-10-25** — no Traefik container or process exists on CT201 (`docker ps -a` and `ps aux` both came back empty for `traefik`), and Tailscale owns 443 there. The Homebox/steel path prefix is not stripped on `/steel-api`.
1. **`:8443` is served by `tailscaled` on CT201, but so is `:443`.** `ss -ltnp` on CT201 shows `tailscaled` bound to `100.96.244.39:443`, and the serve table above lists routes on **both** ports. The old note claiming "Port 443 occupied by Traefik on CT201" is **false as of 2026-10-25** — no Traefik container or process exists on CT201 (`docker ps -a` and `ps aux` both came back empty for `traefik`), and Tailscale owns 443 there.
2. The old table routed `:8443` straight to `http://localhost:8082`. That port has **no listener**; the live target is `8085` (the `asset_proxy.py` front door), which itself proxies to the dead 8082 and returns 502. → [[systems/homepage-dashboard]]
## Atomic Restore Script