Risks of using selfhosted wireguard vpn (hetzner) for p2p

jollyroger@lemmy.dbzer0.com to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 25 points –

Hi, In short: will I run the risk of receiving an angry Hetzner e-mail telling me to stop downloading torrents when I configer my local deluge client to connect through a local gluetun VPN client to a selfhosted wireguard vpn on a hetzner server? I have limited knowledge of VPNs but as far as I understand it the connection provided through gluetun from client to server (vpn) is safe, encrypted, private (somewhat) But connections from the (vpn) server to the public tracker is not, right? Or does the vpn tunnel extend to the destination? Context: I am running a deluge torrent client to download and seed torrents coming from radarr and sonarr its all running containerized through docker on my local machine. The Deluge client is using a VPN connection (via Windscribe) through a gluetun vpn client. `https://github.com/qdm12/gluetun.
I am not very happy with the speeds of Windscribe and I have small Hetzner server running with a wireguard vpn container I got working, that I hope should provide a faster download/upload speed.

Hetzner is pretty strict when it comes to downloading torrents from public trackers. A couple of years ago I basically had my plex server and a deluge client running on one of their servers. At first I used only private trackers but some content was not available so I added some torrents from public trackers. A couple of days after I got an angry e-mail from viacom through hetzner telling to quit it.

Does anyone self host their VPN and on what? And do you use it for downloading?

21

You are viewing a single comment

Mullvad will not work anymore for torrenting. They disabled port forwarding

Mullvad still works perfectly well for torrents, I'm downloading and seeding torrents now as of typing this.

It just won't work well for certain types of torrents and certain private trackers and things like that.

It does suck they took away that feature but I understand why they did it.

It can and will work, but it will not be optimal. You will be able to connect to other peers, but other peers will not be able to connect to you. This usually isn't a big deal, but it's not great in situations where there are not many peers, and you need every connection you can get.

If I remember correctly they will keep already set up ones but take away for new configs