Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UDP and HTTP trackers are being blocked #386

Open
sservaes opened this issue Sep 6, 2023 · 0 comments
Open

UDP and HTTP trackers are being blocked #386

sservaes opened this issue Sep 6, 2023 · 0 comments

Comments

@sservaes
Copy link

sservaes commented Sep 6, 2023

I have recently been running into an issue where qBittorrent blocks all UDP and HTTP trackers within the VPN container which is setup as follows (and used to work for me):

docker run -d --name vpn --cap-add=NET_ADMIN --device /dev/net/tun -p 9117:9117 -p 9696:9696 -p 7878:7878 -p 8989:8989 -p 6881:6881 -p 6881:6881/udp -p 8081:8081 -p 8686:8686 -p 8787:8787 -e NETWORK=192.168.1.0/24 -e USER=myemail@mail.com -e PASS='mypassword' -e TECHNOLOGY=NordLynx -e DEBUG=trace azinchen/nordvpn:latest

docker run -d --name=qbittorrent -e PUID=1028 -e PGID=100 -e TZ=America/New_York -e WEBUI_PORT=8081 --net=container:vpn -v /volume1/docker/qbittorrent:/config -v /volume1/Media/torrents:/volume1/Media/torrents --restart unless-stopped lscr.io/linuxserver/qbittorrent

qBittorrent is run on port 8081, but all these trackers are 'unreachable'.
Not using the container or using https trackers allow traffic to pass through with no issues.

Any suggestions as to what I can do about this to resolve it?

Many thanks, loving this implementation of NordVPN in a containerized format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant