[helper] Downloading install.sh... curl: (6) Could not resolve host: get.tomsparkbox.com (Timeout while contacting DNS servers) [helper] curl failed: 6 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 updatServer:
7 replies
Chris wrote:
Good news first: nothing on your box is broken. That error means the update stopped safely before touching anything, so your setup is exactly as it was. What actually failed is the lookup of our download address. I just checked from the outside and get.tomsparkbox.com is up and serving normally right now, so it is your box that could not reach a name server, not our end being down. One thing to run over SSH: sudo sparkbox doctor Near the bottom it checks whether your apps can reach the internet. Paste that bit back here and we will go from there — no need to reinstall anything.
Majorman747 wrote:
/ | | | | ) \ \| ' \ / | '| |/ / \ / \ \/ / ) | |) | (| | | | <| |) | () < |/| ./ \,|| ||\\/ \//\\ || SparkBox v1.6.389 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Network profile: private SparkBox Doctor Running diagnostics... [Install location] [OK] SparkBox is installed at: /opt/sparkbox [OK] Settings file (.env): /opt/sparkbox/.env [OK] Media library folder (MEDIAROOT): /opt/sparkbox/data/media [Docker] [OK] Docker daemon is accessible [OK] Docker version: Docker version 29.6.2, build dfc4efb [OK] Docker Compose: 5.3.1 [Docker Socket] [OK] Docker socket exists at /var/run/docker.sock [OK] Docker socket is readable [User IDs] [INFO] Current user: root (UID=0, GID=0) [OK] PUID=1000 (containers run as UID 1000) [OK] PGID=1000 (containers run as GID 1000) [Container Egress] [WARN] Container egress check failed — sbproxy cannot reach webhook.tomsparkbox.com. This is fine if you only need free SparkBox. Optional Pro-tier license activation won't work until egress is restored, but every bundled app (Jellyfin, Pi-hole, Vaultwarden, etc.) runs the same either way. If you DO want to fix it (Pro tier only): 1. UFW: grep DEFAULTFORWARDPOLICY /etc/default/ufw (should be ACCEPT) 2. Run: sudo sparkbox repair-network 3. If you have a custom /etc/docker/daemon.json, check its DNS settings. Re-run 'sparkbox doctor' to verify. [Port Conflicts] [WARN] Port 53: in use by non-Docker process LISTEN 0 1000 10.255.255.254:53 0.0.0.0: [OK] Port 80: in use (Docker -- likely SparkBox) [OK] Port 443: in use (Docker -- likely SparkBox) [OK] Port 8080: available [OK] Port 8443: in use (Docker -- likely SparkBox) [OK] Port 9000: in use (Docker -- likely SparkBox) [OK] Port 9092: available [Portainer Auth] [WARN] Portainer returned HTTP 000000 (unexpected — try again in 30s or check 'docker logs sb-portainer') [VPN Tunnel] [OK] Gluetun tunnel is healthy [Hardware Transcoding] [INFO] /dev/dri not found -- Intel/AMD hardware transcoding not available [Media Storage] [OK] MEDIAROOT=/opt/sparkbox/data/media exists [OK] MEDIAROOT is writable [OK] Your apps (user id 1000) can read your media library [INFO] Free space at MEDIAROOT: 931GB [System Resources] [INFO] Total RAM: 4798MB [INFO] Available RAM: 2604MB [OK] RAM looks sufficient for 5 enabled modules [INFO] Free disk at SBROOT: 931GB [Container Health] [OK] All SparkBox containers are running [Tailscale Reachability] [OK] Dashboard reachable on the LAN IP (172.21.149.214:8443) — no Tailscale route shadow ============================================ 1 issue(s) found. Review warnings above and fix as needed. ============================================
Chris wrote:
Thanks for the full doctor run — your box is in better shape than that error suggested: every container is up, the VPN tunnel is healthy, and there is plenty of space. Two separate things went wrong here. The dashboard's update button does its download from inside one of your apps, and that is the same thing failing as the container egress warning further up your output. Separately, on v1.6.389 the sparkbox update command only refreshes your apps' images — it never moves SparkBox itself to a newer release. Over SSH, run this one instead: sudo sparkbox upgrade That downloads straight from your box rather than through an app, so it steps around the failed lookup. Your settings and media are preserved. You should land on v1.6.435 — it is a big jump from where you are, so give it a few minutes. If that download fails too, paste what it says and we will take the network side apart properly.
Majorman747 wrote:
Thanks! that worked!
Chris wrote:
Nice — that puts you on v1.6.435. One practical note for next time: that app-internet warning in your doctor output isn't going to clear on its own, so the dashboard's Update button will most likely fail the same way again. Easiest habit is to just update over SSH with sudo sparkbox upgrade — it worked here, and it keeps working regardless of that warning. Your box looks healthy otherwise, so there's nothing else you need to chase right now.
Chris wrote:
Coming back to you here because your VPN thread has hit a reply limit on my end, and this correction matters more than anything else in it. There I told you to run sudo sparkbox update to pick up Tom's v1.6.443 VPN fix. That was wrong — update only refreshes your apps' images and can never move you onto a newer release, so that fix has never reached your box. You are still on v1.6.435. You already found the right command in this thread. Run sudo sparkbox upgrade, then set WireGuard MTU to 1200 under Settings → Media Center → Advanced. If it still will not connect, tell me and it stays with Tom.
tomspark wrote:
Heads up — 1.6.520 just shipped and should cover what you reported here. You can grab it straight from the dashboard: Settings → Updates → Update SparkBox. Let me know if that sorts it, or if you're still hitting it. (Prefer the terminal? sudo sparkbox upgrade — note update only refreshes app images and will not move you to a new release.)