Introduction

This is probably the easiest, most extensible and trouble-free way of setting up qBittorrent's WebUI with HTTPS. It combines ideas from these other articles of the wiki: 1, 2.

The benefit of this setup is that with one single domain and certificate you are able to setup secure HTTPS access to various different services in your server alongside one another. For example, you may have qBittorrent's WebUI accessible at yourdomain.com/qbt, a simple homepage served with Apache at yourdomain.com, your Nextcloud instance at yourdomain.com/nextcloud, etc.

This guide assumes you have a working qbitorrent-nox setup (check this article if you haven't). This guide also assumes that:

you know how to and can forward ports on your router, to forward ports 80 and 443.
you have setup a DNS pointing to the IP you are running the Web UI from (you can use a free one like Duck DNS).

The overall architecture of the system will be:

                                 ________________________________________________
Outside world (insecure)         |   Your machine (secure)                      |
You <-------HTTPS (secure)-------|->  NGINX <----HTTP-----> qbittorrent WebUI   |
                                 |                                              |
                                 ------------------------------------------------

Install the prerequisites

Install `certbot`

certbot is the recommended ACME client for requesting and managing Let's Encrypt certificates. It is available on the official Ubuntu repositories; it won't be the most recent version, but you don't really need the latest and greatest for this to work just fine. However, if you want to use the most recent version, you will unfortunately have to install it via the proprietary Snap store. Regrettably, the Certbot team no longer maintains their PPA. You will also need the nginx plugin.

sudo apt update
sudo apt install certbot 
sudo apt install python-certbot-nginx # this is needed for the nginx plugin

Install `nginx`

You can use the version in the repositories, but if you want the most recent version you can use the PPA.

sudo apt update && sudo apt upgrade -y # first update all packages in the system
sudo add-apt-repository ppa:nginx/stable
sudo apt install nginx

Setup

Setup the Web UI

Access your WebUI, and go to Tools -> Options -> WebUI
Change the following settings if they are not already like so:
- IP address: 127.0.0.1
- Port: some free port on your system that is NOT accessible through the outside world. In this case we will use port 30000.
- Use UPnP / NAT-PMP to forward the port from my router: unchecked.
- Use HTTPS instead of HTTP: unchecked.
- Optional: if you want to use "enable host header validation", enable that checkbox, and add 127.0.0.1 to the "server domains" text box. Don't forget to also configure the proxy_set_header directive in the nginx config below.

Set up NGINX

Forward ports 80 and 443 in your router.
Allow ports 80 and 443 through your system firewall if you have one.

If you have ufw as your system firewall, it is as simple as:
```
sudo ufw allow 80 && sudo ufw allow 443 && sudo ufw reload
```

Clear the default files

sudo rm /etc/nginx/sites-available/*
sudo rm /etc/nginx/sites-enabled/*

Stop nginx if it is running: sudo systemctl stop nginx.service

Create a config file for your reverse proxy

sudo touch /etc/nginx/sites-available/yoursite
cd /etc/nginx/sites-enabled/
sudo ln -s /etc/nginx/sites-available/yoursite yoursite

Open the file with your favourite text editor and paste something like the following reference configuration (adjust according to your needs):

# change "yourdomain.com" and similar to your actual domain
server {
    listen 80;
    listen [::]:80;
    server_name yourdomain.com www.yourdomain.com;
    return 301 https://yourdomain.com$request_uri;
}

server {
    listen 443;
    server_name yourdomain.com www.yourdomain.com;

    # at this point we haven't created the certificate yet, but that's ok.
    # if, when creating the certificate (see below) it goes to another folder, be sure
    # to change these lines accordingly
    ssl_certificate           /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_trusted_certificate   /etc/letsencrypt/live/yourdomain.com/chain.pem;
    ssl_certificate_key       /etc/letsencrypt/live/yourdomain.com/privkey.pem;

    ssl on;
    ssl_prefer_server_ciphers on;
    ssl_protocols TLSv1.3 TLSv1.2;
    ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256';
    ssl_ecdh_curve prime256v1:secp384r1:secp521r1;
    ssl_session_cache shared:TLS:50m;
    ssl_session_timeout 1d; # default is 5 min 
    ssl_session_tickets off;
    # OCSP stapling
    ssl_stapling on; 
    ssl_stapling_verify on;

    access_log            /var/log/nginx/yourdomain.access.log;

    location /qbt/ {
        proxy_pass         http://127.0.0.1:30000/;
        proxy_http_version 1.1;
        http2_push_preload on; # Enable http2 push

        proxy_set_header   Host               127.0.0.1:30000;
        proxy_set_header   X-Forwarded-Proto  $scheme;
        proxy_set_header   X-Forwarded-Host   $http_host;
        proxy_set_header   X-Forwarded-For    $remote_addr;
        proxy_set_header   X-Real-IP          $remote_addr;

        # optionally, you can adjust the POST request size limit, to allow adding a lot of torrents at once:
        #client_max_body_size 100M;

        # since v4.2.2, is possible to configure qBittorrent
        # to set the "Secure" flag for the session cookie automatically.
        # However, that option does nothing unless using qBittorrent's built-in HTTPS functionality.
        # For this use case, where qBittorrent itself is using plain HTTP
        # (and regardless of whether or not the external website uses HTTPS),
        # the flag must be set here, in the proxy configuration itself:
        proxy_cookie_path / "/; Secure";
    }

    # OPTIONAL: serve static HTML files at the root of the domain, like a simple homepage
    location / {
        root /var/www/html;
        try_files $uri $uri/ =404;
    }

    # OPTIONAL: you can add more "location { (...) }" stanzas for other services, such as Nextcloud, etc
    #location /other_webapp {
        # change the location and port to the location and port the application is actually listening on
        #proxy_pass              http://localhost:8080/;
        #proxy_set_header        X-Forwarded-Proto           $scheme;
        #proxy_set_header        X-Forwarded-Host            $http_host;
        #proxy_set_header        X-Forwarded-For             $proxy_add_x_forwarded_for;
        #proxy_set_header        X-Real-IP                   $remote_addr;
    #}
}

Obtain the certificate

Run the following commands to obtain your certificate (replace yourdomain.com with your actual domain):

sudo certbot --nginx certonly --preferred-challenges http --must-staple --redirect --hsts --uir --staple-ocsp --rsa-key-size 4096 --domain yourdomain.com --domain www.yourdomain.com

Take note of the location where certbot stored the certificate, and adjust the nginx configuration file if needed. If your certbot is setup correctly, it will renew your certificate automatically, so you do not need to worry. You can manually test the renewal process with sudo certbot renew --dry-run, or actually manually renew your certificates with sudo certbot renew.

Note: the following five options used above are optional, but good for hardened security:

--rsa-key-size 4096
--must-staple
--redirect
--hsts
--uir
--staple-ocsp

Refer to the documentation for more info.

Test your setup

Start nginx: sudo systemctl restart nginx.service

Access your WebUI via yourdomain.com/qbt. You should see the qBittorrent Web UI and the indication that your connection is over HTTPS.

9.0 KiB Raw Blame History