Files
felhom.eu/documentation/audits/newbox-2026-10-18
..

R-1148 — a fresh install from nothing with installer 1.34.0 (2026-10-18 evening)

Throwaway customer Tester4 (created by the operator; domain tester4.test, a reserved name that never resolves; no off-site, no PBS-DR — nothing on ep0). VM 9302 newbox-r1148 on demo-hp (Tier 1; 8 GB / 4 cores / 120 GB raw on nvme-scratch = /mnt/hdd_1 root) from the public ISO 1.29.0 (checksum = the published one). The ISO fetches felhom-host-install.sh at run time from https://felhom.eu/scripts/ — served 1.34.0 (SCRIPT_VERSION read live). The graphical installer was driven with qm sendkey, the Hungarian keyboard kept, as a household would. The household's path: the mailed bind link + the pairing code on the console + the owner phrase (the operator put it in a 0600 file; shredded after), then the mailed setup code.

file what it shows
02-timeline.txt every step with its time (UTC below the line)
03-bind.txt the bind page's answer: „Sikeres összekötés"
04-pve-login-check.txt CC's own PVE API login from DooPlex, status codes only: the vaulted value 200; the value typed at install 401
05-claim-and-version.txt the claim (302 /) and the box's own /api/selfupdate/status: 0.329.0 → 0.330.0, initiated_by: auto-floor
07-first-app.txt BentoPDF installed through the dashboard's API: deploy 202, running, healthy
08-bootstrap-journal.txt the box's felhom-bootstrap journal (scanned for secret shapes: 0)
09-hub-reports.txt the hub's host reports (agent 0.159.2) and the controller's own reports (0.329.0, then 0.330.0)
10-poweroff.txt the household's „turn off" (202), the hub's deliberate_off_at
99-teardown.txt the name read back twice, VM 9302 destroyed with its disk; the other VMs listed
screens/ installer and console

Step 4b (R-1145) in the full sequence: recovery password vaulted at the hub (stored) — now setting it on root@pam → chpasswd → [OK] root@pam password vaulted, set, and the PVE login takes it, all at 18:03:43 UTC; the hub's host_recovery.set_at is the same second. The golden and the agent: the hub manifest named agent v0.159.2 (sha 4d98868e…) and golden v0.329.0 — the two vouched artifacts; both verified by sha256. The box came up on 0.329.0 and moved to the floor 0.330.0 by itself 2 min 47 s after the bind.

Not walked: an SSH key login — CC logged in with the vaulted password (sshpass -f, file 0600, shredded after).

Left for the operator (session only): delete customer Tester4 on the hub — allowed from 19:09 UTC (the last report 18:24:18 + the 45-minute stale threshold); a 409 before that is by design (R-599).