Leaderboard

Hello! VPNs are not in the scope of both the legislation and trivial tech considerations, as we don't have the keys for the communications: chat, instant messages and e-mails are encrypted end-to-end without our keys, but with the keys of the parties and/or the keys of the service offering e-mail / chat / messaging service, so we can't decrypt anything in any case. With that said, this abomination must be fought. We repute it is incompatible with the Charter of Fundamental Rights and with various CJEU decisions on data retention and privacy. We feel to share the position and the consideration offered by Tuta and EDRi here and here: https://tuta.com/blog/chat-control-criticism https://edri.org/our-work/most-criticised-eu-law-of-all-time/ Unfortunately, opposition has become more difficult because big AI actors see chat control as a great opportunity and they have spent tens of millions to lobby in favor of this abominable regulation. This is the main explanation that tells you why various politicians have changed their positions. Kind regards

Nice job! So now you are into your own network and the server/service is handing out the unauthorized status based on a local ACL. You are on your way! Happy hunting!

Sounds like you are making great progress, congrats! It sounds to me like everything is working as it should now, so we need to either: reset your expectations and correct your assumptions, or have you communicate why you think something should work a certain way or what your goals are. Putting your first and third posts together, it sounds like you expect to see the WebGUI on multiple ports. Can you explain why you would want that? I'm not going to say you couldn't engineer that, but I'm going to challenge your thinking here. Let's assume your machine has a local network static IP of 10.77.77.42; you access the WebGUI with http://10.77.77.42:8082 right? Why do you need additional access on port 27586? Are you trying to admin qBittorrent from outside your network? You haven't stated that before which is why I ask. Many users are uncomfortable exposing their WebGUI to the world, so you need to be clear that this is your desire (and secure it with https before doing so!). How many ports do you have forwarded from AirVPN? Are ports 8082 and 27586 in pool #2 (saving pool #1 ports for P2P users is the goal here)? Your line "FIREWALL_VPN_INPUT_PORTS=8082,27586,27587" isn't going to work unless all three of those ports are forwarded from AirVPN. I believe the most common use case is to only forward the torrenting port from pool #1 (27587) keeping the WebGUI port just for local network use. Lets check your devices to ensure they are not an issue. When you go to the devices screen have you set up a device? Then in the ports screen is that device linked to the port (in the dropdown)? And when making your config file did you select that device? When working correctly, the sessions screen should list your device at the top of the card when connected.

It would probably be faster for everyone to simply show you my stack: # This is a P2P demonstration stack template which has been tested to work well with AirVPN as of January 2025. # Use AirVPN's config generator to obtain your specific values (https://airvpn.org/generator). Make sure to specify your device. # Remember that the indentation of a Docker Compose file is important. services: gluetun: image: qmcgaw/gluetun:latest container_name: gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - WIREGUARD_PUBLIC_KEY= # copy from config file - WIREGUARD_PRIVATE_KEY= # copy from config file - WIREGUARD_PRESHARED_KEY= # copy from config file - WIREGUARD_ADDRESSES= # copy from config file - SERVER_REGIONS= # optional, comma seperated list, no spaces after commas, make sure it matches the config you created - SERVER_COUNTRIES= # optional, comma seperated list, no spaces after commas, make sure it matches the config you created - SERVER_CITIES= # optional, comma seperated list, no spaces after commas, make sure it matches the config you created - FIREWALL_VPN_INPUT_PORTS= # mandatory, the port number AirVPN forwarded for you (from pool #1) should appear here - TZ= # choose timezone value from list at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones (e.g.: Asia/Tokyo) ports: - 8080:8080 # qbittorrent web GUI, port number can be changed BUT it must match WEBUI_PORT in qbittorrent service environment - (port forwarded from AirVPN):(port forwarded from AirVPN) # also place in TORRENTING_PORT field in qbittorrent service environment restart: unless-stopped qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent depends_on: gluetun: condition: service_healthy restart: true environment: - PUID= # your desired user's number - PGID= # your desired user's group number - TZ= # choose timezone value from list at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones - WEBUI_PORT=8080 # must match "qbittorrent web GUI" port number in gluetun's service above - TORRENTING_PORT=(port forwarded from AirVPN) # must match forwarded port number in gluetun's service above volumes: - /mnt/(your folder structure here):/config # directory you want to save your qbittorrent config files - /mnt/(your folder structure here):/downloads # qbittorrent download location restart: unless-stopped network_mode: "service:gluetun" # this is what forces qbittorrent to only use the VPN connection from gluetun Hope this helps!

Some differences between yours and mine are: I also use Wireguard and I have "- WIREGUARD_PUBLIC_KEY=[redacted]" and you don't; I don't have any volumes set up, everything in the docker compose; You aren't specifying the latest image, consider using "qmcgaw/gluetun:latest"; I do not use CIDR notation for the "WIREGUARD_ADDRESSES" and you do, consider trying it without the "/32"; Are you sure your forwarded port is in AirVPN's pool #1? For P2P it has to be. For qBittorrent: again use the latest: "lscr.io/linuxserver/qbittorrent:latest" consider adding the following for robustness: "depends_on: gluetun: condition: service_healthy restart: true" You don't have "TORRENTING_PORT=[your pool #1 port number]"; Its usually best to have these in the same stack, not separate containers. Keep trying, it DOES work.