this post was submitted on 26 Sep 2025
698 points (96.0% liked)

Selfhosted

51838 readers
604 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
 

Well I already have jellyfin running in a container, just have to figure out how to get mum's TV to work with it I guess

log in on a local IP and not the network name and it's working again. but I'll be moving to jellyfin from now

you are viewing a single comment's thread
view the rest of the comments
[–] TeddE@lemmy.world 8 points 3 days ago (4 children)

Setting up ddns takes 15 minutes for a professional (mostly setting a 1-line script to reload a simple url every ten minutes)

and poking a hole in the firewall takes maybe half an hour (since every router puts the relevant page in a different spot)

And for this you think it's reasonable to pay ~$25/year for the rest of your life? You're not wrong in the sense that you're welcome to choose your own values, but I … disagree with you on the value position.

[–] vithigar@lemmy.ca 9 points 3 days ago (1 children)

I would be ashamed of myself and be tempted to leave the industry in disgrace if setting up DDNS and allowing a single port through a firewall took me 45 minutes.

[–] TeddE@lemmy.world 5 points 3 days ago

Shhhhhhhhhhhhh. I want the newbs to feel accomplished when it only takes them 2 hours to figure it out. 😉

But seriously, you and I have it on reflex, but there's merit to the notion that we also have our mise en place - we've read the manual, we've saved or memorized the script, already know our local equipment passwords, etc - all things we took the time to do before and now have at the ready.

I mean, you just listed the most insecure way to host Jellyfin. Poking a hole in your firewall will technically work, but that doesn’t mean it’s the correct way to do things. A good setup would use a reverse proxy, and some sort of authentication wall like Authentik or Authelia.

All of that would only take about 15 minutes for someone who knows what they’re doing. But the vast majority of people setting up Jellyfin for the first time won’t know what they’re doing. And seeing the inevitable “lol just open your firewall” comments only serves to scare them away, because even the noobs have heads that’s the wrong way to do things.

[–] onslaught545@lemmy.zip 1 points 2 days ago (1 children)

I'd be fine paying $25 a year to not maintain that shit myself. Plus the money should contribute to development efforts.

[–] TeddE@lemmy.world 2 points 2 days ago (1 children)

It should. I agree, but speaking as someone in the industry - usually it doesn't. Just lines some rich guy's pockets.

[–] onslaught545@lemmy.zip 1 points 2 days ago (1 children)

Fair in the instance of Plex, but I'm happy to pay for the feature with Home Assistant.

[–] TeddE@lemmy.world 1 points 2 days ago

Good call! 100% (at least for now 😅)