Files
agent-estate-wiki/infrastructure/tailscale.md
T
Tony0410 cc95dcc54d stocktake: re-verify Tailscale table, correct falsified cliprox/terra claim, regenerate skills-index
Wiki maintenance (wiki-maintain.sh, exit 0) + live-vs-page drift audit.

Script:
- systems/skills-index.md regenerated from the live skill tree: 302 skills in 69
  categories; 45 archived skills under ~/.hermes/skills/.archive/ now excluded and
  noted. (303 SKILL.md files exist outside .archive/, but
  productivity/obsidian-git-sync/obsidian-git-sync is a nested alias duplicate,
  so 302 unique is correct.)
- Freshness report raw/stocktake/freshness-20261029.txt: 2 stale / 105 fresh /
  3 no-date. After the corrections below and a second script run: 0 stale /
  107 fresh / 3 no-date.
- Quartz rebuilt (110 pages -> 644 files) and deployed to public/.

Drift corrections (live-verified):
- infrastructure/tailscale.md: State column rebuilt from tailscale status --json,
  11 rows changed. Two were state transitions, not age drift:
  * sftpgo (CT299, pve) is back online - tailscale ping pong in 0s,
    systemctl is-active sftpgo -> active, tailscale ip -4 inside the guest.
  * m93p is online despite a stale peer record (Online: false in the JSON) -
    tailscale ping pong in 1ms, SSH over the tailnet returned up 11 days.
    Second occurrence of this pattern after 2026-10-26.
  The other 9 rows were offline-age drift of exactly +1 day. Node count unchanged
  at 54 (53 live IPv4 peers + hermes); 76 peers total, 23 IPv6-only funnel
  ingress. No missing peers, no IP mismatches. Container identity re-confirmed
  from inside all 34 guests via pct exec tailscale ip -4 on both hypervisors;
  CT601 still absent from both.

- incidents/2026-10-01-cliproxy-connection-auth-expired.md: the residual claim
  "the connection credential itself was never re-authenticated" is falsified.
  Live POST /v1/chat/completions for cliprox/terra against custom:Omniroute:20128
  (CT600) returns HTTP 200 - the connection has since been re-authenticated. The
  same pin on custom:omni-101 (CT101) still returns HTTP 401, so the nodes carry
  separate credentials. Claim marked superseded, not deleted (SCHEMA rule 9); the
  remediation was never reversed and remains correct.

- incidents/2026-10-05-dead-model-pin-repin.md: every claim re-probed. All 7 jobs
  still on custom:omni-101 with routing aliases; both aliases HTTP 200;
  ollama-cloud/qwen3.5:397b still HTTP 410; nvidia/deepseek-v4-flash still
  HTTP 400; command-code/gpt-5.6-terra now HTTP 401 rather than the original 403
  - still dead, different failure signature.

- systems/scheduled-tasks.md: the Known-Issues entry repeating the
  "never re-authenticated" claim now carries the correction. Fleet figures
  re-checked against live jobs.json and remain accurate (29 jobs / 26 enabled /
  3 disabled, 5 non-clean last_status).

- log.md / index.md: stocktake entry appended and index last-updated refreshed.

Verified correct, no change: systems/homepage-dashboard (CT201 has 8084 and 8085
listening, no 8082, Homarr on 8102); CT201 Serve routes (/ -> 8085, /mgr -> 8084
on both :443 and :8443, Steel routes still gone); CT460 Serve routes (12 paths
on :443, plus :8443/webhook Funnel and :9443).

Noted for a human, not performed: vault mirror at /home/hermes/wiki/agent-estate-wiki
has drifted on both conventions (top-level 35 match / 3 stale / 72 missing;
wiki/ 41 match / 53 stale / 16 missing). A full mirror pass is larger than a
stocktake's mandate.
2026-10-29 03:42:54 +08:00

16 KiB

title, type, status, created, updated, verified_on, confidence, tags
title type status created updated verified_on confidence tags
Tailscale infrastructure active 2026-07-26 2026-10-29 2026-10-29 high
tailscale
vpn
networking
infrastructure

Tailscale

Purpose

WireGuard-based mesh VPN connecting all homelab hosts and providing HTTPS access via Tailscale Serve.

Domain

  • Tailnet: kangaroo-eel.ts.net
  • Primary node: CT460 (hermes.kangaroo-eel.ts.net, 100.118.5.51)
  • Runtipi node: CT201 (runtipi.kangaroo-eel.ts.net)

Tailscale Node Inventory (verified 2026-10-25)

Full node list from tailscale status — 54 non-funnel nodes (53 live IPv4 peers + hermes itself). Offline peers are listed with their last-seen age. Re-verified 2026-10-16: the 2026-10-11 table had drifted (15 nodes missing, several states wrong). Re-verified 2026-10-16: omarchymac (100.84.180.69) added; mattermost state, offline ages and the omni/omarchymac rows refreshed from tailscale status. Re-verified 2026-10-19 00:2x: three live peers had never been listed — guest-vps (100.117.14.84, online), openmausbot (100.91.214.91, online) and openmausbot-vm (100.77.107.30, online) — added; mattermost offline age 26d → 29d. Re-verified 2026-10-21 03:0x: the 2026-10-19 table had drifted again — octop (100.92.163.122), springroll (100.100.153.125), openmausbot and openmausbot-vm were missing from the table body (only mentioned in prose), omarchymac had gone offline (online → idle/offline 3d), and every offline age was stale. Table rebuilt from tailscale status --json, keyed on DNS name rather than HostName (the JSON HostName for freshrss is ct260, and both omniroute nodes share the hostname omniroute). Container states cross-checked against live pct list on pve (100.96.100.82) and m93p (100.104.51.98): CT255 (mattermost) stopped, CT601 (omni) stopped, CT299 (sftpgo) running, CT600 (omniroute) running. Re-verified 2026-10-29 03:0x AWST (stocktake): State column rebuilt from tailscale status --json — 11 rows changed. Two were state transitions, not age drift: sftpgo (CT299, pve) came back online (the 2026-10-28 audit had recorded it as offline <1d; live tailscale ping 100.88.223.70 → pong from sftpgo via 192.168.178.92:41641 in 0s, pct exec 299 -- systemctl is-active sftpgo → active, pct exec 299 -- tailscale ip -4 → 100.88.223.70), and m93p is online despite a stale peer record — tailscale status --json still reports Online: false with LastSeen 2026-10-28T18:40:00Z, but tailscale ping 100.104.51.98 → pong from m93p via 192.168.178.118:41641 in 1ms and SSH over the tailnet returned m93p / up 11 days. This is the second occurrence of the m93p stale-peer-record pattern (first seen 2026-10-26) — the peer record is not authoritative for hypervisor reachability. The remaining 9 rows were offline-age drift of exactly +1 day (anthonys-imac 34d → 35d; cachyos 54d → 55d; cloudreve 95d → 96d — CT209 stopped; elementsynapse 98d → 99d — CT555 stopped; freshrss-new 71d → 72d; mattermost 38d → 39d — CT255 stopped; omarchybook 6d → 7d; omarchymac 10d → 11d; omni 71d → 72d — CT601 removed from both hypervisors; openmausbot 6d → 7d). Node count unchanged at 54 non-funnel nodes (53 live IPv4 peers + hermes itself); tailscale status --json reports 76 peers total — 53 with a 100. IPv4, 23 IPv6-only (the funnel-ingress-node set). Nodes in the table that are no longer in the tailnet: none. Live IPv4 peers absent from the table: none. IP mismatches: none. Container identity re-confirmed from inside every LXC via pct exec <vmid> -- tailscale ip -4 across both hypervisors (pve 100.96.100.82, m93p 100.104.51.98) — 34 guests enumerated; every peer IP mapped to its CT as listed, and the three stopped guests (CT209 cloudreve, CT255 mattermost, CT555 elementsynapse) and the three running-but-unconnected guests (CT105 conduit, CT1264 openmausbot, CT100 obsidian-livesync) confirmed. CT601 remains absent from both hypervisors.

Re-verified 2026-10-28 00:2x (nightly audit): State column rebuilt from tailscale status --json — 14 rows changed (anthonys-imac: idle/offline 32d -> offline 34d; cachyos: idle/offline 52d -> offline 54d; cloudreve: idle/offline 93d — CT209 stopped -> offline 95d — CT209 stopped; conduit: idle/offline 49d -> offline 52d; elementsynapse: idle/offline 96d — CT555 stopped -> offline 98d — CT555 stopped; freshrss-new: idle/offline 69d -> offline 71d; m93p: online -> offline <1d; mattermost: idle/offline 36d — CT255 stopped -> offline 38d — CT255 stopped; omarchybook: idle/offline 4d -> offline 6d; omarchymac: idle/offline 8d -> offline 10d; omni: idle/offline 69d — CT601 removed from both hypervisors -> offline 71d — CT601 removed from both hypervisors; openmausbot: idle/offline 4d -> offline 6d; sftpgo: online — CT299 (pve) -> offline <1d — CT299 (pve); ubuntu-server-xfce: idle/offline 66d -> offline 68d). Header count corrected to 54 non-funnel nodes (53 live IPv4 peers + hermes itself). Nodes in the table that are no longer in the tailnet: none. Live IPv4 peers absent from the table: none. State transitions inside the audit window (not just age drift): m93p online → offline <1d, sftpgo (CT299) online → offline <1d. Re-verified 2026-10-25 03:1x (stocktake): table rebuilt again from tailscale status --json — springroll-browser (100.109.221.91) was missing entirely and has been added. omarchybook (100.107.9.100) and openmausbot (100.91.214.91) have both gone offline (online → idle/offline 3d) and openmausbot is no longer a live peer despite its m93p LXC (CT1264) still running tailscale — the node itself has stopped connecting. Every offline age was refreshed (e.g. mattermost 31d → 35d, omni 64d → 68d, elementsynapse 91d → 95d, ubuntu-server-xfce 60d → 64d, omarchymac 3d → 7d). m93p (100.104.51.98) now reads idle/offline 13m ago — the peer record is stale, but the host is plainly reachable (both pct list probes and the SSH session to CT201/CT460 during this audit succeeded), so treat it as a Tailscale-side liveness artefact, not a hypervisor outage. homeassistant still advertises ExitNodeOption: true but ExitNode: false — it offers exit-node capability; it is not currently serving as one (the old "active; offers exit node" wording overstated the live state). Container states cross-checked again against live pct list on both hypervisors, and each peer's container identity confirmed by running tailscale ip -4 inside the candidate LXC on both hosts — the authoritative mapping, since peer names and LXC names do not always match.

Node IP State
hermes 100.118.5.51 self — CT460 (pve)
agentzero 100.106.54.94 online — CT475 (pve)
anthonys-imac 100.112.123.124 offline 35d
anthonys-ipad 100.111.198.120 online
anthonys-iphone 100.100.116.67 online
anthonys-mac-mini 100.74.17.15 online
cachyos 100.124.208.15 offline 55d
clawtest 100.122.189.81 online — CT333 (pve)
cliproxyapi 100.83.112.94 online — CT103 (pve)
cloudreve 100.111.187.7 offline 96d — CT209 stopped
conduit 100.81.79.87 offline 52d
docker 100.96.150.69 online — CT200 (pve)
docker-01 100.121.12.31 online — CT1001 (m93p)
elementsynapse 100.75.250.37 offline 99d — CT555 stopped
freellmapi 100.127.208.75 online — CT1006 (m93p)
freshrss 100.83.60.93 online — CT1260 (m93p)
freshrss-new 100.110.180.115 offline 72d
gitea 100.82.100.128 online — CT221 (m93p)
guest-vps 100.117.14.84 online
hermesagent 100.98.205.112 online — CT450 (pve)
homeassistant 100.68.139.5 online
litellm 100.79.29.64 online — CT500 (m93p)
m93p 100.104.51.98 online — hypervisor (peer record stale: tailscale ping + SSH verified 2026-10-29)
mailflow 100.115.60.92 online — CT1262 (m93p)
mattermost 100.98.116.14 offline 39d — CT255 stopped
n8n 100.84.124.30 online
nextcloud 100.90.102.19 online — CT270 (pve)
ntfy 100.67.153.116 online — CT1241 (m93p)
octoagent 100.117.10.68 online
octop 100.92.163.122 online
ollama 100.108.44.119 online — CT205 (pve)
omarchy 100.73.227.103 online
omarchybook 100.107.9.100 offline 7d
omarchymac 100.84.180.69 offline 11d
omarchymac-1 100.126.173.115 online
omni 100.93.204.4 offline 72d — CT601 removed from both hypervisors
omniroute 100.88.81.19 online — CT600 (pve), live OmniRoute
omniroute-1 100.78.63.20 online — CT101 (m93p)
openmausbot 100.91.214.91 offline 7d
openmausbot-vm 100.77.107.30 online
openweb 100.69.230.13 online — CT245 (m93p)
paseo 100.72.188.93 online — CT1261 (m93p)
pve 100.96.100.82 online
qwenpaw 100.110.72.126 online — CT465 (pve)
rclone 100.107.116.17 online — CT104 (m93p)
runtipi 100.96.244.39 online — CT201 (pve)
rustdesk 100.95.227.57 online — CT1008 (m93p)
sftpgo 100.88.223.70 online — CT299 (pve)
social-dashboard 100.70.183.37 online — CT1263 (m93p)
springroll 100.100.153.125 online
springroll-browser 100.109.221.91 online
ubuntu-server-xfce 100.101.26.104 offline 68d
vaultwarden 100.123.225.90 online — CT102 (m93p)
webserver 100.82.40.23 online — CT207 (pve)

Note: tailscale status also lists 23 funnel-ingress-node peers with IPv6-only addresses — these are Tailscale's Funnel infrastructure, not homelab hosts, and are deliberately excluded above.

Note: Tailscale's offline list is not authoritative for container state — cross-check pct list on the PVE host.

CT460 Serve Routes

Path Target Notes
/ http://127.0.0.1:9119 Hermes WebUI
/ui http://127.0.0.1:5175/ Hermes UI (Vite)
/jobs http://127.0.0.1:9099 Jobs Dashboard
/wiki http://100.118.5.51:9120 Agent Estate Wiki (Quartz)
/ignis http://127.0.0.1:8080 Ignis (browser-native Obsidian)
/webui http://127.0.0.1:8787/ Hermes WebUI (Standalone)
/gitea http://100.82.100.128:3000 Gitea
/desktop http://127.0.0.1:6081 CUA noVNC
/vnc-camofox http://127.0.0.1:6080 Camofox VNC
/synergy-prep http://127.0.0.1:9123/ Synergy prep
/agent-estate http://127.0.0.1:8769 Role dashboard — target is the bare host root, not /agent-estate-role-dashboard.html (corrected 2026-10-11)
/evening-grid.html http://127.0.0.1:9099/evening-grid.html Evening grid

Re-verified against tailscale serve status on 2026-10-26 — the CT460 route table above matched live exactly (12 paths on :443, plus the :8443/webhook Funnel and the :9443 tailnet route; no drift).

CT460 Funnel and 9443 Routes

Port Target Notes
:8443/webhook http://127.0.0.1:8085/webhook Public webhook Funnel (# Funnel on: confirmed)
:9443 (tailnet only) / http://127.0.0.1:5173 Vite dev server on port 5173 exposed via a tailnet-only Serve on port 9443 — was missing from this page, added 2026-10-11

Re-verified 2026-10-26 (stocktake): the node table was rebuilt again from tailscale status --json — octoagent (100.117.10.68) and omarchymac-1 (100.126.173.115) were both missing entirely and have been added; m93p (100.104.51.98) now reads online (it was "idle/offline 13m ago" — a stale Tailscale peer record, and the host was plainly reachable throughout); every offline age was refreshed (mattermost 35d → 36d, omni 68d → 69d, elementsynapse 95d → 96d, ubuntu-server-xfce 64d → 66d, omarchymac 7d → 8d, omarchybook 3d → 4d, openmausbot 3d → 4d). The omni row now reads "CT601 removed from both hypervisors" rather than "CT601 stopped" — live pct list on both pve and m93p shows no CT601 at all, so the old guest is gone, not merely halted. Container identity re-confirmed from inside each LXC via pct exec <vmid> -- tailscale ip -4 on both hypervisors; every peer whose LXC has no Tailscale IP was checked against pct list (CT105/CT1264 run but do not connect — conduit and openmausbot offline; CT209/CT255/CT555 are stopped). Serve tables re-probed per host with pct exec 201 -- tailscale serve status.

CT201 Serve Routes

Verified live on 2026-10-26 via pct exec 201 -- tailscale serve status on pve (100.96.100.82). The previous version of this table was wrong in two ways and has been corrected.

Host / Port Path Target Notes
runtipi.kangaroo-eel.ts.net:8443 (tailnet only) / http://127.0.0.1:8085 Homepage asset proxy front door — 502 (re-probed 2026-10-26; upstream 8082 has no listener)
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

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.
  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

/home/hermes/.hermes/scripts/tailscale-serve-apply.sh — Rebuilds the complete CT460 route table, including tailnet Serve on :443 and public Funnel on :8443.

tailscale serve reset clears Funnel state as well as Serve state. The atomic script therefore restores /webhook after rebuilding the 443 routes. Do not use the older Serve-only restore path for complete recovery.

Key Commands

# Check routes
tailscale serve status

# Rebuild routes (CT460)
/home/hermes/.hermes/scripts/tailscale-serve-apply.sh --dry-run
/home/hermes/.hermes/scripts/tailscale-serve-apply.sh

# Add route
tailscale serve --set-path /jobs http://127.0.0.1:9099

# Remove route
tailscale serve --set-path /jobs off

Notes

  • CT201 now serves Tailscale on BOTH :443 and :8443 (verified 2026-10-25). The old "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 there" claim was wrong: no Traefik container or process exists on CT201, and tailscaled owns 443 there (ss -ltnp shows it bound to 100.96.244.39:443). The CT201 Serve Routes table above now records both ports.
  • CT460 has no conflict — Tailscale uses 443 directly, with the public webhook Funnel on :8443.
  • Routes must be re-added in order (restore script handles this).
  • After every rebuild, verify that tailscale serve status contains both the :443 Serve routes and the :8443/webhook Funnel route.