Leaderboard

While I love that you continue to support OpenVPN would you please reconsider a few WireGuard‑only 10–20 Gbit servers to quantify the uplift for users who prioritize raw speed and low latency? It’s my understanding that OpenVPN server processes are single‑threaded and CPU‑intensive. Co‑hosting OpenVPN and WireGuard on the same high‑capacity host (10–20 Gbit) can constrain aggregate throughput under load because per‑core bottlenecks caps per‑host headroom when many OpenVPN clients are active. In cities where you have multiple 20 Gbit servers like New York dedicating one to Wireguard doesn't seem unreasonable? Thank you for your consideration.

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!

remote-random remote bg.vpn.airdns.org 443 remote be.vpn.airdns.org 443 remove: persist-tun