Having an issue where I can internally on my local network access rutorrent, but my external network I cannot access rutorrent anymore via the DNS I had setup.
The issue started happening once I upgraded my config to use wireguard. The wireguard works for rutorrent perfectly and can be accessed like I said via LAN clients. But it broke the ability to access the docker container remotely.
I tried rolling back the config to use the old openvpn config, and it works again fine, but the second I go to use the new wireguard config, it breaks the external networks ability to access. Even when accessing via the external DNS method on a local machine on the network, it does not work, but the second i revert the config back to openvpn config, it works.
The only change really in the docker config I see is the addition of:
--sysctl="net.ipv4.conf.all.src_valid_mark=1" \
--privileged=true \
and removal of:
--cap-add=NET_ADMIN \
could it be the iptables that the container uses needs updating? Does the valid_mark sysctl rule cause external source requests to drop?
thoughts?
full config:
docker run -d \
--sysctl="net.ipv4.conf.all.src_valid_mark=1" \
--privileged=true \
-p 8118:8118 \
-p 9443:9443 \
--name=torrentvpn \
-v /docker/torrentvpn/data:/data \
-v /docker/torrentvpn/config:/config \
-v /mnt/pool:/pool \
-v /etc/localtime:/etc/localtime:ro \
-e VPN_ENABLED=yes \
-e VPN_USER= \
-e VPN_PASS= \
-e VPN_PROV=pia \
-e VPN_CLIENT=wireguard \
-e STRICT_PORT_FORWARD=yes \
-e ENABLE_PRIVOXY=yes \
-e ENABLE_AUTODL_IRSSI=yes \
-e ENABLE_RPC2=yes \
-e ENABLE_RPC2_AUTH=yes \
-e ENABLE_WEBUI_AUTH=yes \
-e RPC2_USER= \
-e RPC2_PASS= \
-e WEBUI_USER= \
-e WEBUI_PASS= \
-e LAN_NETWORK=192.168.0.0/24 \
-e NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1 \
-e DEBUG=false \
-e PHP_TZ=UTC \
-e UMASK=000 \
-e PUID=0 \
-e PGID=0 \
binhex/arch-rtorrentvpn
