Files
felhom.eu/STATUS.md
T
admin 978666dde3
gates / gates (push) Successful in 2m2s
lists: the Clock list (70 jobs) and the End-dates list (39 things), 9 register rows, 4 decisions
Read-only review of every job on a timer and of everything that ends on a date,
with measurements from the three test boxes. Nothing ends in the next 14 days.
Register 236 -> 245 (R-1379..R-1387), pointer lines on twelve rows, D76-D79 in
STATUS.md. Part C: felhom-agent's clone address holds no token now; the other
clones wait for the operator's yes. R-1035's 4-week check moved to 2026-11-18
(operator read needed).

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-11-11 11:54:42 +01:00

67 lines
8.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# STATUS — what works, what's broken, what's next
**Ready for Tester 2? Yes — tell the friend go (`documentation/pilot/TESTER2-handover.md`).**
**Updated 2026-11-11 (midday).** Two read-only lists are ready: every job on a timer (70) and everything that ends on a date (39); nothing ends in the next 14 days (`documentation/audits/end-dates-list-2026-11-11/README.md`). The golden passed its 7-day limit on 2026-11-10, so code pushes to `felhom.eu` are refused. Four decisions wait (D76–D79).
## What works
- **The Plex attack 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; a failed or cut restore puts it back as it was; one that does not start says so (map C5, D6, D7, D16).
- After a power cut the box starts by itself and cleans up a half-written backup (map C10, F12).
- A second drive is offered as the backup target; media apps see every drive (map D1, D13, D15).
- The three test boxes answer only over https; the hub's key opens nothing on a box (map E12, E13, E17).
- A hacked app that uploads or computes more than it explains alarms only you (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 (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).
- A box's event is lost if the hub is away for 9 seconds; a DooPlex restart can swallow a mail (R-1361).
## What we work on
- HTTP2Shell waiters: cal.com, Calibre-Web, RomM have no fix; SparkyFitness has one on a new main version (R-785, behind R-784).
## 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 |
|---|---|---|---|---|---|---|
| D76 | R-1380 | Shall the agent follow Proxmox's new certificate by itself? | **Yes** (one agent change, long before 2028; no box then depends on a calendar) | a hand step in a runbook and a calendar date for each box, for ever | in July 2028 the N100's agent loses guest control and backups, with no alarm that says why; the other boxes follow | — |
| D77 | R-1379 | Shall the product warn you 14 days before an end date (a box's web certificate, a hub token)? | **Yes** (a renewal that fails is silent today) | you keep the dates in a calendar by hand | the list of 2026-11-11 is the only guard | — |
| D78 | R-1383 | Shall a timed job that gives up or is skipped tell you (four cases: the guest-power watchdog, a skipped hub daily check, a lost operator mail, a refused signed job)? | **Yes** (small changes in the agent and the hub) | the logs stay the only trace | you learn of a dead guest from the household | — |
| D79 | R-1384 | Shall the hub check each box's clock and alarm above one minute of error? | **Yes** (a box with a wrong clock can look healthy and cannot take an agent update) | R-1301 (repair the N100's time service) stays the only guard | the N100 stays 32 s behind, and nobody is told when it gets worse | — |
| D66 | R-1365 | Should a security-watch source that stays down mail again every 7 days, as an open notice does? Today it mails once, then only the Monday summary lists it. | **Yes** (a real outage then cannot be forgotten; the seven pins that can never be read no longer count, so it stays quiet when all is well) | no: one line in a long Monday mail stays the only reminder | a source that stays down mails once; the Monday list still shows it | — |
| 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
**2026-11-11.** 1. Bake and vouch a golden, or write a waiver (R-468). If not: no code push to `felhom.eu`. 2. Read the dates of „Only you can read these dates” (`documentation/audits/end-dates-list-2026-11-11/README.md`, R-1381). If not: a domain or a token can end with no warning. 3. Rotate the Gitea token of login `kisfenyo` into the store as `GITEA_GIT_TOKEN` (R-925); it was printed on 11-10. 4. Yes or no: may CC fix the two other clone addresses (`cc-secrets`, the plug-meter clone)? Only `felhom-agent` is fixed. 5. Search Console read (R-1035, now 11-18).
**Still needed? (yes/no)** — answer 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-11-03.** To the homelab session: R-1355.
**2026-10-30.** On the hub's Hosts page: Discard the appliance of 10:44:59 (uuid d3529d2d…) and appliance 49 (CC's proof VMs). If not: dead entries alarm. **2026-10-29 (release run).** 1. (since 10-28) Give the homelab session `audits/http2shell-2026-10-27/HOMELAB-LIST.md` (19 images, R-1328). If not: DooPlex keeps the bad runtimes.
**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. 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 website now on Cloudflare, only its mail form on DooPlex (D35). If not: the drawing is out of date.
- 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.