https://github.com/master-hax/compose-wireguard-deluge

a multi-container application to run Deluge behind a Wireguard client
https://github.com/master-hax/compose-wireguard-deluge

bittorrent deluge deluge-daemon deluge-web docker docker-compose port-forwarding torrent torrent-client udp vpn wireguard

Last synced: 1 day ago
JSON representation

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

• Host: GitHub
• URL: https://github.com/master-hax/compose-wireguard-deluge
• Owner: master-hax
• Created: 2022-01-24T05:42:00.000Z (almost 3 years ago)
• Default Branch: master
• Last Pushed: 2024-08-14T02:31:28.000Z (3 months ago)
• Last Synced: 2024-08-14T04:04:31.001Z (3 months ago)
• Topics: bittorrent, deluge, deluge-daemon, deluge-web, docker, docker-compose, port-forwarding, torrent, torrent-client, udp, vpn, wireguard
• Homepage:
• Size: 12.7 KB
• Stars: 15
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# compose-wireguard-deluge

a multi-container Docker application to run [Deluge](https://hub.docker.com/r/linuxserver/deluge) behind a [Wireguard](https://hub.docker.com/r/linuxserver/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](/docker-compose.yml)

1. put your `wg0.conf` file into `./wireguard`

1. 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`

1. forward a port with your VPN provider

1. (probably not required) add port forwarding to your `wg0.conf` using the rules proposed [here](https://github.com/linuxserver/docker-wireguard/issues/58#issuecomment-723702782), then set up that same port in Deluge as the incoming port.

1. 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](https://docs.docker.com/network/links/).

## note: an [OpenVPN version](https://github.com/master-hax/compose-openvpn-deluge) is also available