Open rthidfrev opened 3 years ago
I'm no longer using Deluge, but if you're using this example helper container as-is, then it expects the config to be mounted at /deluge/config
rather than /config
. So:
deluge-port-helper:
container_name: deluge_port_forwarding
build: /media/homemedia/pia/pia
volumes:
- ${ROOT}/pia-shared:/pia-shared
- ${ROOT}/config/deluge:/deluge/config
network_mode: "service:vpn"
depends_on:
- vpn
- deluge
From memory, using deluge-console
was a bit unstable at times, so it might need some retry logic added if something unexpected happens.
Alternatively, if you're not having much luck scripting it, you can set the env var PORT_PERSIST=1
on the vpn container, and then just enter the forwarded port manually into Deluge. IIRC PIA will give the same forwarded port number for two months if done this way.
I got port forwarding to work by a work-around hacky solution
ln -s /config/port.dat /pia/forwarded_port
it should just work after that, no need for another container
huge, ty !
I've just added the option to set where the forwarded port number gets dumped to. That way you can set PORT_FILE=/path/to/forwarded_port
and then mount it into both containers as-is without needing to use symlinks. Should make things a tad simpler.
I have wireguard-pia and deluge working fine, but I don't upload, I think I misconfigured my compose docker, I'm a beginner and I'm lost, can somebody help me pls. ty !