22 replies
tomspark wrote:
Easy one — Lidarr ships with the media stack, just switched off by default. To turn it on: open your dashboard, find Lidarr (it'll show as Optional / Off) and flip it ON. SparkBox starts it for you automatically (it lands on port 8686). One heads-up: once it's running, Lidarr needs connecting to Prowlarr (for indexers) and your download client (qBittorrent or SABnzbd). For Lidarr that part isn't automatic yet, so you'll add those manually — same idea as the SABnzbd connection you just did. Happy to walk you through it once it's up; just give me a shout.
jackhammer57 wrote:
The Lidarr container is not getting installed. I click the slider then click restart all I get an error. So I try clicking slider then through the terminal sudo sparkbox restart media The slider is showing as enabled. But I open docker and there’s no Lidarr container. Is there terminal commands to enable Lidarr?
tomspark wrote:
Ah — flipping the toggle sets Lidarr to 'on', but a restart doesn't always actually start a newly-enabled optional app like Lidarr. The command that does is a full up: sudo sparkbox up That re-reads what's enabled and brings Lidarr online. Give it a moment, then check: sudo docker ps | grep lidarr You should see sb-lidarr appear. If it's still missing after that, run this so we can confirm the toggle actually saved: grep LIDARRENABLED /opt/sparkbox/.env (it should say =true). Tell me what those two show and we'll get it running.
jackhammer57 wrote:
sudo docker ps | grep lidarr, Gives nothing just a new prompt. Lidarrenabled=true
jackhammer57 wrote:
But Lidarr doesn’t show up on the dashboard nor does it show when I try to open through port 8686 and the container isn’t showing up in docker
tomspark wrote:
Ok — so the enable isn't actually taking. I need to see two things to know why. Paste what these show: grep LIDARRENABLED /opt/sparkbox/.env sudo sparkbox up 2&1 | tail -20 The first tells me whether the toggle actually saved the setting (it should say LIDARRENABLED=true). The second's last lines will show any error when it tries to start. My bet is the toggle didn't write the flag — if so, I'll give you a one-liner to set it directly. We'll get Lidarr going.
jackhammer57 wrote:
Joe@DXP4800PRO-868A:~$ grep LIDARRENABLED /opt/sparkbox/.env sudo sparkbox up 2&1 | tail -20 LIDARRENABLED=true Container sb-immich-db Waiting Container sb-immich-redis Waiting Container sb-immich-db Healthy Container sb-immich-redis Healthy [OK] SparkBox is running! Service URLs: Core Infrastructure: Nginx Proxy Manager: http://192.168.4.41:81 Portainer: http://192.168.4.41:9000 Homepage: http://192.168.4.41:3000 SparkBox Dashboard: SparkBox Dashboard: http://192.168.4.41:8443 Immich: Immich: http://192.168.4.41:2283 Joe@DXP4800PRO-868A:~$
tomspark wrote:
That output cracks it — the toggle saved fine (LIDARRENABLED=true), but look at what your 'up' actually started: only Core, the Dashboard, and Immich. There's no media stack at all — no Jellyfin, Sonarr, Radarr or qBittorrent. That's the real reason Lidarr won't appear: Lidarr lives inside the Media module (it shares the same VPN tunnel and download client as Sonarr/Radarr), and that whole module isn't turned on yet. So flipping the Lidarr sub-toggle has nothing to attach to. To get Lidarr, you'd enable the Media module itself — and heads up, that's a bigger step than the photo stuff: the media apps route through a VPN, so it walks you through adding a VPN subscription (Surfshark etc.) as part of setup. Once Media is up, Lidarr comes online with it automatically since you've already toggled it. Want me to walk you through enabling the Media module?
jackhammer57 wrote:
That’s weird because I’ve already set up the media module.. I’ve set up qbit, SABn, Radarr, Sonarr, Prowlarr, jellyfin and Seerr
jackhammer57 wrote:
And they are all showing as healthy in the dashboard
tomspark wrote:
That's the bit worth double-checking — the dashboard can show an app's tile even when its container isn't actually running, so docker is the ground truth. Run this and tell me what comes back: sudo docker ps | grep -E 'lidarr|jellyfin|sonarr' If you see sb-lidarr (and sb-jellyfin-media, sb-sonarr) in that list, the media stack really is up and we just need to wire Lidarr in. If it comes back empty, the dashboard is showing tiles for apps that aren't running yet — which lines up with your earlier 'up' only starting Core + Immich. That one command tells us exactly where we stand.
jackhammer57 wrote:
Here’s the results Joe@DXP4800PRO-868A:~$ sudo docker ps | grep -E 'lidarr|jellyfin|sonarr' [sudo] password for Joe: 874438239d6f jellyfin/jellyfin:10.11.8 "/jellyfin/jellyfin" 4 days ago Up 12 minutes (healthy) 0.0.0.0:8096-8096/tcp, :::8096-8096/tcp sb-jellyfin-media
tomspark wrote:
Perfect, that tells us exactly what's happening: only Jellyfin (sb-jellyfin-media) is actually running — Sonarr and Lidarr aren't there at all. Here's the why: Sonarr, Radarr, qBittorrent, Prowlarr and Lidarr all run through your VPN connection, so if the VPN piece isn't up, none of them can start. Jellyfin doesn't use the VPN, which is exactly why it's the only one alive. So let's check the VPN. Run this: sudo docker ps -a | grep -E 'gluetun|sonarr|lidarr' If you see sb-gluetun showing 'Restarting' or 'Exited', that's the blocker — the VPN isn't connecting, and everything behind it (Lidarr included) stays down. Paste what it shows and we'll get it sorted.
jackhammer57 wrote:
Joe@DXP4800PRO-868A:~$ sudo docker ps -a | grep -E 'gluetun|sonarr|lidarr' 37c6a499a298 lscr.io/linuxserver/sonarr:4.0.17 "/init" 4 days ago Exited (128) 21 minutes ago sb-sonarr 07165c59ad3b qmcgaw/gluetun:v3.41.1 "/gluetun-entrypoint" 4 days ago Up 19 minutes (healthy) 0.0.0.0:7878-7878/tcp, :::7878-7878/tcp, 8000/tcp, 0.0.0.0:8191-8191/tcp, :::8191-8191/tcp, 8388/tcp, 0.0.0.0:8686-8686/tcp, :::8686-8686/tcp, 0.0.0.0:8989-8989/tcp, :::8989-8989/tcp, 8888/tcp, 8388/udp, 0.0.0.0:8089-8080/tcp, :::8089-8080/tcp, 0.0.0.0:8186-8081/tcp, :::8186-8081/tcp, 0.0.0.0:8181-9696/tcp, :::8181-9696/tcp sb-gluetun
tomspark wrote:
Really helpful — this pins it down. Good news first: your VPN (sb-gluetun) is up and healthy, so that's not the culprit. What I can see is Sonarr crashed (Exited 128) and Lidarr never got built at all. That usually means they tried to start a moment before the VPN was ready, and gave up. Now that the VPN's sitting there stable, let's give everything a clean start and watch what happens: sudo sparkbox up 2&1 | tail -30 Paste those last lines here — they'll show whether Sonarr and Lidarr come up this time, or the exact error if one of them still won't. We're close.
jackhammer57 wrote:
Joe@DXP4800PRO-868A:~$ sudo sparkbox up 2&1 | tail -30 Container sb-portainer Running Container sb-homepage Running Container sb-npm Running Container sb-immich-redis Running Container sb-immich-db Running Container sb-immich-ml Running Container sb-immich-server Recreate Container sb-immich-server Recreated Container sb-immich-redis Waiting Container sb-immich-db Waiting Container sb-immich-redis Healthy Container sb-immich-db Healthy Container sb-immich-server Starting Container sb-immich-server Started [OK] SparkBox is running! Service URLs: Core Infrastructure: Nginx Proxy Manager: http://192.168.4.41:81 Portainer: http://192.168.4.41:9000 Homepage: http://192.168.4.41:3000 SparkBox Dashboard: SparkBox Dashboard: http://192.168.4.41:8443 Immich: Immich: http://192.168.4.41:2283 Joe@DXP4800PRO-868A:~$
tomspark wrote:
Got it — this is the answer. Look at what your up actually started: Core, the Dashboard, and Immich, nothing else. SparkBox isn't even trying to start your media apps, which is exactly why Sonarr won't come back and Lidarr won't build. At some point (likely a reset or an update) the media module got switched off in SparkBox's own list — even though all your apps and your VPN are still set up and ready. Easy fix — switch it back on and start it: sudo sparkbox enable media && sudo sparkbox up You should see Jellyfin, Sonarr, Radarr, qBittorrent and Lidarr appear in the list and start up. Your existing setup and VPN stay exactly as they are. Tell me how the list looks after.
jackhammer57 wrote:
That looks like it fixed it. OK] All required images present. [+] Running 3/0 ✔ Container sb-portainer Running 0.0s ✔ Container sb-homepage Running 0.0s ✔ Container sb-npm Running 0.0s [+] Running 4/4 ✔ Container sb-immich-redis Healthy 0.0s ✔ Container sb-immich-ml Running 0.0s ✔ Container sb-immich-db Healthy 0.0s ✔ Container sb-immich-server Running 0.0s [+] Running 12/12 ✔ Container sb-deunhealth Running 0.0s ✔ Container sb-gluetun Healthy 0.0s ✔ Container sb-bazarr Started 4.5s ✔ Container sb-seerr Started 1.9s ✔ Container sb-jellyfin-media Started 1.4s ✔ Container sb-prowlarr Started 4.3s ✔ Container sb-sonarr Started 4.3s ✔ Container sb-lidarr Started 0.8s ✔ Container sb-radarr Started 4.3s ✔ Container sb-flaresolverr Started 0.9s ✔ Container sb-qbittorrent Running 0.0s ✔ Container sb-sabnzbd Running 0.0s [OK] SparkBox is running! [INFO] Auto-firing arr-bootstrap in the background (~90-180s)... [INFO] Jellyfin + Seerr credentials will appear in the launcher modals when ready. Service URLs:
tomspark wrote:
That's the one — your whole media stack is up now (Sonarr, Radarr, Lidarr, qBittorrent, the lot), and Lidarr finally built. Give it 2-3 minutes: SparkBox is auto-wiring the apps in the background right now. One thing left for Lidarr specifically: unlike the others, it doesn't get auto-connected to Prowlarr (your indexers) and your download client yet — that part's still manual. Happy to walk you through those two connections whenever you're ready; it's quick. Out of curiosity, so I can stop this biting anyone else: do you remember if you ran a reset, an update, or toggled something in the dashboard right before the media apps went missing? Totally fine if not.
jackhammer57 wrote:
I think the problem came about when we were trying to get seerr up and running did sparkbox reset media and then had issues with the dashboard not coming up. But I’m unable to pinpoint it any closer than that.
tomspark wrote:
That's a genuinely useful clue — thank you. You shouldn't be able to knock the media stack off SparkBox's list just by setting up Seerr, so the fact that it lined up with that is exactly the kind of detail that helps us track down why it happened. I've flagged it on our end. Either way, you're back up and running now, which is the main thing. The one loose end is Lidarr — it's the odd one out that doesn't auto-connect to your indexers and downloader yet. Want me to give you the two quick steps to wire it up? Takes about a minute.
jackhammer57 wrote:
Thanks. I think I’m good on the Lidarr set up. I got qbit and SABn set up as the download clients, and prowlarr as the indexer and have successfully downloaded my first albums with everything working correctly.