Issues Using a Specific WireGuard Endpoint with ProtonVPN

[loeloe03]

I am trying to configure Gluetun to use ProtonVPN with WireGuard and assign Explicit endpoint to the container. However, every time I try to set a specific server or force a static IP, I encounter the following error:

2025-11-24T20:29:23+01:00 INFO [storage] merging by most recent 19476 hardcoded servers and 19476 servers read from /gluetun/servers.json
2025-11-24T20:29:23+01:00 ERROR VPN settings: provider settings: server selection: Wireguard server selection settings: endpoint IP is not set
2025-11-24T20:29:23+01:00 INFO Shutdown successful

I have tried many approaches, including different Docker image versions, mounting the configuration directory and not mounting it, but nothing works. However letting gluetun dynamicly choose a server does work for me, but this is not preferred.

The following configuration does work, meaning Gluetun can connect, but it does not allow me to use a static endpoint, which is what I need:

version: "3.9"
services:
gluetun:
image: qmcgaw/gluetun:v3.39.0
container_name: gluetun
cap_add:

• NET_ADMIN
  devices:
• /dev/net/tun
  volumes:
• /home/loeloe/docker/wireguard-qbit/gluetun-config:/gluetun
• /home/loeloe/docker/wireguard-qbit/gluetun-tmp:/tmp/gluetun
• /home/loeloe/docker/qbit-downloads:/downloads
  environment:
  VPN_SERVICE_PROVIDER: protonvpn
  VPN_TYPE: wireguard
  WIREGUARD_PRIVATE_KEY: "*****"
  WIREGUARD_ADDRESSES: "10.2.0.2/32"
  WIREGUARD_PUBLIC_KEY: "afmlPt2O8Y+u4ykaOpMoO6q1JkbArZsaoFcpNXudXCg="
  WIREGUARD_ENDPOINT: "46.29.25.3:51820"
  WIREGUARD_ALLOWED_IPS: "0.0.0.0/0,::/0"
  VPN_PORT_FORWARDING: "on"
  FIREWALL: "on"
  TZ: "Europe/Amsterdam"
  HTTP_CONTROL_SERVER_ADDRESS: "0.0.0.0:8000"
  ports:
• "8000:8000"
• "6881:6881"
• "6881:6881/udp"
• "8989:8989"
• "9696:9696"
• "7878:7878"
• "8080:8080"
  restart: unless-stopped

Thank you for your help!

[ashleyross]

Is WIREGUARD_ENDPOINT a valid environment variable?

The gluetun wiki currently documentsWIREGUARD_ENDPOINT_IP and WIREGUARD_ENDPOINT_PORT, but no WIREGUARD_ENDPOINT.

[Prev-I]

I've stumbled on a similar problem recently on gluetun v3.41.1.

Trying to force a specific server, when creating a conf file from protonVPN website I've got this 2 situation:

If I use the wireguard conf file directly, with this variables, network is OK but I could not use port forward:

VPN_TYPE=wireguard
VPN_SERVICE_PROVIDER=custom
------ in compose.yaml
volumes:
- /opt/gluetun/wireguard/wg0.conf:/gluetun/wireguard/wg0.conf:ro

That is expected, as custom provider don't support port forward.
If I use this configuration, the tunnel is opened, the port forward activated but network dont work:

VPN_TYPE=wireguard
VPN_SERVICE_PROVIDER=protonvpn
VPN_PORT_FORWARDING=on
VPN_PORT_FORWARD_ONLY=on
WIREGUARD_PRIVATE_KEY=XXXXX
WIREGUARD_ENDPOINT_IP=NN.NN.NN.NN
WIREGUARD_ADDRESSES=NN.NN.NN.NN/32

If I try to set the WIREGUARD_ENDPOINT_PORT variable, with the content of protonVPN conf file, gluetun does not start.

So right now I'm bounded to use custom wireguard provider with conf file. I would be nice to use proton provider with proton generated configuration.