Skip to content

qBittorrent WebDAV Integration

Stream torrents through Stremio by running your own qBittorrent instance with a WebDAV server. MediaFusion downloads torrents to qBittorrent and streams the files over WebDAV.

Prerequisites

Docker installed on the machine that will run qBittorrent.

Step 1: (Optional) Create a WebDAV password file

To password-protect WebDAV access:

htpasswd -cBm .htpasswd your_username
# Enter and confirm your password when prompted

Generate an MD5 hash at a site like htpasswd.org, then create a file manually:

username:$apr1$...hash...

Step 2: Run the Docker image

Build the image from the repository so that you run the current qBittorrent release:

docker build -t qbittorrent-webdav:latest deployment/qbittorrent-webdav

docker run -d \
  --name=qbittorrent-webdav \
  --restart unless-stopped \
  -p 8080:80 \
  -p 6881:6881/tcp \
  -p 6881:6881/udp \
  -v /path/to/downloads:/downloads \
  qbittorrent-webdav:latest

With WebDAV password protection: 

docker run -d \
  --name=qbittorrent-webdav \
  --restart unless-stopped \
  -p 8080:80 \
  -p 6881:6881/tcp \
  -p 6881:6881/udp \
  -v /path/to/.htpasswd:/etc/apache2/.htpasswd \
  -v /path/to/downloads:/downloads \
  qbittorrent-webdav:latest

Step 3: Get the initial qBittorrent password

docker logs qbittorrent-webdav

Look for a line like The WebUI administrator password was not set. A temporary password is provided for this session: xxxxxxxx.

Access the qBittorrent WebUI at http://localhost:8080/qbittorrent/ with username admin and the temporary password.

WebDAV is available at http://localhost:8080/webdav/.

Step 4: Configure MediaFusion

  1. Open MediaFusion → Configure → Streaming Provider → select qBittorrent – WebDav
  2. Get the container's IP address (needed if MediaFusion is also running in Docker): 
    docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' qbittorrent-webdav
  3. Fill in the URLs:
  4. MediaFusion running locally (not in Docker): use http://localhost:8080
  5. MediaFusion running in Docker: use http://<container_ip>:8080
  6. Enter your WebDAV credentials if you set a password; leave blank if not
  7. Adjust Play video after download (e.g. 30 = start playing when 30% is downloaded) and the download wait timeout in seconds if the torrent needs longer than 5 minutes to get there. Leave prioritize first and last pieces on unless you always wait for the entire file.
  8. Save the configuration

Stored qBittorrent and WebDAV credentials are encrypted with the instance's SECRET_KEY and masked in configuration responses. On API or worker startup, existing profiles are backfilled into encrypted storage and their Redis profile caches are invalidated. Keep the same SECRET_KEY when upgrading; the backfill stops on unreadable encrypted secrets rather than overwriting them.

Playback uses the configured download wait for qBittorrent, including waits longer than the general HTTP request timeout. The resolver and concurrent requests allow for metadata lookup and a retry as well. If you run MediaFusion behind a reverse proxy, its response timeout and the player's timeout must also allow the wait. Both qBittorrent 4.x paused torrents and 5.x stopped torrents resume automatically.

Playing before the download finishes

Playback starts as soon as the threshold is reached, and the player reads the file over WebDAV while qBittorrent keeps writing to it. Two things make this usable: MediaFusion asks qBittorrent to download only the file you picked, so a season pack does not queue the whole run, and it enables prioritize first and last pieces, so the head of the file arrives before the middle.

What you cannot do is seek far ahead. Only the head and tail are fetched first, so anything past the downloaded portion is still zero-filled until qBittorrent gets there — playback starts, then stalls or shows artefacts rather than failing cleanly. Pick a threshold you are comfortable with, and turn prioritize first and last pieces off if you always wait for the whole file anyway.

Public hosting security

If you expose qBittorrent-WebDAV publicly, always use a strong WebDAV password and HTTPS.

Local vs. community-hosted MediaFusion

  • Local: run both MediaFusion and qBittorrent-WebDAV on the same machine or LAN
  • Community-hosted: expose qBittorrent-WebDAV publicly (with HTTPS and authentication) and connect it to the community MediaFusion instance