this post was submitted on 23 May 2026
203 points (97.2% liked)

Selfhosted

60723 readers
300 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Assuming the user will not be connecting over vpn, but is both remote and non-technical, how would you expose Jellyfin to them securely?

(page 4) 50 comments
sorted by: hot top controversial new old
[–] BartyDeCanter@piefed.social 1 points 1 month ago (1 children)

Does Tailscale count as a VPN for you? It’s how I roll. Well, I run my own headscale server, but the free Tailscale tier is going to be fine for any reasonably sized personal project.

load more comments (1 replies)
[–] brickfrog@lemmy.dbzer0.com 1 points 1 month ago* (last edited 1 month ago) (1 children)

Adding onto the other comments, if you have admin access to your network router/firewall you can configure the incoming port forward itself to only allow specific IP addresses while dropping traffic from any other internet WAN IPs. It's a bit like using the Jellyfin whitelist/blacklist but doing it at the network level. This drops all unwanted internet traffic to that port at the firewall before ever reaching the Jellyfin software. Downside is having to occasionally update the firewall whenever there are IP address changes.

This is probably only feasible if you only have some specific Jellyfin clients in mind to accept connections from, not any random person from any random WAN IP address.

[–] FreedomAdvocate -1 points 1 month ago

This is a terrible idea, as you’re trusting their network and device security blindly.

[–] GreenKnight23@lemmy.world -2 points 1 month ago* (last edited 1 month ago)

you don't.

if you're intent on "spreading your legs" to the world, get a WAF.

edit: don't get mad about the analogy, it's apt.

when you open your local network to public access without protection, you're bound to have a couple "accidents" and "infections".

protect your local network with at least a proper firewall and segmented network.

a properly configured WAF is better than any reverse proxy you could use.

[–] frongt@lemmy.zip -2 points 1 month ago

See if there are any apps that will handle the VPN tunneling transparently, then provide the web interface, all in one.

If you can't find any that work like you want, I would put an authenticating reverse proxy in front of jellyfin. But last time I tried that, it only half worked. I don't know if that's changed.

Worst case, a reverse proxy that only exposes the necessary endpoints. Or a WAF that can block known attacks.

In any case, you should have a firewall rule as narrow as possible to only limit access to them. Static IP address if possible, then subnet, then ASN. Whatever is the most restrictive but still works.

[–] KarnaSubarna@lemmy.ml -5 points 1 month ago (2 children)
load more comments (2 replies)
load more comments
view more: ‹ prev next ›