You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: