Skip to content

a multi-container application to run Deluge behind a Wireguard client

Notifications You must be signed in to change notification settings

master-hax/compose-wireguard-deluge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 

Repository files navigation

compose-wireguard-deluge

a multi-container Docker application to run Deluge behind a Wireguard client

WARNING: due to a docker limitation, some network traffic can escape before wireguard connects. to fix this, you should move the wireguard container to a separate compose file

how to set it up

  1. download docker-compose.yml
  2. put your wg0.conf file into ./wireguard
  3. run docker-compose up

if everything works correctly, Deluge should be running behind your VPN!

how to use it

the Deluge web UI should be accessible at http://localhost:8112

if you want to use this persistently, you should probably

  1. change the locations of the deluge-data-volume & downloads-volume
  2. forward a port with your VPN provider
  3. (probably not required) add port forwarding to your wg0.conf using the rules proposed here, then set up that same port in Deluge as the incoming port.
  4. lock the containers to specific versions using sha256 digests e.g. linuxserver/wireguard@sha256:39dd71c3440b93b3e0343aa88b8d415cf07a43e60df208cad6e55e7d2758959e

how it works

the torrent-client (Deluge) service shares the network stack of the vpn-sidecar service (Wireguard), which is tunneled through your VPN provider. to maintain local connectivity to the torrent-client container's web UI, we proxy to it to through the web-proxy service (Nginx) using Docker container links.

note: an OpenVPN version is also available