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?
Does jellyfin have known vulnerabilities for bots to exploit? It’s been up for several years with, afaik, no problems.
System has usual steps taken to harden it, JF is behind an apache proxy, letsencrypt handles ssl certs, fail2ban is running, and users are required to have strong passwords with no option to reset or self-register.
What’s the issue? I’ve run mine exposed for several years…
Possible, not practical.
I use substance painter and I need it to work. I don’t want to spend hours messing around trying to make it work and jumping through hoops.
Wine for DCC is great if you enjoy tinkering with pipelines rather than using them, but impractical for people who are trying to reliably get work done.
Streaming usage per person is available via one of the stats plugins, but it is admittedly crude and missing some info (such as bandwidth used).
I’m using the android app without issues, which didn’t require side loading, but my experience with other platforms is zero.
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?