dashboard says update available: "Current version: 1.6.67 → 1.6.265 available" i try to update then it says: "sking server to start self-update... Self-update started — checking for new release... Checking for updates... New version available: 1.6.265 (current: 1.6.67) Container mode detected — host install at /opt/sparkbox Looking up dashboard image... Spawning privileged update helper (image=sparkbox-sparkbox-dashboard)... [helper 2026-06-19T00:37:28+00:00] starting [helper] from version: 1.6.67 [helper] Downloading install.sh... [helper] Downloading install.sh.sig... curl: (7) Failed to connect to get.tomsparkbox.com port 443 after 59 ms: Could not connect to server [helper] ERROR: install.sh signature missing from release server — refusing to execute install.sh ERROR: Update helper exited with code 1 [ERROR] SparkBox could not install the update. Your current install was left in place. Try again; if it repeats, open Settings → Updates and try the stepped update option." I looked though other post and it showed to go into terminal and do "sudo sparkbox update" after it showed complete but it does not update in dashboard. I also don't see the Tom AI feature, not sure if i'm doing something wrong as i'm new to this. but maybe just feedback or a bug. I'm using a UGreen DXP4800 Pro with UGOS 16GB of Ram, two 12tb Ironwolf Pro HHDs in raid 1 w/ two 1tb samung 980 pro as read/write cache and docker is handling sparkbox. Thanks
14 replies
tomspark wrote:
Thanks for the detail, and you're not doing anything wrong — your install is safe, it left everything in place. The real blocker is right in the log: the updater couldn't reach our download server ('Failed to connect to get.tomsparkbox.com'). Everything else — no Tom AI, the dashboard staying on 1.6.67 — is just downstream of the update not being able to download. Tom AI is a newer feature that shows up once you're updated, so let's fix the connection first. One quick check from your terminal — run this and paste what it says: curl -I https://get.tomsparkbox.com/install.sh If that fails too, your NAS can't reach our server — usually DNS or an ad-blocker. Since you're on a UGREEN box, if you're running Pi-hole or AdGuard here, that's the first suspect (it may be sinkholing our domain). If the line works fine, then it's just the update helper's own networking and we'll fix that. Tell me what it shows and we'll get you to 1.6.265.
pereze94 wrote:
This is what i got: "HTTP/2 200 date: Fri, 19 Jun 2026 03:58:04 GMT content-type: text/plain; charset=utf-8 cache-control: public, max-age=300 speculation-rules: "/cdn-cgi/speculation" report-to: {"group":"cf-nel","maxage":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=t68Zs72DEdGzQiduXuOsXSCUrGyqRxR%2FnxdrhYhuJVkhBkVkFuI07xKQymyHIV7qFAty3Cr5LvEHiIc%2FH%2Bl0xZ88RpPSOjxKVZDpgetaI7RSkaObo6BYm%2BIwHwdPkDBj12T62Q79"}]} nel: {"reportto":"cf-nel","successfraction":0.0,"maxage":604800} server: cloudflare cf-ray: a0df9cffb89f4383-LAX alt-svc: h3=":443"; ma=86400" i am not running Pi-hole or AdGaurd
tomspark wrote:
That 200 is exactly what I hoped to see — your NAS reaches our server fine, and with no Pi-hole or AdGuard, nothing's blocking it. So it's not a network block; it's the dashboard's built-in updater having its own hiccup, which is common on very old versions like your 1.6.67. Since you've got terminal access, let's update directly and skip that updater. Run this one line: curl -sSL https://get.tomsparkbox.com/install.sh | sudo bash That downloads and installs the latest version in place — your settings and media stay exactly where they are. It's a big jump from 1.6.67, so give it a few minutes to finish. Paste the last several lines when it's done (especially if it errors). Once it's updated, the dashboard and Tom AI will both show up; if the dashboard still says 1.6.67 afterward, a quick 'sudo docker restart sb-dashboard' sorts that.
pereze94 wrote:
Perfect, update completed with no issues and dashboard is updated to 1.6.271 and all services are running! I appreciate the help and keep up the good work!
tomspark wrote:
That's the one — nice work! Now that you're current (1.6.271), the Tom AI assistant you were looking for will be there too; you'll spot it right in the dashboard. Enjoy it, and shout anytime if anything else comes up. Thanks for the kind words!
pereze94 wrote:
I wasn't able to update as it failed and followed these steps again making sure its was show the same fault and was able to get it updated to 1.6.313
tomspark wrote:
That's great news — 1.6.313 means you're fully caught up and everything, including Tom AI, is there now. Sorry it took a couple of tries to take; jumping from a really old build like 1.6.67 sometimes needs a second run to fully land, which is exactly what you did right. You're all set, nothing else to do. If the dashboard ever shows an older number again, a quick 'sudo docker restart sb-dashboard' refreshes it. Enjoy it, and shout if anything comes up!
pereze94 wrote:
sorry i ment to say that i couldn't get it to update from 1.6.271 to 1.6.313 but just pressing the update button on sparkbox dashboard so i followed the steps we used the first time and that worked.
tomspark wrote:
Ah, thanks for clarifying. So the dashboard's update button wouldn't take you from 1.6.271 to 1.6.313, but the terminal command did. That's totally fine, you're fully up to date now either way. Good rule of thumb: if that button ever stalls again, the one-line terminal update is a reliable fallback and won't hurt anything. I'll keep digging into why the button's being stubborn on your box specifically. Enjoy 1.6.313!
pereze94 wrote:
Yes, mainly just feedback, I did jam up TomAi becuase i used too long of a log paste and I had to click the "+" next to the "X" to have it reset and let me ask more questions
tomspark wrote:
Appreciate the feedback, genuinely helpful. And good catch on the Tom AI thing, yeah, a really long paste can jam it up, and hitting that + to start a fresh chat is exactly the right move. I'll pass the long-paste hiccup along so it handles big logs more gracefully down the line. Thanks again, and enjoy 1.6.313!
pereze94 wrote:
one last thing i noticed is that with the new dashboard it doesn't pop up the password for qbit so i have to go back to classic dashboard to get the pop up password screen then after switch back
tomspark wrote:
Good catch, thanks. Yeah, on the new dashboard the little 'here's your app password' popup isn't showing for qBittorrent the way it does on classic, so popping back to classic to grab it and then switching back is the right move for now. Nothing's lost, it's just not surfaced yet in the new view. I've flagged it to get that password reveal added to the new dashboard too. Enjoy 1.6.313!
Chris wrote:
Circling back on this one — that reveal has landed, so you can stop bouncing over to classic just to grab it. Once you're on the current release, open Settings → Passwords. There's a Service Passwords list there, with a qBittorrent admin row masked by default and Reveal and Copy buttons next to it. Tom also added a Reset button for qBittorrent in v1.6.473, so a forgotten one now has a way back without the terminal — it re-asks for your admin password first. Sorry it took a while to come back to you on this. — Chris