@Cuscuz@lemmy.world to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish • 2 years agoBitTorrent Pirates Won’t Receive ISP Warnings (It Will Be Something Worse)torrentfreak.commessage-square114fedilinkarrow-up1220arrow-down10
arrow-up1220arrow-down1external-linkBitTorrent Pirates Won’t Receive ISP Warnings (It Will Be Something Worse)torrentfreak.com@Cuscuz@lemmy.world to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish • 2 years agomessage-square114fedilink
minus-square@ANIMATEK@lemmy.worldlinkfedilinkEnglish2•2 years agoYou have to expose the qbt http port in your VPN container. All API communication (arrs etc) goes through here.
minus-square@Appoxo@lemmy.dbzer0.comlinkfedilinkEnglish1•2 years agoAfter much thinking I managed it myself and found that out as well. What I also needed was the environment variable FIREWALL_OUTBOUND_SUBNETS so my other containers could connect to the container.
You have to expose the qbt http port in your VPN container. All API communication (arrs etc) goes through here.
After much thinking I managed it myself and found that out as well. What I also needed was the environment variable
FIREWALL_OUTBOUND_SUBNETSso my other containers could connect to the container.