For both, when it opens a webpage I get the message "This sight can't be reached." Any help would be appreciated. Thank you.
9 replies
Chris wrote:
Nothing's broken here — that message just means the app isn't running yet, so the browser has nothing to open. Lidarr and Chaptarr both run through your VPN, so they only come up once the VPN is connected. Open a terminal on your box and run: sudo sparkbox up — then wait a couple of minutes and click each tile again. If they still won't open, tell me which one (or both) and what the VPN tile on your dashboard shows, and I'll walk you through the next step.
kaufman51 wrote:
Both still won't open after, VPN tile show green/protected. Pipeline healthy, all connected.
Chris wrote:
That actually helps narrow it down — a green VPN and a healthy pipeline mean Lidarr and Chaptarr are running; the browser just can't reach the address the tile is pointing at. In your terminal run sparkbox urls and open the Lidarr and Chaptarr addresses it prints directly. If they load there, it's only the tile link and I'll get that sorted. One quick thing that'll tell me which fix applies: are you running SparkBox inside WSL on a Windows PC, or on a separate NAS/box? That changes the next step, so I don't want to guess.
kaufman51 wrote:
I tried opening the address that were listed in the terminal and same result/same error message. I am running SparkBox on a Ugreen NAS
Chris wrote:
Thanks — that's the detail I needed. Two different things are going on. Chaptarr is brand new, and we've already found a bug on our side: its port was left out of the VPN's allowed list, so even when it's running, the browser can't reach it. That's logged with Tom and being fixed — there's nothing to change on your end, and it'll arrive through sudo sparkbox upgrade once it ships. Lidarr is wired correctly on our side, so that one we should look at together: run sudo sparkbox doctor and reply with what it prints, and I'll take it from there.
kaufman51 wrote:
/ | | | | ) \ \| ' \ / | '| |/ / \ / \ \/ / ) | |) | (| | | | <| |) | () < |/| ./ \,|| ||\\/ \//\\ || SparkBox v1.6.613 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Environment: NAS (generic) 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): /volume1/sparkbox-data/media [WARN] Listed more than once in .env: PIHOLEDNSBIND Only the LAST line for each of those is used, so an edit higher up the file does nothing. Collapse each one to a single line with: sudo sparkbox set-env PIHOLEDNSBIND <the value you want [Docker] [OK] Docker daemon is accessible [OK] Docker version: Docker version 26.1.0, build 9714adc [OK] Docker Compose: 2.26.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=10 (containers run as GID 10) [Container Egress] [OK] Apps can reach webhook.tomsparkbox.com over sbproxy (their real network) [OK] Docker's default bridge can reach tomsparkbox.com (dashboard Update button) [Port Conflicts] [OK] Port 8080: in use by SparkBox (sb-npm) [OK] Port 8444: in use by SparkBox (sb-npm) [OK] Port 8443: in use by SparkBox (sb-dashboard) [OK] Port 9000: in use by SparkBox (sb-portainer) [OK] Port 53: in use by SparkBox (sb-pihole) [Portainer Auth] [OK] Portainer admin login verified (HTTP 200) [VPN Tunnel] [OK] Gluetun tunnel is healthy [Hardware Transcoding] [OK] /dev/dri exists -- GPU devices detected total 0 drwxr-xr-x 3 root root 100 Aug 22 10:17 . drwxr-xr-x 19 root root 7540 Aug 22 10:17 .. drwxr-xr-x 2 root root 80 Aug 22 10:17 by-path crw-rw---- 1 root video 226, 0 Aug 22 10:17 card0 crw-rw---- 1 root render 226, 128 Aug 22 10:17 renderD128 [OK] Intel Quick Sync / GPU render device available (renderD128) [OK] Render device is accessible by current user [OK] sb-jellyfin-media is in the host's real render group (105) [Media Storage] [OK] MEDIAROOT=/volume1/sparkbox-data/media exists [OK] MEDIAROOT is writable [OK] Your apps (user id 1000) can read your media library [INFO] Free space at MEDIAROOT: 457GB [System Resources] [INFO] Total RAM: 7691MB [INFO] Available RAM: 3786MB [OK] RAM looks sufficient for 7 enabled modules [INFO] Free disk at SBROOT: 11GB [NAS-Specific] [INFO] NAS type: generic [INFO] Install directory: /opt/sparkbox [WARN] Install directory is on system partition -- consider moving to a data volume There is no one-shot move command. The supported route is: 1. sudo sparkbox backup 2. copy the archive somewhere off this partition 3. re-install with: --install-dir <path on your data volume 4. sudo sparkbox restore <archive Restore now rewrites SBROOT in the settings file to the new location. [Container Health] [OK] All SparkBox containers are running and passing their health checks [Saved Passwords] [WARN] sb-jellyfin-media: the password saved in state/jellyfin-admin-password.txt is NOT accepted (HTTP 401). [WARN] This happens after a reinstall over existing data, or if the password was [WARN] changed inside the app itself — the saved copy then drifts out of sync. Fix it with: sudo /opt/sparkbox/sparkbox reset-password jellyfin [Tailscale Inbound Path] [OK] Tailscale's inbound path reaches the dashboard (127.0.0.1:8443 from inside sb-tailscale) — phones on your tailnet can get through [Tailscale Reachability] [OK] Dashboard reachable on the LAN IP (192.168.1.101:8443) — no Tailscale route shadow ============================================ 1 issue(s) found. Review warnings above and fix as needed. ============================================
Chris wrote:
Thanks — that readout is clean, and it tells us what we need: no port clashes, VPN healthy, and both apps up and passing their checks. Chaptarr is our bug — its port never got into the VPN's allow-list, so it can't open until the fix ships via sudo sparkbox upgrade. Nothing for you to change there. Lidarr is wired correctly. Your box's address is 192.168.1.101 (the doctor shows it), so from a computer on the same home network open exactly http://192.168.1.101:8686. If the links you tried earlier began with a different number, that's the stale address. If that exact one still won't open, tell me and I'll go from there.
kaufman51 wrote:
Same address still wont open
Chris wrote:
I hear you — this has dragged on longer than it should, and I'm sorry it's still stuck. Let's settle it with one clean test. Chaptarr is on us: its page stays shut until the fix ships, so nothing to change there. For Lidarr, everything checks out on our side, so let's find the exact wall. On the NAS, in the same terminal you used for the doctor, run: curl -I http://localhost:8686 If the first line it prints starts with "HTTP/1.1 200", Lidarr is up and the wall is between your computer and the NAS — tell me how your computer reaches it (same WiFi? wired? a different network?). If it hangs or says "connection refused" instead, paste what it prints and I'll take it straight to Tom.