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