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

60712 readers

358 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!

[email protected]

Torrenting/P2P:

Gaming:

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 2 years ago

MODERATORS

[email protected]

Hello pirates, I am looking to start sailing the seas again but it's been a while looking for hardware requirements? (discuss.tchncs.de)

submitted 3 months ago by [email protected] to c/[email protected]

52 comments fedilink hide all child comments

As the title states I am wondering what would be a good machine to build for my piracy. I am open to buying a used machine on eBay and expanding over time.

The last time I was sailing I had a Dell R610 Server Rack but I don’t have the space for this now. So something that can sit behind a tv stand in the corner next to the router.

I would be running Plex / Jellyfin
Some kind of torrent software
Something for NZBs if still viable
then the usual SONARR, RADARR, etc

I would like to be able to let friends connect from outside my house to stream media and allow them access so they can add films and the server goes off and finds them, extracts them, and adds them to the media server.

Thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 53 points 3 months ago (28 children)

I want to give you some advice: Use Jellyfin, not plex. It has far deviated to a "hub" for other streaming services and unless you want to have built-in streaming platforms on your home media server, or have plex's own "live tv" service shoved up your rear, I would steer clear.

Jellyfin is pretty lightweight if you're just streaming 1-2 connections at a time, I ran it on a raspberry pi 4 for a while and it was near flawless, only recently have I made a proper VM setup for it.

[–] [email protected] 8 points 3 months ago (20 children)

The only problem is properly exposing jellyfin to the Internet. How do you do it?

I'm not planning on leaving Plex anytime soon. But I did plan on setting up jellyfin in parallel to play with it and learn about it. But this stopped me in my tracks.

I don't want my family to need to VPN into my network. Plex, for as frustrating as it is in many ways, just works. And it works on so much stuff.

[–] [email protected] 12 points 3 months ago (1 children)

Jellyfin offers HTTPS, you just need to specify a certificate. It's going to be a lot easier to just setup a web server like nginx and expose that to the internet, probably via port forwarding on your gateway/router. In that case, you can get a free certificate from letsencrypt.

So, the basic steps are:

Get a domain name
Setup JF server, ensure it works locally
Install a web server and set it up to proxy traffic to JF
Expose the web server ports 80 and 443 to the internet
Setup letsencrypt with automatic renewal

This might sound like a lot of work, but at least you own your data and service. Plex can and will block accounts, rendering servers basically useless.

[–] [email protected] 1 points 4 days ago

Thanks, you and others in this thread are the first people to ever tell me about this.

Everyone is always saying tailscale, but that's too complicated and restrictive for my family.

I'm not afraid of port forwarding and dynamic DNS, I've played with it before. My main concern is just doing it safely, not exposing something to the Internet that wasn't designed to be exposed. Security risk, and all that.

Obviously a VPN is the safest way. But as long as JF is reasonably robust and designed to be exposed, I'm happy with that. I just literally didn't know it was designed that way.

Thanks!

load more comments (18 replies)

load more comments (25 replies)