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 must log in or register to comment.
That’s more secure than most setups, the VPN with killswitch will defeat any and all attacks you’re likely to encounter if you don’t open files on that same VM.
Awesome, ty!
I can’t speak to the paid ProtonVPN service, but their free tier doesn’t allow torrenting. They’ll disconnect you with a slap on the wrist error about it.
Seems fair TBH, you’re easily sending TBs of data through it, that’s not the intention of the free tier.
Yeah I found that out the hard way lol. Was just a soft warning. Premium tier allows P2P traffic and actually provides torrent-optimized servers too.
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
I’m trying to recreate this setup in my system. I’m running Ubuntu and I have everything in Docker. I have PIA running outside of Docker. I was also able to get Gluetun working in its own container, too. Does anyone have advice?
That’s very similar to what I run and I’ve never had any problems.
What about file encryption? How do you store your new files?
FDE is for physical attackers, it would have nothing to do with torrenting unless you’re really intending on pissing off every single criminal legal authority and not just worried about civil suits from copyright holders.
Full disk encryption? Or should I do something additional?
file or disk encryption is only for protecting against attackers with physical access to the machine your VM is running on. Getting files from your server to local storage you should still use a secure connection and encrypted traffic to prevent ISP snooping, but going extreme on file encryption isn’t necessary unless you’re downloading actual heinous shit (CSAM) in which case you should go to jail.
Why would you need file encryption?
Not like having a drive full of movies is illegal…Except if OP has CSAM stuff inside. Than it should be very encrypted in case of loosing (or not depending if OP wants jail time).Except if OP has CSAM stuff inside. Than it should be very encrypted
then OP SHOULD go to jail.
Not like I don’t agree. Those vile people should.
But something like that or actually confidential stuff you don’t want others to see is a valid reason to encrypt it.That escalated quickly
Holy shit yeah lol. Obviously nothing like that! I was confused as well why anything other than the generic Linux full disk encryption would be needed.
This would be in a server closet, so not on drives that I would be transporting copyrighted media into other countries anyways.
