IP leaked when nordvpn is disconnected

[xrfmkrh]

version : 2.1.2
i run azinchen/nordvpn:2.1.2 with whoogle. when i stop nordvpn only, IP leak in whoogle for a while and stopped.
i downgraded version and not occur in 0.9.6
similar issue on bubuntux/nordvpn
sorry for my bad english but hope you understand.
thank you.

[azinchen]

Could you describe steps to reproduce?

[xrfmkrh]

you can refer to this
or in my case i used this docker-compose.yml to run whoogle with nordvpn

version: "2.4"
services:
  vpn:
    image: azinchen/nordvpn:2.1.2
    network_mode: bridge
    cap_add:
      - NET_ADMIN    
    devices:
      - /dev/net/tun   
    ports:
      - "5000:5000"
    environment:   
      - USER=set
      - PASS=set
      - COUNTRY=set
      - GROUP=Standard VPN servers
      - PROTOCOL=openvpn_udp
      - RANDOM_TOP=10
      - OPENVPN_OPTS=--pull-filter ignore "ping-restart" --ping-exit 180
    restart: unless-stopped
  whoogle-search:
    image: ${WHOOGLE_IMAGE:-benbusby/whoogle-search}:0.7.4
    container_name: whoogle-search_1
    network_mode: service:vpn
    depends_on:
      - vpn
    pids_limit: 50
    mem_limit: 512mb
    memswap_limit: 512mb
    # user debian-tor from tor package
    user: whoogle
    security_opt:
      - no-new-privileges
    cap_drop:
      - ALL
    tmpfs:
      - /config/:size=10M,uid=927,gid=927,mode=1700
      - /var/lib/tor/:size=15M,uid=927,gid=927,mode=1700
      - /run/tor/:size=1M,uid=927,gid=927,mode=1700
    #env_file: # Alternatively, load variables from whoogle.env
      #- whoogle.env
    restart: unless-stopped

when containers running, i stop nordvpn container. at the same time refresh whoogle-search's search page, i can see my real location(based on ip address) for a second. and after that, whoogle-search is stopped too

[SirCupOfReese]

I've encountered a similar issue as well. When the VPN has any kind of connection issue, etc, a lot of my traffic seems to come rushing out across my real IP. It's actually caused a few problems. Is there any kind of temporary fix for this?

[cjohnson-phys]

Could this be fixed with NordVPN's killswitch?

[SirCupOfReese]

Has there been any update on this @azinchen? I'd love to start using this again, it was tremendously helpful, but I'd rather not do so unless whatever is causing this has been fixed.

If it can't be fully fixed right now, is there any kind of temporary stop-gap we can use? Is it possible to enable Nord's built-in killswitch feature on specific instances of this container?

[azinchen]

Not sure it might help.
test ip leak issue with docker pull azinchen/nordvpn:222-ip-leaked-when-nordvpn-is-disconnected