this post was submitted on 04 Jun 2024
18 points (100.0% liked)
Jellyfin: The Free Software Media System
5475 readers
36 users here now
Current stable release: 10.9.7
Matrix (General Information & Help)
Matrix (Off-Topic) - Come get to know the team and blow off steam!
Matrix Space - List of all the available rooms on Matrix.
Discord - Bridged to our Matrix rooms
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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
Hopefully you setup your configuration folders as an external mount outside the container. 👍
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
Ok, just don't go too far until you are sure the config and database won't be wiped when you update the image.