this post was submitted on 11 Nov 2023
554 points (92.4% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54772 readers
602 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):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Selmafudd@lemmy.world 11 points 1 year ago (2 children)

It's easy af, just look up Jellyfin server guide. Basically it's just forwarding a few ports and setting up usernames/passwords for them and you're good to go

[–] wolfshadowheart@kbin.social 11 points 1 year ago (3 children)

It gets more complicated if someone is double-natted (CG/NAT) unfortunately.

[–] MigratingtoLemmy@lemmy.world 11 points 1 year ago

A slightly more complicated setup would be to host Jellyfin on one's server at home and run a VPN client to a VPS which would have the necessary ports forwarded and routing configured. This way the people who know the right credentials can log in (assuming SSO) and the hoster doesn't have to open their own port

[–] PupBiru@kbin.social 6 points 1 year ago

add tailscale and you’re golden

[–] clericc@feddit.de 1 points 1 year ago

one could dyndns their servers' ipv6 instead, where cgnat to my knowledge does not exist

[–] CmdrShepard@lemmy.one 5 points 1 year ago

This is the riskiest way of doing it because you're exposing ports to the open internet.