- 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
5.1 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Domains and Tunnels | infrastructure | active | 2026-07-22 | 2026-11-11 | 2026-11-11 | high |
|
|
Domains and Tunnels
Purpose
Where martinwa.org subdomains point, and how they reach internal services.
How it works
- Verified: All
*.martinwa.orgpublic hostnames are served by a singlecloudflareddaemon running on ct207 (webserver), tunnel namect207-tunnel(ID339a6757-5574-4723-a16c-da4769535caa), config at/etc/cloudflared/config.ymlon ct207. - Verified:
cloudflaredis not installed on this host (ct460/hermes) — Hermes has no local tunnel process to manage or restart. Any tunnel-side incident (hostname down, wrong target) must be fixed on ct207, not here. - Two other Cloudflare tunnels exist in the same account (
Cloudo,Ifttt-ssh-webhook,livinity-liv) but are unrelated to Hermes/ct207 and out of scope for this page.
Hostnames relevant to Hermes
| Hostname | Target | Notes |
|---|---|---|
hermes.martinwa.org |
http://100.118.5.51:19119 |
Public Hermes dashboard — nginx on ct460 proxies 19119→127.0.0.1:9119 |
hermes-desktop.martinwa.org |
http://100.118.5.51:5174 |
Hermes desktop companion; sets Host: hermes.kangaroo-eel.ts.net |
hermesagent.martinwa.org |
http://100.98.205.112:9119 |
The older/original Hermes agent (ct450 "hermesagent"), kept alive alongside the current ct460 instance |
ssh-hermes.martinwa.org |
ssh://100.118.5.51:22 |
SSH to this host over the tunnel |
mcp-portal.martinwa.org |
(not in ct207 ingress list; see note below) | Referenced in Hermes config as an MCP server URL (https://mcp-portal.martinwa.org/mcp) |
omniroute.martinwa.org |
http://omniroute.kangaroo-eel.ts.net:20128 |
Public front for systems/omniroute |
nanobot.martinwa.org / nano-ssh.martinwa.org |
100.122.189.81 (ct333 "clawtest") |
See comparisons/hermes-vs-nanobot |
mcp-portal.martinwa.org is still not present in the ct207 ingress list — re-read live from
/etc/cloudflared/config.yml on ct207 on 2026-10-20. It may be served by a different
tunnel/host, or the ingress list may have moved since. Still unknown, still flagged for
follow-up rather than guessed.
Ingress changes found 2026-10-20 (full live re-read of ct207 config.yml)
The hostname list had drifted from the 2026-07-22 capture. Verified additions and corrections:
| Hostname | Live target | Note |
|---|---|---|
hermes-chat.martinwa.org |
http://100.118.5.51:8787 |
new — WebUI |
tg.hermes.martinwa.org |
http://100.118.5.51:19119 |
new — Telegram bot webhook |
openwebui.martinwa.org |
http://100.69.230.13:4000 |
new — Open WebUI |
news.martinwa.org |
http://docker.kangaroo-eel.ts.net:8300 |
new — WorldMonitor |
ssh-pve.martinwa.org |
http://100.96.100.82:7681 |
new — PVE noVNC |
nextcloud.martinwa.org |
https://100.90.102.19:443 |
target corrected (was 100.96.150.69) |
readlater.martinwa.org |
http://100.96.150.69:6123 |
confirmed |
velvet.martinwa.org |
http://127.0.0.1:8888 |
confirmed |
runtipi.martinwa.org |
http://100.96.244.39:80 |
confirmed |
homar.martinwa.org |
http://100.96.244.39:8102 |
confirmed — this is Homarr, the live dashboard (see systems/homepage-dashboard) |
The catch-all remains service: http_status:404. The ct207 config.yml still carries ~25 dated
config.yml.bak* files, newest config.yml.bak.1781809151.
Full ct207 ingress list (context, not all Hermes-related)
The tunnel also fronts: pve.martinwa.org (Proxmox UI), docker.martinwa.org (Portainer), runtipi.martinwa.org, homar.martinwa.org, nextcloud.martinwa.org, readlater.martinwa.org, velvet.martinwa.org, overtchat.martinwa.org, freellmapi.martinwa.org, omnideb.martinwa.org, newstarter.martinwa.org, and SSH endpoints for debianvm/pve/webserver. These belong to the wider homelab, not Hermes specifically — recorded here only so an ingress diff is possible later.
Full live re-read of ct207
/etc/cloudflared/config.ymlon 2026-11-11 — the list is unchanged from the 2026-10-20 diff. All ten additions/corrections recorded above are present and no new hostname has appeared; the catch-all is stillservice: http_status:404. ct207's LAN address is192.168.178.132, consistent with thessh-webserver.martinwa.org→100.82.40.23entry.mcp-portal.martinwa.orgremains absent from the ingress list — still unknown, still flagged.
History
- ct207's
/etc/cloudflared/directory has ~25 datedconfig.yml.bak*files going back to 2026-06-18, including several during ct460's own setup (config.yml.before-hermes-ct460-20260717203530,...before-hermes-desktop-20260718,...before-hermesagent-20260718085557) — evidence the ingress list has been actively iterated on throughout Hermes's bring-up.