Files
felhom.eu/STATUS.md
T

7.5 KiB
Raw Blame History

STATUS — what works, what's broken, what's next

Ready for Tester 2? Yes — tell the friend go (hand-over list: documentation/pilot/TESTER2-handover.md).

Updated 2026-10-28 (night). CC cannot delete from its secret store any more (D60). The watch now reads the Node and Brotli inside every image: 20 catalog apps carry HTTP2Shell; Home Assistant and Immich have tested steps waiting for your yes. The hub has 3 minutes to start.

What works

  • The Plex attack (10-17 → 10-23) did not reach Felhom's secrets (R-1241).
  • A box installs from nothing with the public installer, links to the hub, and moves to the floor by itself (map A1, A3, A4).
  • 65 catalog apps install, update one tested step at a time, and a failed update undoes itself (map B1, B3, B4, B6).
  • Backups: database dumps, a second-drive copy, an off-site copy and whole-box copies; restore tests run by themselves (map C1–C4, A17, A18).
  • A restore brings an app back with its data and its database password; a failed or cut restore puts the app back as it was; a restore that does not start says so and keeps both copies (map C5, D6, D7, D16).
  • After a power cut the box starts by itself, cleans up a half-written backup, and Immich repairs broken photos (map C10, F12).
  • A second drive is offered as the backup target; media apps see every drive; a one-disk box gets its own data area (map D1, D13, D15).
  • The three test boxes answer only over https; the hub's key opens nothing on a box; password guesses are counted (map E12, E13, E17).
  • A hacked app that uploads or computes more than it explains alarms only you; each box tests its upload weekly; qBittorrent gets half (map F13).
  • An urgent security fix reaches the boxes at night after one test on the test box; the box backs up first and undoes a failed update (map B23).
  • The hub mails alarms and recoveries and keeps a weekly whole-box copy on ep0; CC uses its own limited token (map F1, F11, G15).

What is broken

  • P1: any hacked app on DooPlex can read the hub's nightly backups, and maybe the signing keys (R-1241, homelab session); about 12 homelab logins still use a password that was public, and the public Gitea repo is not decided (R-925, yours).
  • Tester 2 off since 10-04: old emergency password, no off-site check, no bootstrap (R-1139, R-1104, R-862). Scratch box: no agent features (R-1083).
  • DooPlex: something sets the shared checkout to „bare" (R-935).

What we work on

  • Released 2026-10-27: held apps reach you; safer kept data, ceremony and app import; reinstalled boxes back up off-site at once; the line test works while seeding; Go 1.27.3. Open: R-1285 (needs a BYO box on an old agent), R-1312 (what the hub's off-site switch does on the box). Evening: the one-time off-site clean-up window has a button (customer page → Backup & DR; you tested it); sec rm deleted 46 dead test-box names from CC's store.
  • Dated checks, run by CC. 2026-10-30: D35, website and installer to Cloudflare, starts (R-1228, ruled yes).

Waiting on you — decide

Newest first. CC's pick is in the „Pick" column. Each row also has its full text in the register.

# Row Question Pick (why) The other option costs If you do nothing Blocked
D61 R-1330 RomM: keep it offered while its newest release still has the bad Node inside? Node does not run in RomM, and the setup gate is in front. Keep it (no fixed release exists; the watch flags it nightly) hide it: it leaves the catalog until RomM ships a fix it stays offered —
D38 R-1235 Put the newest golden (637 MB) into the nightly release copy on ep0 too? Yes (a new install after a DooPlex loss needs it; it fits under the 3 GB cap) leave it out: after a loss, no new install until a golden is rebuilt and vouched the same —
D37 R-1236 Raise Gitea's memory limit from 1 GiB to 2 GiB? It was killed for memory 4 times in 17 days, once during today's release. Yes (DooPlex has the RAM; a DooPlex change, so yours) keep 1 GiB: a restart in release hours fails box updates and CI for a minute the same —
D9 R-1062 Split the N100's USB drive in two, for multi-drive tests? No — keep one drive (the lived-in box keeps its nightly whole-box backup) Split: the box loses its local whole-box backup, or you buy a second drive first it stays one drive; multi-drive tests stay on Tester 1 —
D7 R-990, R-989 Rule on the forum ideas and the selfh.st ideas now, or park them? Park them (P4; nothing waits on them) Rule now: about one hour of reading nothing changes; the research gets old —

Waiting on you — do

Still needed? (yes/no) — CC could not check these. Answer yes or no per line.

  1. Look at roms/roms/ on the N100's drive in the file manager (R-1099). (since 10-16)
  2. The N100 sheet, about 30 minutes: Plex, the admins in Prowlarr, Sonarr and Radarr, your download sources (documentation/audits/n100-lived-in-2026-10-15/SHEET.md). (since 10-15)
  3. Look at these demo-hp pages when you have time: Calibre-Web, the file manager, AdventureLog, Plex, the app page, the Plex and Sonarr guides. (since 10-16)
  4. Remove the test server „plex-k6" from your Plex account (plex.tv → Settings → Authorized Devices). (since 10-15)
  5. Ask Google to index https://felhom.eu/sajat-felho-tarhely in Search Console (R-1035). (since 10-14)
  6. BIOS: on the N100, read „After Power Loss"; on the HP, set „Bypass F1 Prompt on Configuration Changes" to Enable. (since 10-14)
  7. Pin the first Facebook post (R-917), and look at the new cover in the Facebook phone app (R-919). (since 10-12)

2026-10-28 morning. 1. Yes for the catalog push: Home Assistant and Immich (tested steps), Wanderer hidden (R-1313). If not: both keep the bad code; Wanderer stays offered. 2. Give the homelab session audits/http2shell-2026-10-27/HOMELAB-LIST.md (19 images, R-1328). 3. A removed store name back: git revert in your terminal (cc-secrets REPORT). 2026-10-23 do list.

  1. Print the break-glass sheet (documentation/runbooks/break-glass-sheet.md, the part from „The sheet”, one A4), fill it by hand, keep it outside the home (D32; R-923, R-924). If not: after a DooPlex loss no off-site copy opens.
  2. On the hub's Hosts page: Discard appliance 49. If not: a dead entry alarms.
  3. Give the homelab session R-1241, R-1242, the lists at the end of documentation/audits/plex2shell-felhom-impact-2026-10-23/README.md and documentation/audits/dooplex-alarms-2026-10-24/README.md, and an upload alarm on DooPlex's eno1 (~100 Mbit/s line; the flood peaked at 905). If not: the next hacked app on DooPlex can read the hub's backups. The rest
  • System poster needs a refresh: the new 01:40 „release copy” arrow from DooPlex to ep0 (D33); the hub-database label already says every 6 hours. If not: the drawing misses one copy.
  • Rotate the reused homelab logins and decide the Gitea repo's visibility (R-925, P1). (since 10-09)
  • Two DooPlex leftovers: leftovers/2026-10-14/first-post/ (keep or delete); the deny-list edit in homelab-manifests' .claude/settings.json (commit or drop). (since 10-14)
  • Before the first paying customer: Tandoor's permission (R-789); a lawyer for the licence list and the terms (R-802, R-813); SparkyFitness by e-mail (R-784).
  • Later (yours, not urgent): R-1248 (a hard upload cap per app), R-1229 (ArgoCD's sync settings into git), R-862 (Tester 2's bootstrap, when it is back), R-504, R-1071, R-1073, R-1077, R-1042, R-132, R-908, R-779, R-904, R-232, R-433, R-933, R-213, R-832, R-388, R-882, R-883, R-814, R-1056, R-1164, R-930, R-920, R-902.