qbittorrent-natmap
The objective of this container is to run a script that requests a port forward (via NAT-PMP) from the VPN provider and upon success changes the listening port of the qBittorrent client when running in Docker (by soxfor)
gluetun-wiki
Home to the Markdown Wiki page for Gluetun (by qdm12)
qbittorrent-natmap | gluetun-wiki | |
---|---|---|
10 | 8 | |
122 | 234 | |
- | - | |
5.3 | 7.4 | |
9 months ago | 12 days ago | |
Shell | ||
- | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
qbittorrent-natmap
Posts with mentions or reviews of qbittorrent-natmap.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-09.
-
Docker torrenting stack , issues with folders
# https://github.com/soxfor/qbittorrent-natmap
-
Torrenting raspberry struggling with folders
qbittorrent-natmap: # https://github.com/soxfor/qbittorrent-natmap image: ghcr.io/soxfor/qbittorrent-natmap:latest container_name: qbittorrent-natmap restart: unless-stopped volumes: - /var/run/docker.sock:/var/run/docker.sock:ro environment: - TZ=Etc/UTC - QBITTORRENT_SERVER=127.0.0.1 # - QBITTORRENT_PORT=8080 # - QBITTORRENT_USER=admin # - QBITTORRENT_PASS=adminadmin # - VPN_GATEWAY= - VPN_CT_NAME=gluetun - VPN_IF_NAME=tun # - CHECK_INTERVAL=300 # - NAT_LEASE_LIFETIME=300 network_mode: "service:gluetun" depends_on: qbittorrent: condition: service_started gluetun: condition: service_healthy
-
Port forwarding is hard!
These ports change after every reboot and can only be manually inserted into my qBittorrent. Luckily someone wrote some code that automatically updates containerized versions of qBittorrent.
-
qBittorent connectivity with Gluetun and ExpressVPN running through Docker
Using qBittorent-NatMap - would help with ExpressVPN (probably not)?
-
Recent terrible streaming services price and shows being butchered left and right pushed me to start building my own self-hosted media server. Using Plex as its easiest to setup sharing with families and friends with the *arr suite running via docker with [Ezarr](https://github.com/Luctia/ezarr)
qBittorrent-NatMap - Automatically configures your qBittorrent container for proper port forwarding (big performance improvements)
-
Is ProtonVPN committed to offering port forwarding?
It's a bit complex but I use a setup of three docker containers which all share the same networking. I use Gluetun (https://github.com/qdm12/gluetun) as the VPN client and qbittorrent as the torrent client (I use the linuxserver io image but any should qbittorrent client should work). For the port forwarding I use https://github.com/soxfor/qbittorrent-natmap which uses nat-pmp to request a port from ProtonVPN via the Gluetun interface and then automatically updates it in qbittorrent. Gluetun apparently supports Proton port forwarding by default and exposes the port via its API if you want to write your own script, but I couldn't get it to work and it uses openvpn. This setup uses a wireguard config on gluetun from Proton with nat-pmp enabled. I run this on a random weak decade old computer 24/7 but in a desktop environment you should be able to just run it on Docker desktop when you want to torrent. The docker compose file in the natmap repo gives a good idea of this docker stack.
-
ProtonVPN running on router/Transmission running on NAS. Looking for way to activate port forwarding
I feel like the solution could involve https://github.com/soxfor/qbittorrent-natmap/pkgs/container/qbittorrent-natmap somehow, but the fact that I run the VPN connection on the router (rather than the NAS) means that I have no clue how to set it upt.
-
Reasonable alternatives to Mullvad?
I just switched over myself and only did a quick test with natpmpc. While that works, on its own it isn't terribly practical. My long term goal is to get it working in a docker container which has proven more challenging. That said others seem to have been successful with this and I'm trying to adapt this: https://github.com/soxfor/qbittorrent-natmap
-
Has Anyone Had Any Luck Setting Up ProtonVPN (with port forwarding) on Asustor NAS?
If your NAS supports Docker, you could use a combination of vpn container (gluetun), natpmp container (for port forwarding) and a qbittorrent container. I have it working on a raspberrypi
-
Port forward with qBittorrent and ProtonVPN (on Docker with VPN via Gluetun)
Since I couldn't find exact instructions for qBittorrent I decided to start something, that can be found here (github)
gluetun-wiki
Posts with mentions or reviews of gluetun-wiki.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-09.
-
Torrenting raspberry struggling with folders
services: gluetun: containername: gluetun image: qmcgaw/gluetun # line above must be uncommented to allow external containers to connect. # See https://github.com/qdm12/gluetun-wiki/blob/main/setup/connect-a-container-to-gluetun.md#external-container-to-gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 8888:8888/tcp # HTTP proxy - 8388:8388/tcp # Shadowsocks - 8388:8388/udp # Shadowsocks - 8080:8080 #qbittorrent - 6881:6881 #qbittorrent - 6881:6881/udp #qbittorrent - 8989:8989 # port for sonarr - 7878:7878 # port for radarr - 9696:9696 # port for prowlarr - 9117:9117 # port for bazarr volumes: - /home/osmc/Docker:/gluetun - /home/osmc/Docker/tmp:/tmp/gluetun environment: # See https://github.com/qdm12/gluetun-wiki/tree/main/setup#setup - VPN_SERVICE_PROVIDER=protonVPN - VPN_TYPE=openvpn # OpenVPN: - OPENVPN_USER=___ - OPENVPNPASSWORD=__ - VPN_PORT_FORWARDING=on # Wireguard: # - WIREGUARD_PRIVATE_KEY=wOEI9rqqbDwnN8/Bpp22sVz48T71vJ4fYmFWujulwUU= # - WIREGUARD_ADDRESSES=10.64.222.21/32 # Timezone for accurate log times - TZ=Netherland # - SERVER_COUNTRIES=Netherland - SERVER_HOSTNAMES=node-nl-13.protonvpn.net,node-nl-01.protonvpn.net - UPDATER_PERIOD=24h - FIREWALL_OUTBOUND_SUBNETS=172.20.0.0/24 restart: unless-stopped
-
Help with Deluge and Gluetun in Docker
gluetun: image: qmcgaw/gluetun container_name: gluetun # line above must be uncommented to allow external containers to connect. # See https://github.com/qdm12/gluetun-wiki/blob/main/setup/connect-a-container-to-gluetun.md#external-container-to-gluetun hostname: gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 8112:8112 - 6881:6881 # inbound torrent - 6881:6881/udp volumes: - ./gluetun:/gluetun env_file: - ./vpn_credentials.env environment: # See https://github.com/qdm12/gluetun-wiki/tree/main/setup#setup - VPN_SERVICE_PROVIDER=protonvpn - VPN_TYPE=openvpn - VPN_PORT_FORWARDING=on - SERVER_HOSTNAMES=node-us-144.protonvpn.net,node-us-126.protonvpn.net # Server list updater # See https://github.com/qdm12/gluetun-wiki/blob/main/setup/servers.md#update-the-vpn-servers-list - UPDATER_PERIOD=24h dns: - 8.8.8.8 - 8.8.4.4 networks: - internal deluge: image: lscr.io/linuxserver/deluge:latest container_name: deluge volumes: - ./config/deluge:/config - /hdd/media/torrents:/media/torrents # ports: # - 8112:8112 # webui # - 6881:6881 # inbound torrent # - 6881:6881/udp restart: unless-stopped network_mode: "service:gluetun"
- Help with setting up gluetun
-
Route docker container via Gluetun + AirVPN
I've got a couple of Docker containers running: 'binhex-plexpass' and 'GluetunVPN'. I've subscribed to AirVPN, and I'm trying to configure 'GluetunVPN' for AirVPN (Wireguard). I think I've succeeded with this. However, I'm a bit stuck on connecting 'GluetunVPN' to 'binhex-plexpass' based on this guide: https://github.com/qdm12/gluetun-wiki/blob/main/setup/connect-a-container-to-gluetun.md
-
NordVPN - AUTH_FAILED Your credentials might be wrong
2023-07-12T11:28:22+01:00 INFO [healthcheck] program has been unhealthy for 2m41s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
- Tun0 not showing up as an interface option in settings
-
Routing torrenting on a home server through VPN
qbittorrent can use proxies if I remember correctly, so you just need to enable privoxy in the gluetun service, and add the ip of the machine plus the choosen port for the proxy to qbittorrent settings from the web interface.
-
Transmission (& other Apps) - is OpenVPN no longer usable? TrueNAS-SCALE-22.12.3.1
Choose your provider if not found, check out custom, wiki here.
What are some alternatives?
When comparing qbittorrent-natmap and gluetun-wiki you can also consider the following projects:
hide.client.linux - Hide.me CLI VPN client for Linux
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.
Saltbox - Ansible-based solution for rapidly deploying a Docker containerized cloud media server.
py-natpmp - a NAT-PMP library for Python
Guides - Here you will find Guides mainly for the Starr Apps (Sonarr/Radarr) and everything related to it.