airvpn setup works on one machine but not on the other

[Staubgeborener]

This is my very basic docker example for gluetun and qbittorrent:

services:
  gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    environment:
      - LOG_LEVEL=debug
      - VPN_SERVICE_PROVIDER=airvpn
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY=XXX
      - WIREGUARD_PRESHARED_KEY=XXX
      - WIREGUARD_ADDRESSES=XXX
      #- DNS_ADDRESS=${DNS_ADDRESS}
      - HTTPPROXY=on
    ports:
      - 8080:8080
      - 8888:8888/tcp # For Gluetun's built-in HTTP proxy (if needed)
      - 8388:8388/tcp # For Gluetun's built-in Shadowsocks server (if needed)
      - 8388:8388/udp # For Gluetun's built-in Shadowsocks server (if needed)
    volumes:
      - ./gluetun:/gluetun
    restart: unless-stopped

  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    network_mode: service:gluetun
    container_name: qbittorrent
    depends_on:
      - gluetun
    environment:
      - WEBUI_PORT=8080
      - PUID=1000
      - PGID=1000
      - TZ=${TZ}
      - DOCKER_MODS=ghcr.io/gabe565/linuxserver-mod-vuetorrent # Add /vuetorrent as alternative WebUI
    volumes:
      - ./qbittorrent/config:/config
      - ./qbittorrent/downloa

I created the wireguard config via airvpn vonfig manager. This setup works perfectly with a virtual machine running kubuntu. Now i tried this on another (non virtual) machine which runs debian. All i get is this docker log:

2024-10-31T15:39:03Z DEBUG [wireguard] Wireguard server public key: XXX
2024-10-31T15:39:03Z DEBUG [wireguard] Wireguard client private key: XXX=
2024-10-31T15:39:03Z DEBUG [wireguard] Wireguard pre-shared key: XXX=
2024-10-31T15:39:03Z INFO [firewall] allowing VPN connection...
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/iptables -t filter -L OUTPUT --line-numbers -n -v
2024-10-31T15:39:03Z DEBUG [firewall] found iptables chain rule matching "--delete OUTPUT -d 193.37.252.162 -o eth0 -p udp -m udp --dport 1637 -j ACCEPT" at line number 4
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/iptables -t filter -D OUTPUT 4
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/iptables -t filter -L OUTPUT --line-numbers -n -v
2024-10-31T15:39:03Z DEBUG [firewall] found iptables chain rule matching "--delete OUTPUT -o tun0 -j ACCEPT" at line number 4
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/iptables -t filter -D OUTPUT 4
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/ip6tables -t filter -L OUTPUT --line-numbers -n -v
2024-10-31T15:39:03Z DEBUG [firewall] found iptables chain rule matching "--delete OUTPUT -o tun0 -j ACCEPT" at line number 4
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/ip6tables -t filter -D OUTPUT 4
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/iptables --append OUTPUT -d 134.19.179.170 -o eth0 -p udp -m udp --dport 1637 -j ACCEPT
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/iptables --append OUTPUT -o tun0 -j ACCEPT
2024-10-31T15:39:03Z DEBUG [firewall] /sbin/ip6tables --append OUTPUT -o tun0 -j ACCEPT
2024-10-31T15:39:03Z INFO [wireguard] Using available kernelspace implementation
2024-10-31T15:39:03Z INFO [wireguard] Connecting to 134.19.179.170:1637
2024-10-31T15:39:03Z DEBUG [netlink] ip rule add lookup 51820 pref 101
2024-10-31T15:39:03Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
2024-10-31T15:39:09Z INFO [dns] downloading hostnames and IP block lists
2024-10-31T15:39:18Z ERROR [vpn] getting public IP address information: fetching information: Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2024-10-31T15:39:24Z WARN [dns] cannot update filter block lists: Get "https://raw.githubusercontent.com/qdm12/files/master/malicious-hostnames.updated": context deadline exceeded (Client.Timeout exceeded while awaiting headers), Get "https://raw.githubusercontent.com/qdm12/files/master/malicious-ips.updated": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2024-10-31T15:39:24Z INFO [dns] attempting restart in 1m20s

It seems like there is an issue while trying to resolve a hostname.

[Staubgeborener]

I will close this, fresh install works perfectly. I guess the issue was with the iptables /nftables settings on the system.