this post was submitted on 02 Sep 2023
41 points (97.7% liked)

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

54083 readers
295 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

💰 Please help cover server costs.

Ko-FiLiberapay

founded 1 year ago
MODERATORS
db0@lemmy.dbzer0.com
sunbrothersco@lemmy.dbzer0.com
dataprolet@lemmy.dbzer0.com
Flatworm7591@lemmy.dbzer0.com
RandomLegend@lemmy.dbzer0.com
41
Sanity Check Setup (lemmy.ml)
submitted 1 year ago by Lettuceeatlettuce@lemmy.ml to c/piracy@lemmy.dbzer0.com
19 comments fedilink hide all child comments
 

Just making sure I'm not missing something obvious:

Self-hosted Linux VM with protonVPN and QBitorrent installed on it.

QBittorrent networking bound only to ProtonVPN's virtual interface with killswitch and secure core enabled.

Auto updates enabled and a scripted alert system if ProtonVPN dies. Obviously everything with very secure unique passwords.

Is this a safe setup to run 24/7 to torrent and seed with?

Are there any significant risks I'm missing? Thanks, fellow sea salts!

you are viewing a single comment's thread
view the rest of the comments
[–] skankhunt42@lemmy.ca 2 points 1 year ago

What kind of firewall do you have? (Not on the VM, though something similar might work there also)

I use OPNSense and have an allow rule for the specific IP and port my VPN uses from that VM's IP. Then a block everything from the VM IP after the allow.

I can connect to the VPN no problem, updates and everything work through the VPN. When it goes down it trys to connect normally and fails.

DNS can be a problem when trying to connect to the VPN so make sure to use the IP