I have my JellyFin on a dedicated server outside my home. I use a domain, with and SSH certificate. Before I moved to the domain and the cert I just had an IP:Port setup. At that time JellyFin worked perfectly fine with the windows app, but after moving to the domain and adding an SSH cert, it no longer wants to connect. It works perfectly fine in FIreFox though, so I'm curious if it's worth trying to figure out why it won't work in the app, or is using FireFox just as good.

you are viewing a single comment's thread
view the rest of the comments

[–] possiblylinux127 1 points 8 months ago (1 children)

It sounds like you've at least taken some steps to harden. For me it is trivial to use a VPN so that's what I do.

[–] [email protected] 1 points 8 months ago (1 children)

A VPN would not be practical for my situation, as the instance is used by various family members and friends. I'm happy for them to use my JF instance but I'm not providing VPN services as well.

If you're not referring to any specific vulnerabilities in JF then I feel confident there are no exceptional risks from allowing web access to JF? Just the usual ones?

[–] possiblylinux127 1 points 8 months ago (1 children)

You don't need to give them access to a internet connection, just the local device. There are many options for this including Netbird, Tailscale, and just plain old wireguard.

[–] [email protected] 1 points 8 months ago

That's overly complicated for some of the users - most of them aren't very tech savvy, and they're watching via all kinds of devices - TV's, iOS, Kindle, etc.

I don't see any major security reason for access requiring a VPN. Are there particular vulnerabilities that you're concerned about, or just those that generally come from having a web-facing service?