Bug: Windscribe suddenly stopped working after months of working fine?

[crispybegs]

Is this urgent?

No

Host OS

Ubuntu

CPU arch

x86_64

VPN service provider

Windscribe

What are you using to run the container

docker-compose

What is the version of Gluetun

gluetun:v3 image (f72b6f64c077)

What's the problem 🤔

I just noticed in my homepage that my gluetun container running windscribe has stopped and it refuses to restart.

Share your logs (at least 10 lines)

|   ├── Process UID: 1000
|   └── Process GID: 1000
├── Public IP settings:
|   ├── Fetching: every 12h0m0s
|   ├── IP file path: /tmp/gluetun/ip
|   └── Public IP data API: ipinfo
└── Version settings:
    └── Enabled: yes
2024-05-28T17:04:07Z INFO [routing] default route found: interface eth0, gateway xxx.xx.x.x, assigned IP xxx.xx.x.x and family v4
2024-05-28T17:04:07Z INFO [routing] adding route for 0.0.0.0/0
2024-05-28T17:04:07Z INFO [firewall] setting allowed subnets...
2024-05-28T17:04:07Z INFO [routing] default route found: interface eth0, gateway xxx.xx.x.x, assigned IP xxx.xx.x.x and family v4
2024-05-28T17:04:07Z INFO [dns] using plaintext DNS at address 1.1.1.1
2024-05-28T17:04:07Z INFO [http server] http server listening on [::]:8000
2024-05-28T17:04:07Z INFO [healthcheck] listening on 127.0.0.1:9999
2024-05-28T17:04:07Z INFO [firewall] allowing VPN connection...
2024-05-28T17:04:07Z INFO [wireguard] Using available kernelspace implementation
2024-05-28T17:04:07Z INFO [wireguard] Connecting to xx.xxx.xxx.xx:1194
2024-05-28T17:04:07Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
2024-05-28T17:04:07Z INFO [dns] downloading DNS over TLS cryptographic files
2024-05-28T17:04:15Z INFO [healthcheck] program has been unhealthy for 6s: restarting VPN
2024-05-28T17:04:15Z INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-28T17:04:15Z INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-28T17:04:15Z INFO [vpn] stopping
2024-05-28T17:04:15Z ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/releases": context canceled
2024-05-28T17:04:15Z ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 1.1.1.1:53: write udp xx.xxx.xxx.xx:57519->1.1.1.1:53: write: operation not permitted - retrying in 5s
2024-05-28T17:04:15Z INFO [vpn] starting
2024-05-28T17:04:15Z INFO [firewall] allowing VPN connection...
2024-05-28T17:04:15Z INFO [wireguard] Using available kernelspace implementation
2024-05-28T17:04:15Z INFO [wireguard] Connecting to xx.xxx.xxx.xx:1194
2024-05-28T17:04:16Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
2024-05-28T17:04:17Z WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": dial tcp: lookup www.internic.net on 1.1.1.1:53: read udp xx.xxx.xxx.xx:38397->1.1.1.1:53: i/o timeout
2024-05-28T17:04:17Z INFO [dns] attempting restart in 10s
2024-05-28T17:04:27Z INFO [healthcheck] program has been unhealthy for 11s: restarting VPN
2024-05-28T17:04:27Z INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-28T17:04:27Z INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-28T17:04:27Z INFO [vpn] stopping
2024-05-28T17:04:27Z INFO [vpn] starting
2024-05-28T17:04:27Z INFO [firewall] allowing VPN connection...
2024-05-28T17:04:27Z INFO [wireguard] Using available kernelspace implementation
2024-05-28T17:04:27Z INFO [wireguard] Connecting to xx.xxx.xxx.xx:1194
2024-05-28T17:04:27Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
2024-05-28T17:04:27Z INFO [dns] downloading DNS over TLS cryptographic files
2024-05-28T17:04:30Z ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 1.1.1.1:53: read udp xx.xxx.xxx.xx9:42385->1.1.1.1:53: i/o timeout - retrying in 10s
2024-05-28T17:04:37Z WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": dial tcp: lookup www.internic.net on 1.1.1.1:53: read udp 100.86.120.209:42978->1.1.1.1:53: i/o timeout
2024-05-28T17:04:37Z INFO [dns] attempting restart in 20s
2024-05-28T17:04:43Z INFO [healthcheck] program has been unhealthy for 16s: restarting VPN
2024-05-28T17:04:43Z INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-28T17:04:43Z INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-28T17:04:43Z INFO [vpn] stopping
2024-05-28T17:04:43Z INFO [vpn] starting
2024-05-28T17:04:43Z INFO [firewall] allowing VPN connection...
2024-05-28T17:04:43Z INFO [wireguard] Using available kernelspace implementation
2024-05-28T17:04:43Z INFO [wireguard] Connecting to xx.xxx.xxx.xx:1194
2024-05-28T17:04:43Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
2024-05-28T17:04:50Z ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 1.1.1.1:53: read udp xx.xxx.xxx.xx:34224->1.1.1.1:53: i/o timeout - retrying in 20s
2024-05-28T17:04:57Z INFO [dns] downloading DNS over TLS cryptographic files
2024-05-28T17:05:06Z INFO [healthcheck] program has been unhealthy for 21s: restarting VPN
2024-05-28T17:05:06Z INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-28T17:05:06Z INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-28T17:05:06Z INFO [vpn] stopping
2024-05-28T17:05:06Z INFO [vpn] starting
2024-05-28T17:05:06Z INFO [firewall] allowing VPN connection...
2024-05-28T17:05:06Z INFO [wireguard] Using available kernelspace implementation
2024-05-28T17:05:06Z INFO [wireguard] Connecting to xx.xxx.xxx.xx:1194
2024-05-28T17:05:06Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.

Share your configuration

services:
  gluetun:
    image: qmcgaw/gluetun:v3
    container_name: gluetun
    restart: always
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    volumes:
      - /home/crispy/docker/gluetun2/config:/config
    ports:
     # - "8082:8080" # qbittorrent WebUI
      - "8009:8000/tcp"
      - "6081:6881"
      - "6081:6881/udp"
      - "6011:6011"
      
    environment:
      # Wireguard
      VPN_SERVICE_PROVIDER: windscribe
      VPN_TYPE: wireguard
      WIREGUARD_PRIVATE_KEY: xxxx_redacted_xxx=
      WIREGUARD_ADDRESSES: xxx.xx.xx.xxx/32
      WIREGUARD_PRESHARED_KEY: xxxx_redacted_xxx=
      SERVER_REGIONS: France
      SERVER_CITIES: Paris

[github-actions]

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

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[qdm12]

See

2024-05-28T17:05:06Z INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-28T17:05:06Z INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION

[HaWaKv78]

I have exactly the same issue SERVER_REGIONS: Belgium, tried seting up a new container with the exact same setup but region France and that worked without an issue, so this seems to be a Windscribe issue but no idea what might be wrong.

[qdm12]

@HaWaKv78 Have you tried updating your servers data?

[HaWaKv78]

I've deleted my old credentials and created new ones for both Belgium and France and still the same, Belgium doesn't work and France does.

[qdm12]

Have you tried updating your servers data?

[HaWaKv78]

Sorry, misread your question, I updated the server list from the command line and this fixed the issue, thanks a lot for getting me on the right path and also for your time developing gluetun!