Bug, still can't get medieserver to run

Posted by Amilo21

Hey Tom Have tried like a zillion things, and your TomAI have helped tremendesously with setting everthing up and how to connect the apps with API keys etc and where to do it. But somehow there is still some issues that might be a bug, and perhaps not one of my mistakes. The next is from TomAI But here's a summary you can paste as context: --- Dashboard tiles red — Radarr/Sonarr/Prowlarr "not answering" despite healthy containers SparkBox: v1.6.257 | Platform: UGREEN NAS | Install: /opt/sparkbox | Media root: /volume2/Multimedia What's happening: Dashboard health tiles show Radarr, Sonarr, and Prowlarr as unreachable after a sparkbox up. All containers are confirmed healthy in Docker. Root cause found: sb-dashboard compose only connects to sbproxy. Media apps are behind sb-gluetun on sparkboxsbmedia. The two networks never overlap, so the dashboard literally cannot resolve sb-gluetun by name. What was tried: - docker network connect sparkboxsbmedia sb-dashboard → ping to sb-gluetun:7878/ping now returns {"status":"OK"} - docker restart sb-dashboard after network fix → tiles still red - Hard refreshes throughout — no change Suspected bugs (needs a proper fix): 1. Dashboard compose missing sbmedia network — workaround drops on every sparkbox up 2. Dashboard health state appears cached/stuck — doesn't recover even after connectivity restored

3 replies

tomspark wrote:

You didn't break anything, and your apps are actually fine — Docker shows them healthy, so this is the dashboard losing track of them after a restart, not the apps themselves going down. The clean way to get the dashboard and your media apps talking again is to restart the media group together so they re-link: sudo sparkbox restart media Give it a minute, then refresh the dashboard — the Radarr/Sonarr/Prowlarr tiles should go green. If they're still red after that, tell me which ones and run sudo sparkbox doctor for me. At that point it's something on our end to chase down, not yours.

Amilo21 wrote:

Still doesn't seem to connect. The apps are green under medieserver app under apps, but the media pipeline is red at "Download app" and yellow at "! indexers" Martin@SecretLairNAS:~$ sudo sparkbox doctor / | | | | ) \ \| ' \ / | '| |/ / \ / \ \/ / ) | |) | (| | | | <| |) | () < |/| ./ \,|| ||\\/ \//\\ || SparkBox v1.6.257 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Environment: NAS (ugreen) 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): /volume2/Multimedia [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] Containers can reach webhook.tomsparkbox.com (license server) [Port Conflicts] [WARN] Port 53: in use by non-Docker process LISTEN 0 32 127.0.0.1:53 0.0.0.0: users:(("dnsmasq",pid=1461,fd=5)) [WARN] Port 80: in use by non-Docker process LISTEN 0 511 0.0.0.0:80 0.0.0.0: users:(("nginx",pid=53073,fd=6),("nginx",pid=53072,fd=6),("nginx",pid=53071,fd=6),("nginx",pid=53070,fd=6),("nginx",pid=53069,fd=6),("nginx",pid=53068,fd=6),("nginx",pid=53067,fd=6),("nginx",pid=53066,fd=6),("nginx",pid=1536,fd=6)) [WARN] Port 443: in use by non-Docker process LISTEN 0 511 0.0.0.0:443 0.0.0.0: users:(("nginx",pid=53073,fd=8),("nginx",pid=53072,fd=8),("nginx",pid=53071,fd=8),("nginx",pid=53070,fd=8),("nginx",pid=53069,fd=8),("nginx",pid=53068,fd=8),("nginx",pid=53067,fd=8),("nginx",pid=53066,fd=8),("nginx",pid=1536,fd=8)) [OK] Port 8080: in use (Docker -- likely SparkBox) [OK] Port 8443: in use (Docker -- likely SparkBox) [OK] Port 9000: in use (Docker -- likely SparkBox) [OK] Port 9092: available [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 Jun 15 10:11 . drwxr-xr-x 20 root root 7600 Jun 15 10:11 .. drwxr-xr-x 2 root root 80 Jun 15 10:11 by-path crw-rw---- 1 root video 226, 0 Jun 15 10:11 card0 crw-rw---- 1 root render 226, 128 Jun 15 10:11 renderD128 [OK] Intel Quick Sync / GPU render device available (renderD128) [OK] Render device is accessible by current user [Media Storage] [OK] MEDIAROOT=/volume2/Multimedia exists [OK] MEDIAROOT is writable [OK] Your apps (user id 1000) can read your media library [INFO] Free space at MEDIAROOT: 7387GB [System Resources] [INFO] Total RAM: 7712MB [INFO] Available RAM: 3388MB [OK] RAM looks sufficient for 4 enabled modules [INFO] Free disk at SBROOT: 97GB [NAS-Specific] [INFO] NAS type: ugreen [INFO] Install directory: /opt/sparkbox [WARN] Install directory is on system partition -- consider moving to a data volume [Container Health] [OK] All SparkBox containers are running ============================================ 3 issue(s) found. Review warnings above and fix as needed. ============================================ It looks like its some issues with port 53, 80 and 443. But don't understand what to do about it.I'm gonna try TomAI again, and hope for the best

tomspark wrote:

Those port 53 / 80 / 443 warnings are just your NAS's own web server and DNS already using those ports — totally normal, and NOT what's causing the red tiles, so you can ignore them. I tracked down the real cause: on some NAS setups the dashboard can't reach your media apps through the firewall the way it checks them, so the tiles show red even though the apps themselves are perfectly fine. A fix is on the way in the next update and you won't need to do anything for it. I went into a bit more detail on your newer thread too. Thanks for the full doctor output — that helped.