I've tried setting this up with an orchestrator but I had issues with accessing the container from the reverse proxy. I think it is because rtorrent was trying to setup the iptables passthrough for web ui on 172.18.x.x but the network subnet for the overlay network was 10.x.x.x. (if I manually connected the container to the network with 172.18.x.x ip I could access the ui through that ip)
Could we have an env var to force cidr range that is used in the iptable rules?
Hi,
I've tried setting this up with an orchestrator but I had issues with accessing the container from the reverse proxy. I think it is because rtorrent was trying to setup the iptables passthrough for web ui on 172.18.x.x but the network subnet for the overlay network was 10.x.x.x. (if I manually connected the container to the network with 172.18.x.x ip I could access the ui through that ip)
Could we have an env var to force cidr range that is used in the iptable rules?