Feature request: support for Windscribe Static IP Port Forwarding over Wireguard

[tobsynl]

What's the feature 🧐

Hi there,

I have a Windscribe plan with a Static IP with Permanent Port Forwarding. Following instructions in the Gluetun Wiki, I have a working Gluetun container with qBittorrent (yay!). I have added the forwarded port I created in the Windscribe portal to FIREWALL_VPN_INPUT_PORTS. Unfortunately though, the port is still closed. I have been able to get it to work by using one of their regular servers, but the Static IP seems to cause trouble. Any chance to get support for this?

Cheers, Tobsy

Extra information and references

version: "3.5"
services:
  gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    network_mode: bridge
    ports:
      - 8085:8085
    volumes:
      - /volume1/docker/gluetun:/tmp/gluetun
    environment:
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard
      - VPN_ENDPOINT_IP=redacted
      - VPN_ENDPOINT_PORT=redacted
      - WIREGUARD_PUBLIC_KEY=redacted
      - WIREGUARD_PRIVATE_KEY=redacted      
      - WIREGUARD_PRESHARED_KEY=redacted
      - WIREGUARD_ADDRESSES=redacted
      - FIREWALL_VPN_INPUT_PORTS=redacted
    restart: always

  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent
    container_name: qbittorrentvpn
    network_mode: "service:gluetun"
    environment:
      - PUID=1026
      - PGID=100
      - TZ=Europe/Amsterdam
      - WEBUI_PORT=8085
    volumes:
      - '/volume1/docker/qbittorrentvpn:/config'
      - '/volume1/docker/Downloads:/downloads'
    depends_on:
      - gluetun
    restart: always

[qdm12]

Sorry I cannot help in this case, reach out to Windscribe about this? If the Wireguard connection is working, and FIREWALL_VPN_INPUT_PORTS is set, then it's allowed in the firewall of Gluetun and that's it. The rest is up to the Windscribe wireguard server to properly port forward.

[github-actions[bot]]

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.