this post was submitted on 23 May 2026
187 points (97.0% liked)

Selfhosted

56957 readers
1426 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

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?

you are viewing a single comment's thread
view the rest of the comments
[–] GreenKnight23@lemmy.world -2 points 1 day ago* (last edited 1 day 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.