this post was submitted on 31 Mar 2025
213 points (98.2% liked)

Selfhosted

45658 readers
832 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I already host multiple services via caddy as my reverse proxy. Jellyfin, I am worried about authentication. How do you secure it?

(page 3) 46 comments
sorted by: hot top controversial new old
[–] geography082@lemm.ee 1 points 1 week ago

My setup is: Proxmox - restricted LXC running docker which runs jellyfin, tailscale funnel as reverse proxy and certificate provider. So so don't care about jellyfin security, it can get hacked / broken , its an end road. If so i will delete the LXC and bring it up again using backups. Also i dont think someone will risk or use time to hack a jellyfin server. My strategy is, with webservices that don't have critical personal data, i have them isolated in instances. I don't rely on security on anything besides the firewall. And i try not to have services with personal sensitive data, and if i do, on my local lan with the needed protections. If i need access to it outside my local lan, vpn.

[–] CapitalNumbers@lemm.ee 1 points 1 week ago* (last edited 1 week ago) (2 children)

So i’ve been trying to set this up this exact thing for the past few weeks - tried all manner of different Nginx/Tailscale/VPS/Traefik/Wireguard/Authelia combos, but to no avail

I was lost in the maze

However, I realised that it was literally as simple as setting up a CloudFlare Tunnel on my particular local network I wanted exposed (in my case, the Docker network that runs the JellyFin container) and then linking that domain/ip:port within CloudFlare’s Zero Trust dashboard

Cloudflare then proxies all requests to your public domain/route to your locally hosted service, all without exposing your private IP, all without exposing any ports on your router, and everything is encrypted with HTTPS by default

And you can even set up what looks like pretty robust authentication (2FA, limited to only certain emails, etc) for your tunnel

Not sure what your use case is, but as mine is shared with only me and my partner, this worked like a charm

[–] vodka@lemm.ee 1 points 1 week ago (2 children)

Pay attention to your email, when cloudflare decides to warn you for this (they will, it's very very much against TOS) they'll send you an email, if you don't remove the tunnel ASAP, your entire account will be terminated.

load more comments (2 replies)
load more comments (1 replies)
[–] jagged_circle@feddit.nl -2 points 1 week ago (1 children)

Kinda hard because they have an ongoing bug where if you put it behind a reverse proxy with basic auth (typical easy button to secure X web software on Internet), it breaks jellyfin.

Best thing is to not. Put it on your local net and connect in with a vpn

[–] satans_methpipe@lemmy.world 1 points 1 week ago (1 children)

I'm not experiencing that bug. My reverse proxy is only accessed locally at the moment though. I did have to play with headers a bit in nginx to get it working.

[–] jagged_circle@feddit.nl 1 points 1 week ago (1 children)

Basic auth. The bug is if you enable basic auth.

[–] satans_methpipe@lemmy.world 1 points 1 week ago (1 children)

It is enabled, but now I'm doubting that. I'll double check when my homelab shift is complete.

load more comments (1 replies)
[–] softcat@lemmy.ca -3 points 1 week ago (9 children)

CloudFlare tunnel with Zero Trust, plus their bot and abuse blocking. Users can get in with the right oauth, plus only allowed from the countries I know they're in. Then just their username and password on jellyfin.

[–] Netrunner@programming.dev 1 points 1 week ago* (last edited 1 week ago) (1 children)

Using cloudflare tunnels means nothing is encrypted and cloudflare sees all.

[–] softcat@lemmy.ca 0 points 1 week ago

Oh no they'll see I'm watching TNG

[–] rice@lemmy.org 1 points 1 week ago (2 children)

just run wireguard on the jelly server..

[–] jagged_circle@feddit.nl 1 points 1 week ago

Can't use double VPN on mobile.

[–] softcat@lemmy.ca 1 points 1 week ago (1 children)

My users aren't going to figure that out.

[–] rice@lemmy.org 0 points 1 week ago (1 children)

they don't have to figure it out, you are the one running it

load more comments (1 replies)
load more comments (7 replies)
[–] Mubelotix@jlai.lu -3 points 1 week ago* (last edited 1 week ago) (8 children)

~~Jellyfin is secure by default, as long as you have https. Just chose a secure password~~

load more comments (8 replies)
load more comments
view more: ‹ prev next ›