Closed she11sh0cked closed 3 years ago
I don't really know what the issue with deluge is. I've gotten it to work in the past... Anyway! This qBittorrent configuration works (somehow), so I'll be using it for now.
services:
qbittorrent:
image: ghcr.io/linuxserver/qbittorrent
container_name: qbittorrent
restart: always
volumes:
- configqbittorrent:/config
- downloadstorrents:/data/downloads/torrents
environment:
- PGID=${PGID}
- PUID=${PUID}
- TZ=${TZ}
- WEBUI_PORT=8181
ports:
- 6881:6881
- 6881:6881/udp
labels:
- "traefik.enable=true"
- "traefik.http.routers.qbittorrent.rule=Host(`qbittorrent.${TRAEFIK_DOMAIN}`)"
- "traefik.http.services.qbittorrent-seedbox.loadbalancer.server.port=8181"
volumes:
configqbittorrent:
driver: local-persist
driver_opts:
mountpoint: /data/config/qbittorrent
downloadstorrents:
driver: local-persist
driver_opts:
mountpoint: /data/shared/downloads/torrents
I would be happy to hear if anyone else has this issue though!
That is strange, I never had any issue with Deluge.
Here is my configuration:
Keep in mind that mapping the port with the one on the host exposes your server and increases the attack surface. Normally for seeding torrents you do not need it.
I'm closing this issue since I cannot reproduce it. Feel free to re-open it if you need.
Deluge doesn't seem to be able to seed anything. Probably because of the HTTP auth.