this post was submitted on 08 Jun 2026
477 points (96.1% liked)

Selfhosted

59864 readers
965 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.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

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

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] klankin@piefed.ca 3 points 6 days ago* (last edited 6 days ago) (1 children)

No reason to connect jellyfin to any sort of local network, router will still hairpin for local connection.

With that setup its honestly more secure than 99% of IOT devices, and like 50% of routers.

edit: and if youre running it in the pentagon or something just toss authentication like keycloak in front of it, plus a bit of crowdsec/fail2ban and an IP whitelist, I'd be surprised if you'd even get an attack, much less one violating that strict of a threat models.

[–] kalpol@lemmy.ca 3 points 5 days ago (1 children)

Good grief. If you're doing all that, just set up Wireguard

[–] klankin@piefed.ca 1 points 5 days ago

I mean containers make the networking pretty easy, everything beyond that is optional based on your threat model.

Same as hosting anything networked, you can do it easy or do it safe.

(but also wireguard is kinda an O(n) problem while exposing to wan is an O(1) problem - at least IT man hours wise)