admin
9e94479449
Read-only diagnostic; nothing restarted, reconfigured or deployed. CAUSE (H2, supported): the island migration rewrote bootstrap.json (169.254.253.1:8443) but the controller reads controller.yaml, which still holds the pre-island LAN address on both boxes -- mtimes 2026-07-21 and 2026-07-23, i.e. days BEFORE the migration. ensureLocalAPI (bootstrap.go:254) returns early when local_api.endpoint is non-empty, so it fills a MISSING endpoint and never reconciles a STALE one. The agent no longer binds the LAN address, hence "connection refused". H1 refuted: every island leg is healthy on both hosts -- agent active and bound 169.254.253.1:8443, vmbr9 up, guest eth1 up, TCP from the guest to the island is OPEN. The island works; nothing is using it. H3 refuted: hub-persisted events put the first alarm at 2026-07-25 12:44/12:46, ~17.5h before the v0.172.0 deploy. Today's re-fires are restart artifacts -- channel state is in-memory by design. H4 refuted: felhom-agent is active on both hosts. Also: the logged "up->down" is an ARTIFACT -- the debounce branch seeds an unseeded state to "up", so the channel was born-down and has never been up. Symptom B confirmed: EffectiveProtected gates cloudflared on a token predicate but samba on smb.Enabled alone, so sharing-without-password reports FAIL for a deliberately-undeployed stack. The function's own doc comment asserts the parity that is broken. Caused by leg 4 of the R-75 task. Blast radius: zero emails so far, but demo-hp flipped ok->fail and the health_critical path has reached the CUSTOMER channel historically. The English issue strings are whole-surface, not a one-off. Fixes described, none applied.
Felhom — Documentation
Felhom is a managed home-server service for Hungarian households, built on a three-component model over Proxmox:
- Hub — operator backend on k3s (
hub.felhom.eu). Repo:felhom.eu/hub/. - Host agent — one per Proxmox host; operator-tier; owns all Proxmox interaction. Repo:
felhom-agent/. - In-guest controller — one per customer LXC; Docker-only; manages the customer's apps. Repo:
felhom-controller/.
This directory is the central, code-verified documentation home for all three components plus the platform and the security-audit record.
Sections
Controller (in-guest) — controller/
The Docker-only app-domain controller. Full per-area docs grounded in current source (v0.59.0).
→ controller/README.md: module map, deploy & stack lifecycle, backup
architecture, storage/monitoring/metrics, auth/hub/sync/integrations.
Host agent & platform — architecture/, proxmox-platform.md
The operator-tier agent and the Proxmox platform.
architecture/01-topology-and-trust.md— topology & trust modelarchitecture/03-host-agent.md— the host agent (Go; v0.29.1)architecture/04-control-plane-authorization.md— signing, escrow, authzarchitecture/02-controller-module-map.md— historical v0.33 planning map; the live map iscontroller/module-map.mdproxmox-platform.md— Proxmox platform reference
Hub (operator backend) — architecture/05
architecture/05-hub-architecture.md— hub architecture (v0.11.0)
Security audits & remediation — audits/
audits/deep-sweep-2026-06-13.md— cross-repo deep audit (controller + agent) with remediation statusaudits/bughunt-reconcile-2026-06-13.md— reconciliation of the v0.30.3 BUGHUNT against current code + merged fix list
Spike & test findings — tests/
Per-slice spike/validation findings (phases 0–5, slices 7–10). See tests/.
Conventions
- Code-verified, not memory-derived. Architectural claims here are checked against the actual current source; if a claim can't be verified it is omitted and flagged, not guessed.
- Per-repo operational working files (
CLAUDE.md,CONTEXT.md,CHANGELOG.md,BUGHUNT.md,REPORT.md,TASK.md) live in their own repos — they are operational, not published docs. - Authoritative versions at last refresh: controller v0.59.0, agent v0.29.1, hub v0.11.0.