Deluge
Bittorrent downloader.
Migrated to ansible collection
Use r_pufky.arr.deluge.
Tip
- The UID/GID should be set to a user/group that has access to your media. All media clients should run under the same user to run correctly.
- Your downloader will report the download path mapped in the downloader service. You need to map this exact path in Deluge for it to be able to post-process downloads properly.
- Deluge must be connected to the Daemon to write configuration changes. Select Connection Manager ➔ Connect when logging in.
- max_upload_speed should be set to a non-zero number to enable downloads.
Reverse Proxy
Deluge should be run via a Reverse Proxy, allowing you to isolate and wrap connections in SSL. See NGINX for more details. See Base Proxy Control for basic proxy configuration.
/etc/nginx/conf.d/reverse_proxy.conf
0644 root:root
# Subdomain
server {
listen 443 ssl http2;
server_name deluge.{DOMAIN} deluge;
location / {
proxy_pass http://deluge:8112;
include /etc/nginx/conf.d/proxy-control.conf;
add_header X-Frame-Options SAMEORIGIN;
}
}
/etc/nginx/conf.d/reverse_proxy.conf
0644 root:root
# Subpath
server {
location /deluge {
proxy_pass http://deluge:8112/;
include /etc/nginx/conf.d/proxy-control.conf;
proxy_set_header X-Deluge-Base '/deluge/';
add_header X-Frame-Options SAMEORIGIN;
}
}