I’m using cloudflare tunnel to access my movie collection on selfhosted jellyfin. Jellyfin accounts are behind a strong password.
Considering it’s on the web, how bad is it? I’m not thinking about attacks, can I be flagged for piracy or things? Where does the ISP stand?
why not have nothing exposed and just use tailscale
deleted by creator
why is this downvoted? tailscale works amazingly well…
I would suggest to put it behind an sso service like a self hosted authelia or authentik. So even if someone finds your website they will only see your authentication page and not what’s behind it.
How would that work with a Jellyfin client running on a device like a Chromecast dongle? The code on the dongle doesn’t (IMHO) know how to log into an SSO service.
You would have to exclude the */api/ path in the authentik provide settings, so that if something wants to call the jellyfin api (like Swiftfin) it can go around the sso. It’s not the best practice for security but the only working way I have found.
Why would that be a benefit? Jellyfin already provides a login screen (allegedly with strong passwords)
Like I said. So even if someone find your domain to your jellyfin server they would only see Authentik.
And if you start with authentik you could use it for much more self hosted services so you have one big login page in front of your services.
Ooh, I like the sound of that.
I really gotta find a straight forward install guide for Authelia.
Cloudfare offers an authentication service like that already. Really easy to set up in front of a tunnel
Jellyfin is a media player. It’s built in security is more than enough for most. A lot use it for access to their own personal collections. You’re using it for your own use, you’re not distributing so doubtful anybody would care. There’s no way to know what’s there so not worth anybody’s time. Now if you were selling logins to that server and advertising the content then things would be different in the same way that if you seed pirated content they will care more than if you just leech it. For all they know you could have your personal home videos behind it or legitimate backups of physical disks you own. Hide it behind a subdomain and random path then unless somebody is looking for it they won’t stumble on it in the first place. This should be enough really. Jellyfin is designed to keep your content secure. The only way somebody official would come knocking is if they suspect there’s something to hide. Unless you tell people they have no reason to suspect. They have much bigger fish to fry.
I don’t think you have anything to worry about but you can ofc secure things further if you want to jump through a few mostly unrequired hoops.
That’s just my personal opinion. If you don’t feel safe exposing it then you shouldn’t and should setup a vpn or similar and hide it all behind that. My jellyfin has been exposed for years. Just me and my family using it. I’ve never had anybody try to access it. Nothing exciting behind it other than family videos but nobody knows that.
i cant imagine a anti piracy organisation hacking into your server for the purpose of suing you
I using Plex with 2FA.
My jellyfin and jellyseerr both servers are open to web.because so many people using it i can’t sacrifice accessibility.but i have hardcore monitoring,alert system and emergency shutdown systems in place.
Same situation here but my users are all just friends and family so what I did was whitelist access from my own country and blacklist everything else. Not bulletproof of course but it did cut down on unintended traffic by nearly 100%
As long as passwords are strong it’s usually fine, I use ldap through jellyfin on authentik and everyone gets a passphrase.
And you will be banned. Cloudflare does not permit non-html traffic over their tunnels.
Are jellyfin Servers behind a Reverse Proxy realy such a big Security risk?
It’s really not that bad especially if you setup access lists. That simple configuration alone eliminates most problems from even accessing the server.
I would like to know aswell, because that is my case.
JellyFin behind NPM listening on a non standard https port (4443) with a Letsencrypt SSL certificate
I serve to plenty of family members with chromecasts, smarttvs, laptops, smartphones… that may be not compatible with SSO.