Files
felhom.eu/STATUS.md
T
admin 44d1904286
gates / gates (push) Successful in 12m24s
DooPlex backup alarms: one cause (the dump job's password after the reboot), fixed; alarm mail quieter; R-1250 proven
R-232 dated note + a dated check for tonight's sweep; R-934 closed (the disk was pulled
2026-10-23); R-1250 fixed on main, live proof on demo-hp with a real seed; 08 §9 item 5.
Evidence audits/dooplex-alarms-2026-10-24/.
2026-10-24 13:53:57 +02:00

7.2 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-24 (afternoon, attended). The two DooPlex backup alarms had one cause: yesterday's reboot changed which password the database takes, so the database copy job could not log in, and the Gitea off-site copy then refused its old copy. Fixed and cleared at 12:51 local; critical alarms now repeat every 4 hours (all backup alarms in one mail), warnings every 12. A box whose torrent app seeds all day can now get its weekly line test (proven on demo-hp, not yet released).

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 — off-site live, local on the test image (map C5, D6, 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 one whole-box copy per week on ep0; CC uses its own limited token, not your password (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 is off since 2026-10-04: old emergency password, no off-site check, no bootstrap (R-1139, R-1104, R-862). The scratch box cannot use agent features (R-1083).
  • DooPlex: something sets the shared checkout to „bare" (R-935).

What we work on

  • Dated checks, run by CC. 2026-10-25: tonight's database copy reaches the restic sweep (R-232). 2026-10-26: each hub daily job ran once on the clock-change day (R-1183). 2026-10-27: the weekly clean-up window (R-435; the logs of the last one were lost to restarts). 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
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 2026-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 2026-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 2026-10-16.
  4. Remove the test server „plex-k6" from your Plex account (plex.tv → Settings → Authorized Devices). Since 2026-10-15.
  5. Ask Google to index https://felhom.eu/sajat-felho-tarhely in Search Console (R-1035). Since 2026-10-14.
  6. BIOS: on the N100, read „After Power Loss"; on the HP, set „Bypass F1 Prompt on Configuration Changes" to Enable. Since 2026-10-14.
  7. Pin the first Facebook post (R-917), and look at the new cover in the Facebook phone app (R-919). Since 2026-10-12.

Day, 2026-10-23 — your 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, and delete host Tester4-16fdef. If not: two dead entries alarm.
  3. D37 and D38 in the table (two small yes/no). If not: Gitea may restart in release hours; no golden in the release copy.
  4. Give the homelab session R-1241, R-1242, the 7-item list at the end of documentation/audits/plex2shell-felhom-impact-2026-10-23/README.md, the 5-item list at the end of documentation/audits/dooplex-alarms-2026-10-24/README.md (the database's two passwords), and an upload alarm on DooPlex's eno1 (the line is ~100 Mbit/s; 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 2026-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 2026-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-1250 (a seeding qBittorrent is never tested), 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.