4 replies
tomspark wrote:
Hey — this one's usually just the Jellyfin address field inside Seerr. It needs to be exactly http://sb-jellyfin-media:8096 (not localhost, not your NAS's IP address). In Seerr, go to Settings Jellyfin, fix that field if it's wrong, save, and try connecting again. If it's already set that way and still won't connect, reply here with the exact error text you see on screen and I'll dig further.
Grenshal wrote:
Thanks for the quick response, Seerr won't allow me to sign in at all, it is giving me the error message that it can't connect to jellyfin sever.
tomspark wrote:
Since it's blocking you right at sign-in (not just a wrong address), the best next step is a clean reset of Seerr's setup. SSH into your box and run: sudo sparkbox repair-seerr - that rebuilds Seerr fresh so it can talk to Jellyfin again. Once it finishes, open Seerr and try signing in once. If it still won't connect, copy the exact error text or a screenshot of what pops up and send it over, that'll tell me exactly what's happening.
Chris wrote:
Please don't run that one, and I'm sorry it was suggested. repair-seerr deletes Seerr's whole config folder, and for a sign-in that has never worked it just hands you back the same empty wizard. The address is the more likely culprit. That Jellyfin screen has a separate hostname box and Port box, so the full http://sb-jellyfin-media:8096 pasted into the first one will never resolve. Fill them in separately: Hostname: sb-jellyfin-media Port: 8096 Use SSL: unticked Username: the one you chose in Jellyfin's own setup screen, not sparkbox Seerr keeps no accounts of its own, it checks that pair straight against Jellyfin, so your own login is the one it accepts. — Chris