Ran wiki-maintain.sh (skills-index regenerated: 302 skills / 69 categories, unchanged; freshness report 0 stale / 109 fresh / 3 no-date of 112 pages; Quartz rebuilt and deployed). Freshness is not accuracy. A live-vs-page diff found real drift on five pages. All corrections verified against live sources first. - infrastructure/tailscale: node table rebuilt from tailscale status --json. 50 non-funnel nodes (49 IPv4 peers + hermes), not 54. 2 IP changes, 4 peers expired out of the tailnet. Zero IP mismatches, zero missing/extra rows on re-verification. m93p records online (peer record chronically stale, third occurrence -- ping + SSH confirm). CT460 :443 route set (12 paths) and CT201 :443/:8443 tables re-probed and match. - systems/scheduled-tasks: fleet is 29 jobs (25 enabled / 4 disabled), not 28/25/3. Mnemosyne Health Monitor ea79a2107e36 was auto-paused 2026-10-30 01:04:22 after its 00:01:08 slot closed "unknown" on a gateway-connection failure. Non-clean last_status is 4, not 3. "Failing (delivery only)" is 2. Seven job rows carried stale error claims for jobs since cleared to ok -- each marked superseded with a dated correction, not rewritten (SCHEMA rule 9). - NEW incidents/2026-10-30-mnemosyne-health-monitor-paused: the job's own failure notice was never delivered (deliveries.db has zero rows for 2026-10-30), so the incident row is the only trace. Job not re-enabled and gateway not restarted by this run; root cause recorded as unverified. - infrastructure/hosts: CT201 LAN is 192.168.178.77 (was .166); CT450 Hermes is v0.22.5 / bf0203a794a0, same build as CT460 (page said v0.22.3 / 5b147ab036d6); cron count 29/25/4; orphaned "omni" peer has expired out of the tailnet entirely. Skills count of 302 left alone -- it is correct. - systems/homepage-dashboard: live app count is 123 (was 114); grid is a responsive repeat(auto-fill, minmax(230px, 1fr)), not a fixed 5-column grid; tab bar is built from the service groups (renderTabs iterates state.groups), so the settings.yaml layout block and its tab:/columns: keys are inert -- there is no "Overview" tab; saved theme is Boarding Pass / light, not dark amber; manager.py runs inside the homepage-manager container; and the "no Traefik container" evidence was wrong -- the container exists but is stopped (Exited (255) 2 months ago). The conclusion that Traefik does not occupy 443 stands. Same evidence error corrected in tailscale.md. Also corrected two of my own first-pass errors before committing: the homepage tab list (groups vs tabs) and the CT450 version (a stale root-level /usr/local/bin/hermes reports v0.19.0; the live agent is the hermes-user install at v0.22.5). No secrets written -- provider names, key names and HTTP status codes only.
14 KiB
title, type, status, created, updated, verified_on, confidence, tags
| title | type | status | created | updated | verified_on | confidence | tags | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Homepage Dashboard | systems | degraded | 2026-07-26 | 2026-10-30 | 2026-10-30 | high |
|
Homepage Dashboard
Purpose
Central dashboard for all homelab services, with Proxmox integration, per-VM stats, and a management UI.
⚠ Status: DEGRADED (verified 2026-10-20)
The stock homepage container is not running on CT201. Only homepage-manager (port 8084)
and homebox are up; homebridge exited two months ago. Port 8082 has no listener, and the
asset_proxy.py front door on port 8085 proxies to 8082 — so it answers 502 Connection refused.
The dashboard that is live and serving 200 is Homarr on port 8102
(homar.martinwa.org in the Cloudflare tunnel ingress, and homarr in the Runtipi app list).
The dashboard content itself is now custom Python tooling under /opt/homepage/
(manager.py, asset_proxy.py, dashboard.html/js/css), not the upstream Homepage image.
Two independent dashboards are therefore in play — do not assume "the dashboard" means Homepage.
URLs
- Homarr (live, 200):
http://100.96.244.39:8102/— public viahttps://homar.martinwa.org - Tailscale:
https://runtipi.kangaroo-eel.ts.net:8443/→ proxies to 8085 → currently 502 - Local:
http://100.96.244.39:8082/→ no listener - Manager UI:
http://runtipi.kangaroo-eel.ts.net:8084/→homepage-manager, up
Architecture (re-verified 2026-10-30)
CT201 (runtipi)
├── homarr container (port 8102) — live dashboard, HTTP 200
├── homepage-manager container (8084) — web UI for adding/removing apps, up
├── homebox container (7745) — up
├── asset_proxy.py (python3, port 8085) — HOST process, proxies 8085 → 8082, currently 502
├── manager.py (python3) — runs INSIDE the homepage-manager container (see below)
└── Tailscale serve (ports 443 AND 8443) — / → 8085, /mgr → 8084 on both ports
(the former /steel and /steel-api routes were
removed 2026-10-29)
No container is listening on 8082 — docker ps on CT201 lists no homepage container at all.
Corrected 2026-10-30: the old diagram implied
manager.pyalso ran directly on the CT201 host. Livedocker inspect homepage-managershows its command is["sh","-c","pip install --quiet --no-cache-dir PyYAML && python3 /opt/homepage/manager.py"]with/opt/homepagebind-mounted — somanager.pyruns inside thehomepage-managercontainer (MANAGER_PORT=8084). Onlyasset_proxy.pyis a host process: livess -ltnpon CT201 shows0.0.0.0:8085 users:(("python3",pid=4038))— a bare/usr/bin/python3 /opt/homepage/asset_proxy.pywith no container owning it. The host-side:8084listener isdocker-proxy, not python.
Tabs
Re-verified 2026-10-30 against the live manager API (
GET http://127.0.0.1:8084/api/groupson CT201), the served/dash.jsand the served/dash.css. The old table below was wrong in several ways — the live tab bar is built from the service groups (renderTabs()indash.jsiteratesstate.groups), not from thelayout:block insettings.yaml. Thatlayout:block — and itstab:/columns:keys — is inert:grep -c "Overview" /dash.jsreturns 0, andgrep -c "columns" /dash.jsreturns 0. There is no "Overview" tab and thecolumns: Nvalues are never read.
The live tab bar is: ☆ Pinned, All (123), then the 14 service groups in order — each with a live
count badge:
| Tab | Live count | Apps |
|---|---|---|
| ☆ Pinned | — | pinned apps only (19 pinned in dash_prefs.json) |
| All (123) | 123 | every app, deduped by (name, normalised href) — corrected from 114 |
| AI Quotas | 3 | Claude, Codex, Ollama |
| Infrastructure | 13 | Gitea, Grafana, Guacamole, LAN watcher, PVE, Portainer docker, Portainer openweb, Runtipi, SFTPGO, Syncthing Runtipi, Theme Studio, cloudreve, filebrowser runtipi |
| Everyday | 8 | Homelab dashboard, Investbrain, Linkwarden, Mealie, NextCloud, cardholder, homebox, read later |
| Agents | 20 | AISBF Dashboard, Agent Dashboard, Agent zero, Camofox VNC chaos, Camofox VNC rhino, Chaos webUI, Herdr omarchy, Hermes Control, Hermes web UI (rhino), Hindsight chaos, Honcho memory dashboard, Mausbot ×2, Octoagent, PAN Hermes, Zeroclaw dash, herdr omarchybook, hermes desktop rhino, hermes workspace, nanobot dashboard |
| Media | 11 | Audio bookshelf, Flaresolverr, FreshRSS, Jellyfin, MeTube, NewsKu, Prowlarr, RSS-Bridge, Transmission, YouTube, qBitTorrent |
| AI & LLM | 17 | Agent estate wiki, Cliproxy api, FreeLLMAPI, Khoj ADMIN, Khoj SH, LiteLLM, Lobe chat (docker), Manifest router, Omniroute gateway, Opencode server, Openweb, Reasonix, Searxng, Simple chat ai, Vercel ai cloud, Voice Studio, World monitor |
| Tools | 20 | 8mb video compression, Cobalt, Convert to it, Cyber chef, Dockage, Element synapse, Excaldraw, IT tools, Matermost, Quiet thanks, Retroarch, Social dashboard (communities), Stirling PDF, Subscription tracker, T3 code frontend, Wordpress, code-server debian, compose craft, convert anything?, subtitle generator |
| Storage | 6 | Obsidian agent vault, filebrowser Debby, filebrowser DebianVM, filebrowser DebianVM NEW, filebrowser Docker, guacano |
| More | 13 | Cloudfare apps, GitHub, Kubuntu desktop, N8n, Next step, Omni tools, Reactive resume, Sunshine Ubuntu's-server, Yeah koko tts, hermes desktop, hermes desktop chaos, home assistant, jupyter server |
| Resources | 6 | Communities reporting - socials, Dashboard Manager, Helper Scripts, Homelab Docs, RADAR, Self-Hosted Directory |
| System Health | 0 | empty — the tab renders but holds no app cards (the health panel is separate, widget-driven) |
| Subscriptions | 1 | Renewals |
| Quick Launch | 2 | Paseo, Portainer |
| Uncategorised | 3 | Hermes desktop ui, Openchamber, Vaultwarden |
App-count reconciliation (two different numbers, both correct in context):
- 123 — the live count the UI shows on the
All (123)tab.get_all_apps_flat()walks every group exceptAll AppsandAI Quotas & Rate Limits, then dedupes by(name, normalised href)— so an app defined in two groups collapses to one card (e.g.Mausbotappears in bothAgentsandTools). - 122 — the literal
All Appsgroup in/opt/homepage/config/services.yaml, a generated roll-up that is not what the tab bar counts. The old page's "114" was simply wrong.
Grid layout (corrected): the served /dash.css (385 121 bytes, = /opt/homepage/config/dashboard.css)
sets .app-grid at line 3640 to grid-template-columns: repeat(auto-fill, minmax(230px, 1fr)) — a
responsive auto-fill, not a fixed 5-column grid. Narrower breakpoints override it to
repeat(auto-fill, minmax(160px, 1fr)) (line 5001) and then 1fr 1fr (line 5010). The columns: figures in
settings.yaml are dead config.
Proxmox Integration
- Node widget: Shows live VM/LXC counts, CPU, memory for PVE node
- Per-VM stats: Click "View Proxmox stats" on mapped services
- API token:
homepage@pve!homepage(privsep=0) - proxmox.yaml: Config at
/opt/homepage/config/proxmox.yaml
VM/LXC Mapping
Two Proxmox hosts exist and guest IDs collide — always qualify with a host.
ct460= PVE100.96.100.82;m93p= PVE100.104.51.98. The mapping below was re-read frompct liston both hosts on 2026-10-20; several rows previously listed bare IDs now live onm93p, and one row no longer exists at all.
| Service | Host | VMID | Type | Live state |
|---|---|---|---|---|
| PVE | both | (node) | — | — |
| Portainer docker | ct460 | 200 | lxc | running (8000, 9443) |
| Portainer debianVM | ct460 | 101 | qemu | running |
| Portainer openweb | m93p | 245 | lxc | running |
| Runtipi | ct460 | 201 | lxc | running |
| Gitea | m93p | 221 | lxc | running |
| FreshRSS | m93p | 1260 | lxc | running |
| NextCloud | ct460 | 270 | lxc | running |
| LiteLLM | m93p | 500 | lxc | running |
| OmniRoute | ct460 | 600 | lxc | running (also Omniroute:20128 on m93p 101) |
| Ntfy | m93p | 1241 | lxc | running |
| Home Assistant | ct460 | 100 | qemu | running |
| N8n | ct460 | 215 | lxc | running |
| Mattermost | ct460 | 255 | lxc | stopped |
| SFTPGo | ct460 | 299 | lxc | running |
| Cliproxy API | ct460 | 103 | lxc | running |
| OpenClaw | — | — | qemu | absent — no VM 403 on either host |
| Zeroclaw | ct460 | 333 | lxc | running |
| Hermes | ct460 | 460 | lxc | running |
| Hindsight | ct460 | 450 | lxc | running |
Portainer on CT245 (
openweb.kangaroo-eel.ts.net:9443) now uses a Tailscale/Let's Encrypt cert (installed 2026-08-09). Files:/root/portainer-certs/portainer.{crt,key}mounted into the container,--sslcert/--sslkey. Renewal:/root/renew-portainer-cert.shvia crontab (04:00 on the 1st monthly) —tailscale cert --min-validity=20dthendocker restart portainer. Cert validity ~90 days.
Configuration Files
/opt/homepage/ on CT201 now holds custom Python tooling, not the upstream Homepage bundle:
manager.py— dashboard management service (running)asset_proxy.py— port 8085 → 8082 front door (running, currently 502 upstream)dashboard.html/dashboard.js/dashboard.css— the custom dashboard frontendconfig/— legacy Homepage config directory (still present, upstreamhomepagecontainer not running)manager.py.bak.*— a long tail of dated manager backups (brand, chat2, cookie, hp, motion, owtools …)
Manager UI
Web form at port 8084 for adding/removing apps without SSH.
- Add: Name, Category (dropdown), URL, optional Icon
- Delete: Search apps, click Delete
- Auto-restart: Homepage restarts after each change
Quick Launch Search
Type anywhere on the dashboard to search services by name/description. Google search disabled — only searches your apps.
Theme
- Corrected 2026-10-30: the live saved theme is
{"pair":"Boarding Pass","mode":"light"}— read from/opt/homepage/config/dash_prefs.jsonkeydash.theme. The previous "Dark base with warm amber (#d4a04a) accents" claim is wrong on both counts: the mode is light, not dark, and#d4a04ais not this theme's amber at all. Boarding Pass (chassis: boarding, "Boarding pass desk — perforated stubs, gate codes, seat and route labels") is one of 59 theme pairs in/opt/homepage/config/themes.jsonunderdashboard.pairs; in its light mode the amber accent is#795000(dark mode would be#f5c96a). The dashboard also ships 26 legacyhomepage:themes (obsidian-midnight,nord-frost,cyberpunk-terminal, …) and three savedcustom:themes indash.customThemes(E2E Test Theme, Whiteboard Ops 1, Evidence Wall 1), each with its own chassis and palette. - Bigger tiles (68px min-height, 40px icons)
- Custom CSS in
custom.css
Tailscale Serve
CT201 serves Tailscale on BOTH :443 and :8443 (verified live 2026-10-25 via pct exec 201 -- tailscale serve status).
The earlier note on this page — "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 instead" — was wrong:
no Traefik process runs on CT201 (ps aux returns nothing for traefik), and
ss -ltnp shows tailscaled bound to 100.96.244.39:443. Corrected on 2026-10-25.
Evidence corrected 2026-10-30: the old wording said
docker ps -a"returns nothing fortraefik". That was not accurate — livedocker ps -aon CT201 does listruntipi-reverse-proxy | traefik:v3.2 | Exited (255) 2 months ago. The conclusion is unchanged (Traefik is not running and does not occupy 443;tailscaledis bound to100.96.244.39:443), but the container is stopped, not absent.
Maintenance
- Restart Manager:
docker restart homepage-manager - Restart Homarr:
docker restart homarr - Restart the custom dashboard: the
manager.py/asset_proxy.pyprocesses run directly on CT201 (not in Docker) — restart via whatever supervises them; checkps aux | grep -E 'manager.py|asset_proxy' - Recover the upstream Homepage (8082): the image
ghcr.io/gethomepage/homepageis still present on CT201 (4 months old) but no container uses it — recreate it to restore 8082 and the 8085 proxy path - Tailscale serve on CT201:
/→ 8085 and/mgr→ 8084 on both:443and:8443. The former/steel(5173) and/steel-api(3000) routes were deleted on 2026-10-29 when Steel was removed from CT201 — there are no other paths. → infrastructure/tailscale
Recent Changes
- 2026-10-29 (Steel removal): the
/steel(5173) and/steel-api(3000) Serve routes on CT201 were deleted withtailscale serve --set-path <path> offwhen the Steel Browser deployment was removed. CT201's remaining routes are only/→ 8085 and/mgr→ 8084 on both:443and:8443. → infrastructure/tailscale, comparisons/steel-vs-camoufox - 2026-10-25 (live probe, stocktake): the "Port 443 occupied by Traefik on CT201" note was false — no Traefik
process runs on CT201 (the
runtipi-reverse-proxyTraefik container exists but is stopped —Exited (255) 2 months ago— re-verified 2026-10-30), andtailscaledowns both:443and:8443there. Serve tables corrected:/→ 8085 and/mgr→ 8084 on both ports (the/steeland/steel-apiroutes listed at the time were deleted on 2026-10-29 — see above). Re-confirmed live: 8084 → 200, 8085 → 502, 8082 → no listener,homepage-managerup. → infrastructure/tailscale - 2026-10-20 (live probe):
homepagecontainer absent, 8082 dead, 8085 → 502, Homarr on 8102 → 200. Status changedactive→degraded. VM/LXC table re-read from both PVE hosts; corrected IDs and host assignments, dropped the non-existent OpenClaw VM 403, marked Mattermost CT255 stopped.
Related
- infrastructure/tailscale — Tailscale Serve routes on CT201 and CT460
- infrastructure/docker-services — container inventory for CT201 and CT333
- comparisons/steel-vs-camoufox — why the
/steelroutes were removed on 2026-10-29