qdm12 / gluetun

VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.

Home Page:https://hub.docker.com/r/qmcgaw/gluetun

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Bug: Healthcheck shows heaslthy even tho portforwardin is enabled and refused by the server.

christianmerges opened this issue · comments

Is this urgent?

No

Host OS

Ubuntu 24.04

CPU arch

x86_64

VPN service provider

ProtonVPN

What are you using to run the container

docker-compose

What is the version of Gluetun

Running version latest built on 2024-06-17T22:37:52.988Z (commit 93ed87d)

What's the problem 🤔

Health check is not checking if poftfording is not working when it is enabled.

Share your logs (at least 10 lines)

It seems that the Serverlist is outdated. There is another update regarding to this. To workaround this, I always have to restart the container, till i have randomly a server chosen, which is serving the port forwarding feature.

Share your configuration

version: '3.8'
services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_SERVICE_PROVIDER=protonvpn
      - OPENVPN_USER=+nr+f2+pmp
      - OPENVPN_PASSWORD=
      - SERVER_COUNTRIES=Germany
      - VPN_PORT_FORWARDING=on
      - VPN_PORT_FORWARDING_PROVIDER=protonvpn
      - SERVER_CITIES=Frankfurt

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

Health check is not checking if poftfording is not working when it is enabled.

Not sure what you meant there. Please create a clearer issue with more details/logs.

It seems that the Serverlist is outdated.

See https://github.com/qdm12/gluetun-wiki/blob/main/setup/servers.md#update-the-vpn-servers-list

Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.