Patches shipped: v1.6.626 → v1.6.636
Posted by Chris
Tom shipped 10 releases since the last note — here is the roll-up in one place. Every box picks them up on its own, or run sudo sparkbox update now. v1.6.636 — Docs and Tom AI catch up with today's changes: no more 'add the flaresolverr tag' advice anywhere - Tom AI no longer tells anyone to add a Cloudflare tag by hand — its guidance now matches the product: Byparr is the helper, every source is routed automatically, and the real next steps when a walled site still fails. - Tom AI also knows the new Video quality setting, so 'how do I get 4K?' is a one-line answer instead of a walk through Radarr profiles. - The docs page, the troubleshooting doc and the app descriptions no longer describe the old two-step FlareSolverr setup; the Settings reference now lists SBMEDIAQUALITY. v1.6.635 — Walled search sources just work: SparkBox routes every source through the Cloudflare helper for you — no tag to know about - You no longer need to know that a 'flaresolverr' tag exists. SparkBox now puts it on every search source automatically — on every start and within minutes of adding one — and the helper only steps in when a site actually shows an 'are you a robot?' page, so normal sources are untouched. Prefer to manage tags yourself? Set SBSOLVERAUTOTAG=false. - The guides and app descriptions that told you to tag sources by hand now say so only for older boxes. v1.6.634 — Byparr is now the default Cloudflare helper — the one that actually passes today's checks - Byparr replaces FlareSolverr as the default helper for search sources that sit behind a Cloudflare 'are you a robot?' check. FlareSolverr can't pass the newer ones; Byparr can. Same port, same Prowlarr setup, same 'flaresolverr' tag — nothing for you to change. - Boxes set up before this switch over automatically on their next update (it happens once; the log says so). Prefer FlareSolverr? App Store → Media → 'Use Byparr instead of FlareSolverr' → Off, and it stays off. - Fresh installs now get the Prowlarr proxy entry registered for whichever helper is running — previously a box on Byparr from day one would never have had it. v1.6.633 — The Media pipeline now spots when FlareSolverr can't pass Cloudflare and points at Byparr; every checkup failure links its guide - New: when every search source you routed through the Cloudflare helper is unavailable at once, the Media pipeline's Indexers step now says so and points at the one-toggle fix — App Store → Media → 'Use Byparr instead of FlareSolverr'. If you're already on Byparr it gives you the honest next step instead of sending you in a circle. It never names your sources. - Six new guides for the checkup's most common failures — an app keeps restarting, port already in use, permission denied (PUID/PGID), disk full, exposed to the internet, Docker unreachable — and the checkup, Tom AI and the Help page now link them. - The Cloudflare troubleshooting guide gained a 'switch to Byparr' cause and an 'already on Byparr?' section; the app setup pages were rewritten as short, honest cards that link each app's real fixes. v1.6.632 — dedup restartmodule "fails most of the time" cluster (field-5dd42c3976) - Dedup restartmodule "fails most of the time" cluster (field-5dd42c3976). v1.6.631 — Prowlarr tag tip; 'Ask Tom AI about this' works on the new dashboard; checkup guide links never guess - Warn that Prowlarr's tag field needs Enter to save a typed tag. - Fixed: on the current dashboard the new 'Ask Tom AI about this' button on a failing Media step showed up but did nothing. The step's existing ✦ Ask Tom button now carries the same ready-typed question instead. - Fixed: a failed checkup with no matching guide could be paired with an unrelated page (seen once on our test box). Now it links a guide only when we have the right one, and otherwise hands you to Tom AI. v1.6.630 — Help that follows you: every failing Media step now offers the guide and a one-click 'Ask Tom AI about this' - Every red or amber step on the Media pipeline card now carries two buttons: 'Read the guide' (the tested tomsparkbox.com page for exactly that problem) and 'Ask Tom AI about this' (opens Tom AI with the problem already typed, so you don't have to describe it — nothing is sent until you press Send). - When Tom AI runs the checkup, it now gets the matching guide for each failed check and hands you the page instead of improvising the fix. - Help page: a search box that finds guides from your own words ('jellyfin won't play', 'vpn keeps restarting'), plus a 'Recommended for your box right now' list built from what is actually failing on your server. - Behind it all is one shared guide catalogue — the card, the checkup, Tom AI and the website now point at the same help, and none of them can link a guide that doesn't exist. v1.6.629 — Curated download quality is back for new installs; new 1080p / 4K switch; Tom AI now links the real guides - Fixed: Media installs from roughly 7 August onward were silently left on the stock 'HD-1080p' profile with no custom formats — the community-standard (TRaSH-Guides) quality profiles SparkBox is supposed to apply never landed, because the upstream template format changed and our sync quietly failed every time. The sync now uses the current format and runs again on your next start; Radarr and Sonarr get 'HD Bluray + WEB' / 'WEB-1080p' and Seerr is pointed at them. Boxes set up before that date were never affected. - New: Settings → Media → Video quality. Pick 1080p (default) or 4K / UHD and Radarr, Sonarr and Seerr all switch together within about a minute — no per-app profile editing. Files you already have are never touched, and a profile you picked yourself inside Seerr is left alone. Guide: tomsparkbox.com/guides/media-4k-quality - New guide for the one media step SparkBox can't do for you — adding a search source (indexer) in Prowlarr: what the word means, exactly where to click, and what each Test error means. The Media pipeline's 'Show me how' button now opens it. SparkBox still does not pick or recommend sources. - Tom AI can now hand you the tested guide instead of improvising: it knows the full tomsparkbox.com guide catalogue and links only guides that actually exist for your question. v1.6.628 — Tom AI can repair the Portainer login itself; Portainer port clash healed; fixes keyed to the checkup - New one-click fix in Tom AI: when the checkup reports the known Portainer 'admin login failed' problem, Tom AI can now run the repair for you (new admin password saved under Settings → Passwords, only the Portainer container is recreated). It refuses to run if your login already works, and asks before doing anything, like every fix it offers. - Behind the scenes, Tom AI now remembers which fixes worked against which exact failed check from the checkup — the same failed check reads the same on every box, so what worked for one home can be offered confidently to the next. Nothing personal leaves your box: only counts per check and per fix. - Heal a :9000 rival the CLI can't attribute to a container. v1.6.626 — Saved passwords show up when you open an app again; Tom AI checks before it asks - Fixed the 'Opening qBittorrent' (and Jellyfin) note that promised to show your saved password below and then showed nothing. The launcher was looking up the wrong container for every app in the media stack, so it fetched a password that didn't exist. It now finds the right one, and the username and password appear under the note as intended. (Found on Tom's own NAS.) - Tom AI reads its own doctor report properly now. It used to see only the last screen of the report — the GPU listing and the summary banner — and missed the early checks that explain the common 'can't activate / can't reach our server' problems. It now gets every failing check with its fix lines, the passing checks in one line, and the checks about your problem first — in a single look. - Tom AI has two new standing rules for beginners: measure before asking (never ask you for a fact it can check on the box itself), and one step at a time in plain English, with third-party screens described rather than insisted on. Thanks to everyone who reported these — most started as a post here. If one of them is your report and it is not fixed for you, reply and I will pick it up.