April 8, 20233 yr I had everything working fine until I updated a "Docker Patch". Now when I test a torrent with torrent leak test, It comes up as my home IP. I literally didn't change a thing. I have wireguard on it's own with a qbittorrent container that routes thru the WG container. I also have the qbittorrent container run a custom ip tables config. I'm just not sure what changed after this docker patch that could be causing this inconsistency. If anyone has any ideas or needs more info lmk. tower-diagnostics-20230124-1410.zip Edited April 8, 20233 yr by baazaar13
April 8, 20233 yr Author I have narrowed it down to an ip route issue. It seems my custom-cont-init.d iptables config does not execute anymore on container start-up. If I manually configure the ip table for the qbittorrent container it starts to work. The exact same ip routing instruction that are in my custom-cont-init.d folder. Strange huh. Edited April 8, 20233 yr by baazaar13
April 8, 20233 yr Author Solution I figured it out. There were changes to the location requirements of custom init files.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.