Can't connect to Jellyfin running on docker on Synology NAS through any means?
from RGB3x3@lemmy.world to jellyfin@lemmy.ml on 04 Jun 2024 22:20
https://lemmy.world/post/16186379

I need some help. I’ve installed the Jellyfin container and it’s running on my Synology NAS. It seems fine, but I can’t get to the server through 192.168.x.x:8096. I get a typical “unable to connect.”

What settings do I need to configure to connect to it? I’ve already allowed the port on my Windows laptop.

Thanks

#jellyfin

threaded - newest

Kaefor@lemmy.ca on 05 Jun 2024 00:43 next collapse

Is port 8096 on the server the port that is sending data to port 8096 on Jellyfin?

What I mean by that is that you can choose the NAS port that forwards to the Jellyfin 8096 port. I have my docker image set to run port 55000 (server) to port 8096 (Jellyfin) so I then connect to the server at 192.168.x.x:55000 on my local WiFi.

Hope this helps (or that I at least understood your issue). I’m fairly new to self-hosting myself.

RGB3x3@lemmy.world on 05 Jun 2024 01:56 collapse

No, so I’m just straight up trying to connect to the NAS IP with port 8096, but can’t get through to anything.

So where I get to the Synology console through 192.168.x.x:5000, I’m trying 192.168.x.x:8096 and getting nothing.

Edit: Turns out the container was running local port 49154. Need to change that

CCMan1701A@startrek.website on 05 Jun 2024 03:12 collapse

Hopefully you setup your configuration folders as an external mount outside the container. 👍

RGB3x3@lemmy.world on 05 Jun 2024 08:45 collapse

Good point, I’m going to have to go through some more tutorials on how Synology’s stuff works. I’ve only just gotten my first NAS

CCMan1701A@startrek.website on 05 Jun 2024 12:53 collapse

Ok, just don’t go too far until you are sure the config and database won’t be wiped when you update the image.

hitmyspot@aussie.zone on 05 Jun 2024 04:02 collapse

Mariushosting has a great tutorial for this.