this post was submitted on 08 Dec 2025
81 points (98.8% liked)

Selfhosted

53588 readers
480 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 2 years ago
MODERATORS
 

when reading through the jellyfin with chromecast guide i realized that it would probably be less effort to just let the casting api be public, with the added bonus that i could then cast my library to any device that supports it. but that seems like it would paint a giant target on the server.

what's the recommended way of doing stuff like this? ideally i want to be able to go to someone's house and just play some of my media on their tv.

not that any of this is doable in the near future, since i'm behind cgnat and won't get my colocated bounce server up until spring.

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

Can you elaborate on 'properly configured'?

[–] dogs0n@sh.itjust.works 4 points 2 days ago* (last edited 2 days ago) (13 children)

The default configuration for Jellyfin is good. I mostly mean as long as you follow best practices in general you should be fine, eg:

  • You keep your system and jellyfin updated;
  • have some type of firewall in place;
  • make sure you aren't accidentally exposing jellyfins port directly to the internet;
  • have a good password for your jellyfin accounts that are able to login from outside the LAN;
  • and so on and so forth

https://jellyfin.org/docs/general/post-install/networking/reverse-proxy/

A firewall is probably the most important, having your ssh port blocked in the firewall being second.

[–] mic_check_one_two@lemmy.dbzer0.com 7 points 2 days ago (3 children)

Also, don’t use the default “data/media/{library name}” (or whatever the suggested format is) folder setup that the Trash Guide has you set up. At least change the “tv”, “movies”, etc name to something different. Jellyfin has a known vulnerability where an attacker can get access to media without valid credentials if they already know the file path. Jellyfin devs have stated that they have no intention of ever fixing this, because it would require completely divesting from the Kodi branch that everything is built on. And since everyone follows the Trash Guide to set their *Arr stack and library up, guessing file paths is laughably easy.

You’re using the suggested file naming in your *Arr stack, so Jellyfin can automatically match media? Congrats, so is everyone else. You’re using the suggested folder layout so your *Arr stack can use hardlinks? Congrats, so is everyone else. At least change the library folder names. Since your library folder doesn’t need to match the name of your Jellyfin library, you can literally have your “tv”, “movies”, and other folders be named whatever you want. Hell, name your tv folder “peepee” and your movies folder “poopoo” for all I care.

[–] Wolf314159@startrek.website 1 points 2 days ago

This needs to be copypasta'd as a reply to every comment suggesting that opening up jellyfin to the internet is easy and everyone should do it to get away from Plex.

load more comments (2 replies)
load more comments (11 replies)
load more comments (11 replies)