search

soxfor / qbittorrent-natmap

The objective of this container is to run a script that requests a port forward (via NAT-PMP) from the VPN provider and upon success changes the listening port of the qBittorrent client when running in Docker
133 stars 17 forks source link

Connection between Qbitt and Gluetun - only network mode supported? #2

Closed Stiefmeister closed 1 year ago

Stiefmeister commented 1 year ago

I suppose http proxy will not work within Qbitt and network mode (--network=container:gluetun) is required?

Thanks for clarification!

soxfor commented 1 year ago

The reason for it needing to use network=container:gluetun or network=service:gluetun (either/or, depending on how it's deployed/implemented) is the need to access the tun interface of the VPN container, so that the VPN endpoint can be contacted to request the NAT-PMP/port forward.

IIRC, using SOCKS5 or HTTP proxy (for peer-to-peer connections) won't allow for a port foward to be used. The torrent client is essentially un-connectable/firewalled.

Stiefmeister commented 1 year ago

Thanks for the quick reply; that's what I thought