nordvpn
docker-qbittorrent
Our great sponsors
nordvpn | docker-qbittorrent | |
---|---|---|
50 | 11 | |
695 | 840 | |
- | 8.3% | |
3.5 | 8.5 | |
22 days ago | 10 days ago | |
Shell | Dockerfile | |
GNU Affero General Public License v3.0 | 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.
nordvpn
- [Self Hosted] VPN Mullvad pour les conteneurs Docker
- [Nord Vpn] Après la mise à jour: /run/nordvpn/nordvpnd.sock introuvable
-
Nordlynx, qbittorrent, sonarr, radarr, jellyfin, and jellyseer
version: "3.8" services: nordlynx: image: ghcr.io/bubuntux/nordlynx cap_add: - NET_ADMIN # Required environment: # Review https://github.com/bubuntux/nordvpn#environment-variables - PRIVATE_KEY=mykey # Required - CONNECT=United_States - NET_LOCAL=10.20.30.40/24 # So it can be accessed within the local network - ALLOWED_IPS=10.20.30.40/24 ports: - "6881:6881" #qbittorent - "6881:6881/udp" #qbittorrent - "8080:8080" #qbittorrent - "7878:7878" #radarr - "8989:8989" #sonarr - "9696:9696" #prowlarr - "8097:8096" #jellyfin - "5055:5055" #jellyseer sysctls: - net.ipv6.conf.all.disable_ipv6=1 # Recomended if using ipv4 only qbittorrent: image: linuxserver/qbittorrent container_name: qbittorrent network_mode: service:nordlynx environment: volumes: - /path/to/qbittorrent/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped radarr: image: linuxserver/radarr container_name: radarr network_mode: service:nordlynx environment: volumes: - /path/to/radarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped sonarr: image: linuxserver/sonarr container_name: sonarr network_mode: service:nordlynx environment: volumes: - /path/to/sonarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped prowlarr: image: linuxserver/prowlarr container_name: prowlarr network_mode: service:nordlynx environment: volumes: - /path/to/prowlarr/config:/config depends_on: - nordlynx restart: unless-stopped jellyfin: image: linuxserver/jellyfin container_name: jellyfin network_mode: service:nordlynx environment: - JELLYFIN_PublishedServerUrl=http://10.20.30.184:8097/ volumes: - /path/to/jellyfin/config:/config - /path/to/jellyfin/cache:/cache - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped jellyseer: image: fallenbagel/jellyseerr:latest container_name: jellyseer network_mode: service:nordlynx environment: volumes: - /path/to/jellyseer/config:/app/config depends_on: - nordlynx restart: unless-stopped
-
KASM with VPN?
All the infos you need are on the github page > https://github.com/bubuntux/nordvpn
-
NordLynx with docker for torrenting | Transmission and QbitTorrent
Issues · bubuntux/nordvpn (github.com)
-
Docker Image - Invalid Username or Password Bug
On https://github.com/bubuntux/nordvpn it mentions that token login is also supported (Nord v3.15.0+). I've used the token login and it works well for me.
- NordVPN bittorrent contaner inside openmediavault
-
Extremely Slow Torrenting Speed
There has been an issue reported on github: https://github.com/bubuntux/nordvpn/issues/367
-
Meshnet on opnsense router
Two of the popular containers are https://github.com/qdm12/gluetun and https://github.com/bubuntux/nordvpn but it's not clear if either of them can use meshnet.
-
VPN gateway on home server VM
A ubuntu/debian vm with nordvpn official client, use iptables to forward this connection to the vm IP. I've seen a similar approach using docker here https://github.com/bubuntux/nordvpn but this only shares connection to other dockers ct's in the same setup
docker-qbittorrent
-
We're no longer sunsetting the Free Team plan | Docker
Say I wanted to run this container on k3s. How do I specify PUID, PGID, WEBUI_PORT, and the volumes? This is literally the only thing keeping me from jumping headfirst into k3s. I have no intention of running anything docker in the near future and onwards, but I need to know how I can switch without using something like kompose (I don't want to trust a script with my deployment options, I want to do it by hand like I used to with Docker).
-
Memory leak with linuxserver/qbittorrent Docker container?
Here is a link to an issue I found on the linuxserver/docker-qbittorrent repo discussing the issue I'm currently having.
-
Issue with docker, radarr, and qbittorrent: this directory does not appear to exist.
# https://github.com/linuxserver/docker-qbittorrent qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent network_mode: service:nordvpn environment: - PUID=13002 - PGID=13000 - TZ=${TIMEZONE} - UMASK=002 volumes: - ${ROOT_DIR}/docker/qbittorrent-config:/config - ${ROOT_DIR}/data/torrents:/data/torrents restart: unless-stopped depends_on: - vpn
-
What's the difference in using or not using `network_mode: host`? (example below)
In "docker ps" you'll see the EXPOSE Ports defined in the Dockerfile of your Image. They are only accessable in their own networks unless you just bridge your container to your host's network (not recommended).
-
Where can I find help with Gluetun and Qbittorrent?
My only issue is the the linuxserver/qbittorrent container doesn't always start up after a server reboot, I've just filed a github issue about this: https://github.com/linuxserver/docker-qbittorrent/issues/167
- qBittorrent errors
-
qbittorrent default password?
Check out the GitHub... Nine times out of ten the info is there: https://github.com/linuxserver/docker-qbittorrent
-
Self-hosting all these services on two Raspberry Pi 4s!
qBittorrent
- Problem with torrenting
-
PSA: use older linuxserver/qBittorent stack on docker to resolve WebUI login issue
Stuck on the Login page · Issue #109 · linuxserver/docker-qbittorrent (github.com)
What are some alternatives?
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
flood - A modern web UI for various torrent clients with a Node.js backend and React frontend.
docker-wireguard
synology-wireguard - WireGuard support for some Synology NAS drives
docker-surfshark - Docker container with OpenVPN client preconfigured for SurfShark
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.
openvpn-client
nordlynx
authelia - The Single Sign-On Multi-Factor portal for web apps
docker-wireguard-socks-proxy - Expose a WireGuard tunnel as a SOCKS5 proxy
Paperless-ng - A supercharged version of paperless: scan, index and archive all your physical documents