Trying to utilize an old laptop as a torrenting/media server, but I’d like to remote in from my phone to control it when needed.
My concern is, if the laptop is running VPN with kill switch and the qBitTorrent is bound to ProtonVPN, would me remoting in expose the laptop’s IP or DNS? Or would it expose that I’m doing P2P torrents to my ISP? Or any other concerns i should be aware of?
In general, no. As long as you don’t do some type of split tunneling, teamviewer well go over the VPN also. I don’t remember if teamviewer works behind a VPN/NAT or not without forwarding ports.
A much better solution than teamviewer would either be to setup a Wireguard VPN server in your network or something like Tailscale if you can’t port forward on your router. Then just RDP or VNC into your torrent box. Ideally, run the VPN or Tailscale on a different box than the torrent client.
This question can only be answered with trial and error. But I’m gonna recommend port forwarding the web ui on your router and using that instead of remote desktop
No split tunneling, port forwarding is on via ProtonVPN and I match the port number in BitTorrent, and the kill switch is set to permanent.
By chance are there any guides that explain the how’s and why’s of how to set up a wireguard vpn server? I’m brand new to vpns and torrenting and thought that was more or less what I was already doing with this laptop
This is bad advice. There are much more secure ways of getting to your torrent client remotely than exposing it’s web interface to the Internet.
Thank you! I hadn’t considered this as an option
The local Wireguard VPN server would be so you can get into your local network remotely, as opposed to running teamviewer. Checkout PiVPN package. Super simple to setup a Wireguard VPN server with that. Works in any Linux distro, not just Raspberry Pi. You could run it on the same box as your torrent client. Just forward the port via your Proton VPN.
Different topic. Make sure you have bound your torrent client to the Proton VPN interface.
True but not as convenient, I trust the login page to not have a vulnerability. I haven’t even had crawlers find the subdomain on my site in the last year it’s been running (checking nginx logs)
Many thanks for this explanation, I think I understand now!