you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 3 months ago (33 children)

Setting up Jellyfin to be accessible outside of my home network has been a huge pain in the ass.

Not Jellyfin’s fault tho. I wish there was an easier way

  • source
  • parent
  • hideshow 33 child comments
  • [–] 9 points 3 months ago (7 children)

    I use tailscale and NPM to reverse proxy.

    When I want to watch, I turn on the VPN and go to the app. Easy peazy

  • source
  • parent
  • hideshow 7 child comments
  • [–] 4 points 3 months ago (6 children)

    Tailscale could probably be easier but I wanted to make it easy for my parents.

    I was trying to set it up via Reverse Proxy in Caddy. My stupid NAS has proprietary software and the only way to do it is in Docker but their version of docker has some wonky issues with ports.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 3 months ago (5 children)

    Oh, I use caddy too. What gave you trouble?

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 3 months ago (4 children)

    It’s been a few weeks since I’ve tinkered with it but I plan on pulling it up today. If I remember right, it works fine if I launch it as a singular container by itself, but if I launch it inside a container with multiple apps, it says the ports are in use. I verified that no other app is using the ports. I checked in the CLI and it says containers is using the port. Very weird.

    Following tutorials and researching online had been helpful by my NAS uses QNAP’s QTS operating system. It locks you out of many basic functions. I can’t install apps outside of its App Store unless it’s in a docker container, for example.

    Many command line functions have also been removed so when I’m troubleshooting or looking for alternate fixes, I’m blocked out.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 3 months ago* (3 children)

    You nas doesn't support docker compose? Its kind of the only reason why you'd want to have several processes on the same container.

    Ps.: can you ssh in?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 3 months ago (2 children)

    I can use docker compose. I need them on the same container so they can see the other apps exist and direct traffic there. Or that I as my understanding.

    I tried setting up Caddy on a separate container as Jellyfin but that didn’t work.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 months ago

    I need them on the same container so they can see the other apps exist and direct traffic there.

    That's only by default, since all apps in a container share a network. I got this working with my *arr stack using multiple containers by manually creating a shared network in the console, then adding that network to each compose file. Works like a dream.

  • source
  • parent
  • [–] 7 points 3 months ago* (2 children)

    It’s not easy trying to set up VPN or a reverse proxy, dynamic DNS and so on if you want secure access for more than yourself l, that is true. I hope they can figure out a way to make that process a lot easier.

    Actually, using an LLM to walk you through the process of setting up jellyfin inside a docker container (and setting up the arr stack) and all of that makes things a lot easier than trying to figure it all out on your own.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 3 months ago

    That was a big reason I went with Emby. Not open source, but wasn't necessary to me, and I wanted a cloud connect function that it handled well. And not all devices have a Jellyfin app that's easy to install. My TV would require it to be rooted.

  • source
  • parent
  • [–] 1 point 3 months ago (18 children)

    Fair, but self hosting stuff has that part of self. It is difficult to make it easy for everyone since everyone has a different setup, as such it is mostly directed towards people who are expert in doing this kinds of things or who will dedicate the time to learn how to do it.

    The good thing is after you spent a couple days trying to figure out how to make it work, it will work in the future and you already know how to setup more stuff.

  • source
  • parent
  • hideshow 18 child comments
  • [–] 0 points 3 months ago (16 children)

    It’s not directed towards people who are experts. I’m an expert and can’t secure Jellyfin properly because Jellyfin doesn’t support proper secure authentication.

  • source
  • parent
  • hideshow 16 child comments
  • [–] 0 points 3 months ago (13 children)
  • [–] 2 points 3 months ago* (12 children)

    I would rather just properly secure it like every other selfhosted service I have, and not have to manage a VPN client for every user who wants to connect to Jellyfin.

  • source
  • parent
  • hideshow 12 child comments
  • [–] 0 points 3 months ago (11 children)

    A security focused service vs a media consumption service competing for max security...

    I wonder what would be the most successful at this task...

  • source
  • parent
  • hideshow 11 child comments
  • [–] 2 points 3 months ago* (10 children)

    A security focused authentication service would be the most successful, straightforward, and simple to implement solution.

    Unfortunately Jellyfin, nearly alone amongst its FOSS peers has not implemented support for these services. It’s the only one of my many dozens of selfhosted services that I can’t properly secure.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 1 point 3 months ago (9 children)

    There are plugins for SSO.
    There are 3rd party plugins for OIDC and I think LDAP is even first party.
    The issue comes when intercepting the signin-progress with 1st party clients. Jellyfin (to my knowledge) doesnt support redirects/callbacks like a homeassistant companion app does.
    And how many media servers are there? The 2 other major offerings (Plex and Emby) don't support OIDC either.
    Plex does it's own sauce and Emby doesnt support it. Authentik has a guide to implement it via LDAP.

    And Jellyfin has a tech-debt history being forked from emby. Stark contrast to newly developed projects which were started when SSO and OIDC wasbstarting to become popular.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 1 point 3 months ago (5 children)

    Yeah, natively Jellyfin supports LDAP (1st party plug-in anyway), which means I can use my personal IdP to centrally manage accounts and it works across all their apps I've tried (as oppose to the OIDC plugin which seems to still break their apps).

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 3 months ago (4 children)

    Forgot that LDAP is sort of first party.
    Does the jellyfin app support the ldap auth?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 months ago (3 children)

    Yep, as far as I'm aware, it's the only way to use a separate IdP with the official apps.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 3 months ago (2 children)

    Very neat!
    Sadly I suspect that if I'd access it through authelia (and other reverse proxies) that the redirect will break the accessibility.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 months ago (2 children)

    Plugins for SSO and OIDC are not a solution as they will only work with the web clients, so that’s a non-starter.

    Jellyfin can blame it on the tech debt all they want but implementing it really wouldn’t be that hard, they just haven’t prioritized it, simple as.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 months ago (1 child)

    This sounds lile you are very knowledgable about it.
    Why not propose a dev-draft or propose a feature on their feature voting website?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 months ago* (last edited 3 months ago)

    Because it’s already a proposed feature on their feature voting website. In fact It’s been one of the top voted features for the last 7 years straight. It’s at this point the most often talked about drawback of Jellyfin and biggest stated reason why people won’t switch away from Plex. It’s been so long that the SSO plugin has been archived because the maintainer only made it on a temporary basis and he was tired of maintaining it, likely because it’s only taken the pressure off of the Jellyfin team to implement native SSO because folks like you like to point to it as a solution to the problem.

  • source
  • parent
  • [–] 0 points 3 months ago

    I actually love when I run into an issue like that get an error. Researching that stuff is fun for me, but I think trying to get the average person to do it is a non-starter

  • source
  • parent