Connected but unhealthy

[godfuture]

⚠️ Make sure to follow the template, troubleshoot on your own first, review Open/Closed Issues, Discussions, Wiki and consider creating a discussion thread instead. ⚠️

Describe the bug

Docker container is deployed and started correctly showing green status "healthy". Connection is up and running. All seems ok. After some time (mostly after some days, last issue appeared after 6 days) health goes to yellow "unhealthy". No traffic is going through the tunnel anymore. A restart of docker container solves the issue for next couple of days. This issue was not existant two years ago. It started some time in 2024 or end of 2023.

To Reproduce using docker CLI

Full command needs to be provided (hide credentials)
docker run ... bubuntux/nordlynx

To Reproduce using docker-compose

docker-compose.yml if used (hide credentials)

version: '3'
services:
  nordvpnlynx:
      image: ghcr.io/bubuntux/nordlynx:latest
      container_name: "nordvpnlynx"
      network_mode: bridge
      restart: always
      ports:
        - 8990:17442/tcp
        - 8991:8081/tcp
        - 8410:8000/tcp  
        - 8420:7227/tcp
        - 8421:7228/tcp
        - 8430:9666/tcp
        - 8080:8080/tcp      
        - 1080:1080/tcp
        - 1080:1080/udp      
      cap_add:
        - NET_ADMIN
        - SYS_MODULE
      environment:
        - PRIVATE_KEY=myPrivateKey
        - PERSISTENT_KEEP_ALIVE=25
        - NET_LOCAL=192.168.10.0/24
        - QUERY=filters\[country_id\]=153
        - DNS=192.168.10.2
        - TZ=Europe/Berlin
      volumes:
        - /etc/localtime:/etc/localtime:ro
        - /lib/modules:/lib/modules:ro
        - temp:/tmp
        - scripts:/var/local/scripts
      sysctls:
        - net.ipv6.conf.all.disable_ipv6=1
      logging:
        driver: "fluentd"
        options:
          fluentd-address: ${FLUENTD_ADDRESS}
          tag: ${FLUENTD_TAG}

Expected behavior

Once docker container is started up and health state shows "healthy" then container should not get in degraded state after some time.

Logs

In logs I can only see normal logs, even the interruption happed. The last line in "unhealthy" state is:
[2025-01-22T13:10:30+01:00] Connected! (ᵔᵕᵔ)/

Additional context

Using docker image "sha256:36e1abca987d315770c9703d40e90a6eee3e73e4e06a2c076870a381ec93c7d3". Debian 12. Kernel Linux 6.1.0-28-amd64.

[GinoBlij]

I used the same container and still used it in 2024, but since the end of 2024 or the beginning of 2025, it has completely died for some reason.

[mateus-werneck]

Same problem here.

Logs says the container is connected but not connection.

[mateus-werneck]

Container logs for reference

[2025-02-04T10:43:26+00:00] Connecting...
[#]
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.5.0.2/32 dev wg0
RTNETLINK answers: Network unreachable
[#] ip link set mtu 1420 up dev wg0
[#] resolvconf -a wg0 -m 0 -x
[#] wg set wg0 fwmark 51820
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820
[#] ip -4 rule add not fwmark 51820 table 51820
[#] ip -4 rule add table main suppress_prefixlength 0
[#] iptables-restore -n
[#]
[2025-02-04T10:43:27+00:00] Connected! (ᵔᵕᵔ)/