ANSWERED Gluetun VPN - connection issue

[osalj 0]

Hi,

I use AirVPN on a Windows virtual machine to download files via Qbittorrent.

A few days ago I set up Docker in LXC and on it the entire SERVARR, including Gluetun VPN and Qbittorrent.

Docker configuration:
 

networks:
  servarrnetwork:
    ipam:
      config:
        - subnet: 172.18.0.0/24

services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun # If running proxmox see readme for more info.
    networks:
      servarrnetwork:
        ipv4_address: 172.18.0.2
    ports:
      - 8080:8080 # qbittorrent web interface
      - 12789:12789 # qbittorrent torrent port
      - 6789:6789 # nzbget
      - 9696:9696 # prowlarr
      - 5800:5800 # firefox
    volumes:
      - /docker/gluetun:/gluetun
    environment:
      - VPN_SERVICE_PROVIDER=airvpn
      - VPN_TYPE=wireguard
      - FIREWALL_VPN_INPUT_PORTS=12789
      - WIREGUARD_PRIVATE_KEY=___KEY___
      - WIREGUARD_PRESHARED_KEY=____KEY____
      - WIREGUARD_ADDRESSES=10.166.233.17/32
      - SERVER_COUNTRIES=UNITED KINGDOM
      - SERVER_CITIES=LONDON
      - HEALTH_VPN_DURATION_INITIAL=120s
      - WIREGUARD_PERSISTENT_KEEPALIVE_INTERVAL=15s
#      - VPN_PORT_FORWARDING=on
#      - TORRENTING_PORT=2207
    healthcheck:
      test: ping -c 1 www.google.com || exit 1
      interval: 60s
      timeout: 20s
      retries: 5
    restart: unless-stopped

# This is a new addition since creating the tutorial video on this stack. 
# See the 'qBittorrent Stalls with VPN Timeout' section for more information.
  deunhealth:
    image: qmcgaw/deunhealth
    container_name: deunhealth
    network_mode: none
    environment:
      - LOG_LEVEL=info
      - HEALTH_SERVER_ADDRESS=127.0.0.1:9999
      - TZ=Europe/London
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

# Healthcheck was added to work with deunhealth to restart container
# on unhealthy status. labels allows deunhealth to monitor.
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    restart: unless-stopped
    labels:
      - deunhealth.restart.on.unhealthy=true
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - WEBUI_PORT=8080
      - TORRENTING_PORT=12789
    volumes:
      - /docker/qbittorrent:/config
      - /data:/data
    depends_on:
      - gluetun
    network_mode: service:gluetun
    healthcheck:
        test: ping -c 1 www.google.com || exit 1
        interval: 60s
        retries: 3
        start_period: 20s
        timeout: 10s

Gluetun connects without a problem, Qbittorrent works correctly, port forwarding too.

I only have a problem, because when I check the connection status on the AirVPN website it shows me that the connection is not active.



When I check this connection inside the Qbittorrent or GlueTun container via the command wget -qO- https://ipinfo.io I get:

"ip": "217.151.98.163",
"city": "London",
"region": "England",
"country": "GB",
"loc": "51.5085,-0.1257",
"org": "AS9009 M247 Europe SRL",
"postal": "E1W",
"timezone": "Europe/London",
"readme": "https://ipinfo.io/missingauth"

So the connection works.

Why does the AirVPN website show me that the connection is not active?

TIA! Edited ... by osalj

[Staff 10144]

Hello!

According to the ticket the problem could not be reproduced anymore after the initial event. If it was a glitch of the account panel, apparently it was momentary.

Kind regards