🏰️ qBittorrent + ProtonVPN (WireGuard) in Docker (macOS)

Securely run qBittorrent in Docker with ProtonVPN (WireGuard) using Gluetun, ensuring full VPN routing and automatic port forwarding for improved torrenting performance.

📌 Table of Contents

• Overview
• Features
• Prerequisites
• Installation Guide
• Install Docker
• Clone the Repository
• Set Up the .env File
• Configure Authentication
• Start the Containers
• Accessing qBittorrent Web UI
• Security & Best Practices
• Troubleshooting
• License
• Contributing
• Support & Feedback

🔹 Overview

This setup ensures qBittorrent only connects through ProtonVPN (WireGuard) using Gluetun, preventing leaks and enhancing security.\ It also automates port forwarding for better torrent speeds and runs everything inside Docker for easy management.

✅ Features

• 🔒 VPN-Enforced Torrenting – No leaks, all traffic runs inside the VPN.
• ⚡ Automatic Port Forwarding – Ensures better speeds and improved peer connections.
• 🌐 Local Web UI Access – Easily control torrents via http://localhost:8080.
• 📺 Fully Containerized – Uses Docker for easy deployment, updates, and isolation.
• 🔄 Resilient Setup – Containers auto-restart if anything crashes.
• Uses separate storage for incomplete and completed torrents
• Automatically updates containers using Watchtower 🛠️

🛠️ Prerequisites

• Docker Desktop (macOS/Windows/Linux)
• Docker Compose (bundled with Docker Desktop)
• ProtonVPN account (Plus or Visionary required for WireGuard support)

📂 Installation Guide

1️⃣ Install Docker

Download and install Docker Desktop from here.\ Ensure Docker is running before proceeding.

2️⃣ Clone the Repository

git clone https://github.com/torrentsec/qbittorrent-protonvpn-docker.git
cd qbittorrent-protonvpn-docker

3️⃣ Set Up the .env File

This project uses an .env file to store sensitive configuration values (which are ignored by Git for security).

#### Create Your .env File

cp .env.example .env
nano .env

#### Fill in the Following Variables

WIREGUARD_PRIVATE_KEY=your_private_key_here
SERVER_COUNTRIES="United Kingdom"
SERVER_CITIES="London"
PUID=1000
PGID=1000
TZ=Europe/London
GLUETUN_USER=your_admin_username
GLUETUN_PASS=your_admin_password
GSP_GTN_API_KEY=your_random_api_key_here
GSP_QBITTORRENT_PORT=your_forwarded_port_here

Save and close (CTRL + X, then Y, then ENTER).

4️⃣ Start the Containers

docker-compose up -d

🚀 qBittorrent is now running securely through ProtonVPN!

📚 Accessing qBittorrent Web UI

Once running, open:\ 📌 http://localhost:8080\ (Default username: admin, password: check console for temporarily password)

Make sure to change your web UI password after the first login. Otherwise, the password will be randomly generated after every container restart.

🛡️ Security & Best Practices

• Keep .env Private
• The .gitignore file already prevents .env from being uploaded to GitHub.
• Use a Strong Password for Gluetun API
• Modify GLUETUN_PASS in .env to prevent unauthorized API access.
• Verify VPN Connectivity Before Torrenting
• Run curl ifconfig.me inside the container:

     docker exec -it qbittorrent curl ifconfig.me
     ``
   
✅ If the IP matches ProtonVPN, it's working.
   
❌ If it shows your real IP, something is wrong.
---
🛠️ Troubleshooting
Check if VPN is Running

If Gluetun isn’t running, restart everything:

Verify qBittorrent is Using VPN

🟢 If the IP matches ProtonVPN, it’s working.\
🔴 If it shows your real IP, something is wrong.
Check Logs for Errors

Look for AUTH\_FAILED or connection issues.

💎 License

This project is licensed under the MIT License – see the LICENSE file for details.

💪 Contributing

Contributions are welcome! If you have improvements or feedback, feel free to submit an issue or pull request.

💬 Support & Feedback

• If you found this helpful, give it a ⭐ star on GitHub!
• Feedback & suggestions are always welcome.