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

  • Kaefor@lemmy.ca
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 months ago

    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.worldOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      5 months ago

      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
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 months ago

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

        • RGB3x3@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          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
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 months ago

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