this post was submitted on 27 Nov 2025
205 points (99.5% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
65359 readers
494 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
🏴☠️ Other communities
FUCK ADOBE!
Torrenting/P2P:
- !seedboxes@lemmy.dbzer0.com
- !trackers@lemmy.dbzer0.com
- !qbittorrent@lemmy.dbzer0.com
- !libretorrent@lemmy.dbzer0.com
- !soulseek@lemmy.dbzer0.com
Gaming:
- !steamdeckpirates@lemmy.dbzer0.com
- !newyuzupiracy@lemmy.dbzer0.com
- !switchpirates@lemmy.dbzer0.com
- !3dspiracy@lemmy.dbzer0.com
- !retropirates@lemmy.dbzer0.com
💰 Please help cover server costs.
![]() |
![]() |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments



It does not say that in the documentation. What the documentation does have, however, are extensive instructions on how to make Jellyfin accessible on WAN: https://jellyfin.org/docs/general/post-install/networking/ https://jellyfin.org/docs/general/post-install/networking/reverse-proxy/
It says so right there.
And there.
This smug mentality that security is unnecessary when exposing ports to the open internet reminds me of people who think its fine to drive drunk because "I've done it dozens of times before and nothing happened!" It also reminds me of the mentality of tech company VPs right before they have a massive data breach. It's quite absurd to read.
For some reason they recommend against directly forwarding Jellyfin's ports, but reverse proxies are fine. I expect this is because the default configuration doesn't use SSL.
I think you'll find without exposing ports to the open internet we would not be having this conversation right now. Which, I suppose, wouldn't be such a bad thing.
I've not looked into it but presumably it's because whatever web server framework they are using might not be as bug free and battle tested as dedicated web server application like nginx so by limiting the actual web servers exposure you are limiting the attack surface.
This is good to know, thanks for sharing. I've only got it local for now after installing at the weekend and wasn't sure how secure it was for external access.
I'm just chiming in to say that while the documentation gives you information on how to do external access, there are multiple issues open on the github about unauthenticated endpoints that if you know what is on the server already, you can confirm that it's there
So I wouldn't use a standard naming convention because using that knowledge, someone who cares could use common names that could be on the server, followed by common standards of formats they would be in, and be able to confirm it's their via the end points.