Exactly. Their VPN app on Linux does not even have WireGuard options, let alone the Stealth Protocol. No port-forwarding either. There are so mamy features on Windows that they do not provide Linux users.
I change servers very frequently. For that I have to download a lot of config files. Considering, I am paying Proton just as much a Windows user, I shouldn’t have to do all this work.
I have a seedbox built with ProtonVPN and Linux. You can’t use their app but the manual configuration does work. (Port forwarding is annoying though, i had to write a script to manage it.)
A lot of manual work. The easy version is i used qemu to create a fedora server vm. If you’re on windows, virtual box or whatever should work just as well. With that up, I configured the manual ProtonVPN wireguard connection with port forwarding according to their configuration guides. Note that you can only request a port from them for 60 seconds at a time, so a script will be needed there to keep it active. I forwarded the port I got through firewall-cmd and then tested to ensure it was open. I configured my router’s firewall to give the VM a set up but that may not really be necessary and you don’t need to do port forwarding on the router firewall with this setup.
From there, I installed a BitTorrent client. I went with transmission because it has a good cli, but if you’re not planning to automate this whole process something like deluge or qbittorrent will probably work better. I configured to to bind it’s IP to the ProtonVPN VPN IP and to upload through the port i got from ProtonVPN.
At that point, I ran a bunch of tests to confirm it was forwarding the port correctly and all the traffic went through the VPN. I could find the sites I used to confirm the thing was working as expected if you like. I also tested that it was able to upload and stuff
And that’s it. That should approximately be functional.
The big downside: If the port you’re getting from ProtonVPN changes you’ll have to manually change the VM’s firewall and the port used in your torrent client. That’s what the automation is basically doing.
Exactly. Their VPN app on Linux does not even have WireGuard options, let alone the Stealth Protocol. No port-forwarding either. There are so mamy features on Windows that they do not provide Linux users.
I just use Wireguard for ProtonVPN. Just download the wireguard config and import it into wireguard
I change servers very frequently. For that I have to download a lot of config files. Considering, I am paying Proton just as much a Windows user, I shouldn’t have to do all this work.
“Shouldn’t have to”
I mean, you don’t have to. There’s other services. Mullvad or whatever.
Having a handful of config files and switching to them isn’t the hardest thing. It works. Not like they’re preventing you from it.
I have a seedbox built with ProtonVPN and Linux. You can’t use their app but the manual configuration does work. (Port forwarding is annoying though, i had to write a script to manage it.)
Do you mind sharing how you did that? I want to have a seedbox at my house too.
A lot of manual work. The easy version is i used qemu to create a fedora server vm. If you’re on windows, virtual box or whatever should work just as well. With that up, I configured the manual ProtonVPN wireguard connection with port forwarding according to their configuration guides. Note that you can only request a port from them for 60 seconds at a time, so a script will be needed there to keep it active. I forwarded the port I got through firewall-cmd and then tested to ensure it was open. I configured my router’s firewall to give the VM a set up but that may not really be necessary and you don’t need to do port forwarding on the router firewall with this setup.
From there, I installed a BitTorrent client. I went with transmission because it has a good cli, but if you’re not planning to automate this whole process something like deluge or qbittorrent will probably work better. I configured to to bind it’s IP to the ProtonVPN VPN IP and to upload through the port i got from ProtonVPN.
At that point, I ran a bunch of tests to confirm it was forwarding the port correctly and all the traffic went through the VPN. I could find the sites I used to confirm the thing was working as expected if you like. I also tested that it was able to upload and stuff
And that’s it. That should approximately be functional.
The big downside: If the port you’re getting from ProtonVPN changes you’ll have to manually change the VM’s firewall and the port used in your torrent client. That’s what the automation is basically doing.