Thank you — to everyone who reported, dug in, and stuck with it
Posted by tomspark
SparkBox is in beta, which is a polite way of saying: you've all been finding the rough edges the hard way — on your own hardware, on your own time. Almost every fix that's shipped these past couple weeks exists because someone here hit a wall, pasted a log, ran some weird diagnostic I asked for, and waited while we chased it down. I want to actually name you. The heavy lifters — hours of back-and-forth until we found the real root cause: - squid — the qBittorrent "Unauthorized" blank-page saga. Three browsers, incognito, the broken-quoted-hash upgrade path, the works. "finally lmao" lives in my heart. - LaggyGamerZA — ran the conclusive bcrypt test that cracked the Portainer 2.41 login bug wide open, plus Seerr and AdGuard. Relentless. - GamerX06 — Surfshark/gluetun, the Portainer 422 on a clean wipe, the egress false-positive, the Custom Domain gate. You broke it in all the useful ways. - notrike — most of the DM trenches: Moonfin, the arr downloads dir, qBit, anime indexers. - jackhammer57 — the Proton city-list issue and the VPN settings panel render bug. - fellini & ziggity — the multi-day Seerr "Jellyfin hostname already configured" hunt; fellini's network-inspector paste was the smoking gun. And everyone who reported, repro'd, and helped get it fixed: CtheEnigma (Seerr login-loop), MintyDuck (Proxmox LXC VPN fix — and circled back to confirm it, thank you), Seez (Usenet/VPN routing), illien (UGREEN volume-layout edge case), siv & jono1084 (WSL2 permission walls), JustJumpIn & notabubba (the Cloudflare install snag + wizard cutoff), waffle38930 (Duplicati), flashsider, Cammo92, frdrck, fwaygo (the arr / media-path tangle), sparkboxfan (first to flag the Portainer 422), Vorx4643 & DigitalDojos (Seerr auth), Crom (FileBrowser), NerdPlex, noliver2761, unfied, wartbump (early install + session fixes). If I missed your name, that's a failure of my list, not of your help — reply and I'll fix it. Here's the part I really want you to hear: a tester who just rage-quits teaches us nothing. Every one of you instead chose to write it up, run the command, screenshot the log, and come back. That's the entire difference between a project that limps and one that actually gets good. The patch speed people keep complimenting isn't us — it's you handing us the exact thing to fix. Thank you. Genuinely. It means the world to us. — Tom
2 replies
waffle38930 wrote:
No thanks needed Tom, thank you for creating a cool peice of software and having the drive and knowhow to do what you've done. I'm happy to support however I can.
LaggyGamerZA wrote:
thanks for all the hard work put in on your side