Leaderboard

For anybody wanting to utilize AirVPN via a Docker VPN client container, Gluetun has now added AirVPN support for both OpenVPN and WireGuard connections. The container itself is very lightweight and fast. https://github.com/qdm12/gluetun Here's an example of a Portainer Stack using Gluetun as the path to the Internet for a Firefox container: version: '3.7' services: gluetun: image: qmcgaw/gluetun:latest container_name: gluetun cap_add: - NET_ADMIN ports: - 8100:8000 # Remote Control VPN - 3000:3000 # Firefox environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=openvpn - SERVER_COUNTRIES=Canada - OPENVPN_CIPHERS=AES-256-GCM - PUID=1000 - PGID=1000 - TZ=America/Denver volumes: - /data/openvpn:/gluetun # /data/openvpn contains client.crt and client.key firefox: image: lscr.io/linuxserver/firefox:latest container_name: firefox environment: - PUID=1000 - PGID=1000 - TZ=America/Denver volumes: - /data/firefox:/config shm_size: '1gb' network_mode: 'service:gluetun' depends_on: - gluetun You'll need to add client.crt and client.key files to the directory you have mapped to /config for OpenVPN. For WireGuard, change the VPN_TYPE= to wireguard, and add WIREGUARD_PRIVATE_KEY=, WIREGUARD_PRESHARED_KEY=, and WIREGUARD_ADDRESSES= environment variables to your stack. In both cases, you can get the data you need from the Config Generator in the AirVPN Client Area. The Gluetun container can also be configured to provide an HTTP or Shadowsocks proxy to your entire network. AirVPN rocks, and the ability to connect to it through a Docker VPN Client container makes it that much better!

@Weasel Hi, The thing you described is called anycast. In simple words there are several main entry points used by all users (like 1.1.1.1 & 1.0.0.1 for Cloudflare public DNS or 185.228.168.168 for Cleanbrowsing in your case) which will automatically redirect your requests to the closest node in order to improve performance, reliability and response times. ipleak doesn't show host names but if you check 173.205.92.162 for example here, you'll see that it's dns-edge-usa-west-seattlex.cleanbrowsing.org (in other words just Cleanbrowsing's node)

2.22.2 seems to have resolved it.