alpine-qbittorrent-openvpn
DISCONTINUED
docker-transmission-openvpn
Our great sponsors
alpine-qbittorrent-openvpn | docker-transmission-openvpn | |
---|---|---|
12 | 189 | |
230 | 3,929 | |
- | - | |
4.2 | 7.3 | |
over 1 year ago | 17 days ago | |
Shell | Shell | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
alpine-qbittorrent-openvpn
-
Whats everyone using for you torrent/vpn combos? I've using transmission+vpn and its slow
Wow, was about to suggest what I've been using for years only to notice it's been deprecated since November of last year hah: https://github.com/guillaumedsde/alpine-qbittorrent-openvpn
- Torrenting and vpn on Synology NAS instead of local pc?
-
You probably don't need a VPN, here is why.
This was the docker container I used; there's a guide on there but it assumes you're familiar with docker.
-
Using ProtonVPN thru Qvpn Service
There are Docker images for this exact purpose: https://github.com/guillaumedsde/alpine-qbittorrent-openvpn/
- Torrenting client using ProtonVPN through Portainer on a Pi
-
Torrent IP check websites show my VPN IP, but I see my history on IKnowWhatYouDownload. What should I do?
I use guillaumedsde/alpine-qbittorrent-openvpn
-
A quick write-up of my current setup with a Raspberry Pi 4
qBittorrent : torrent downloader. The Docker image includes an OpenVPN client which is connected to my ProtonVPN account.
-
Thanks to this subreddit, I got into self-hosting over the last few months and am slowly adding more and more stuff. This is my current dashboard with all the services I run on a Raspberry Pi 4.
qBittorrent: torrent downloader. I used this container to enable the VPN
-
qBittorrent + VPN in one docker container on pi
Looks like the developer has abandoned that in favour of one based on Alpine here.
docker-transmission-openvpn
- Routing torrenting on a home server through VPN
-
Transmission (and Other) Notifications
I would try the absolute path of the script and see if that does it for you. I'm running transmission on docker using haugene/docker-transmission-openvpn and that's the absolute path within the container, but YMMV if you're running the program somewhere/somehow else.
- NordVPN with docker for torrenting | Transmission and QbitTorrent | Gluetun
-
I'm an idiot and need some experienced eyes to debug VPN and Gluetun crashing
I haven’t used GlueTUN so can’t help unfortunately but I do use this one - https://github.com/haugene/docker-transmission-openvpn and it seems easier and safer (the container stops if the VPN is down)
-
Transmission 4.0.0 has been released with over a years worth of new features and fixes!
Both of the main docker images I know of are managed by 3rd parties so they don't get updated instantly. Looks like haugene/transmission-openvpn added 4.0.0 to their beta branch a few hours ago
- Best Torrent Client
-
Advice on using VPNs with containers
Some vpns are built into docker containers, such as https://github.com/haugene/docker-transmission-openvpn
-
I've just just joined the Linux (Unbuntu 2204)and NAS ranks and have questions
Look into docker containers that have kill switches like this one
-
My first homelab in over a decade. 15yr and 12yr kids will be doing it with me this time. Any suggestion on what we should start with to run? We will have a K8s cluster.
It starts with use a vpn to download, the service is less than $2 per month. And if you want to get fancy, this git is sweet https://github.com/haugene/docker-transmission-openvpn
-
More than a decade of doing this and I finally get a letter...
If you don't have a local server in your home you can leave connected to VPN 24/7 I'd recommend doing it all through a docker container on your computer. That'll let you keep it on VPN without needing to put everything else on VPN. You could even set up two docker containers. One for the VPN and one for the torrent client, then when you turn on VPN for your regular stuff on the machine you can tunnel through that VPN without needing two take up two device slots. Here's just one option for it. But there are tons of options pre built. https://github.com/haugene/docker-transmission-openvpn Alternatively you could always set up your own if you have the know how.
What are some alternatives?
nordvpn - NordVpn Docker Client
synology-wireguard - WireGuard support for some Synology NAS drives
docker-qBittorrentvpn - Docker container which runs a headless qBittorrent client with WebUI and optional OpenVPN
gluetun - VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
docker-qbittorrentvpn - Docker container which runs a qBittorent-nox client with an optional WireGuard or OpenVPN connection
flood - A modern web UI for various torrent clients with a Node.js backend and React frontend.
arch-delugevpn - Docker build script for Arch Linux base with Deluge, Privoxy and OpenVPN
arch-qbittorrentvpn - Docker build script for Arch Linux base with qBittorrent, Privoxy and OpenVPN
FlareSolverr - Proxy server to bypass Cloudflare protection
uptime-kuma - A fancy self-hosted monitoring tool
deluge - Deluge BitTorrent client - Git mirror, PRs only
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface