Seerr error Unable to connect to Jellyfin server.
Posted by burkinar
Hello, I installed SparkBox on two separate local servers running Ubuntu 24.04 and 26.04. Everything went smoothly until I encountered the SEERR configuration issue. When I try to connect, I consistently receive the error message "Unable to connect to the Jellyfin server". After doing some research, I found a thread discussing this, but the SEERR connection errors aren't the same. I tried looking for the jellyfin-admin-password.txt file, but it doesn't exist in the folder. Could this be the cause? I'm asking for help to continue the deployment. link text cd /opt/sparkbox/state/
4 replies
tomspark wrote:
The jellyfin-admin-password.txt file doesn't exist because Jellyfin doesn't use a pre-generated password like qBittorrent or Pi-hole do — you create the admin account during Jellyfin's first-run wizard, and that credential isn't stored in state files. Seerr can't connect to Jellyfin because it needs the correct Jellyfin server address and admin username/password that you set up when you first logged into Jellyfin. Here's the fix: 1. Open your Jellyfin instance (port 8096 or 8097 depending on which bundle you're running) and confirm you've completed the setup wizard. If you see a login form, log in with the admin account you created. 2. In Seerr's Settings, under "Jellyfin Server," set: - Host/IP: Use the container name sb-jellyfin-media (internal Docker DNS) or 127.0.0.1 if on the same host - Port: 8096 - API Key / Username: The admin username you created in Jellyfin - Password: The admin password you created in Jellyfin - Use HTTPS: Off (internal Docker bridge doesn't need TLS) 3. Click "Save" and Seerr should connect. If it still fails, run docker logs sb-seerr --tail 50 and paste the error — it'll tell us if it's a network routing issue or auth mismatch. What username and password did you use when you first set up Jellyfin?
burkinar wrote:
Thank you for your reply; I just got it working thanks to your help. Let me explain: when choosing the Jellyfin name, I changed it to jellyfin-media I used this name instead of Jellyfin's IP address, 192.168.1.211. It works now. I'll continue the configuration. Thank you.
tomspark wrote:
Nice — that's exactly it. 🎉 The internal name works where the LAN IP doesn't here, so you're all set. Enjoy the rest of the setup!
tomspark wrote:
Nice — glad you got it sorted. The container name works great for internal Docker networking, so you're all set there. Enjoy the rest of the setup.