search

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.
https://hub.docker.com/r/qmcgaw/gluetun
MIT License
7.53k stars 355 forks source link

Bug: can't update Surfshark server #1504

Closed vip-design closed 1 year ago

vip-design commented 1 year ago

Is this urgent?

Yes

Host OS

Ubuntu

CPU arch

x86_64

VPN service provider

Surfshark

What are you using to run the container

docker-compose

What is the version of Gluetun

lastest

What's the problem 🤔

I'm getting this error: ERROR updating server information: getting servers: not enough servers found: 0 and expected at least 268.

Since it is 0 here, I'm not sure how to move ahead.

I did docker pull qmcgaw/gluetun:latest before updating.

Share your logs

After running docker run -it --rm -v /var/lib/docker/volumes/server:/gluetun qmcgaw/gluetun update -enduser -providers surfshark, I got:

(base) root@ubuntu:~# docker run -it --rm -v /var/lib/docker/volumes/server:/gluetun qmcgaw/gluetun update -enduser -providers surfshark
2023-04-04T01:20:29Z INFO merging by most recent 13064 hardcoded servers and 13064 servers read from /gluetun/servers.json
2023-04-04T01:20:29Z INFO updating Surfshark servers...
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving us-kan.prod.surfshark.com: lookup us-kan.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving kz-ura.prod.surfshark.com: lookup kz-ura.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving dz-alg.prod.surfshark.com: lookup dz-alg.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving sg-sng-st008.prod.surfshark.com: lookup sg-sng-st008.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving uk-lon-mp001.prod.surfshark.com: lookup uk-lon-mp001.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving pt-lis.prod.surfshark.com: lookup pt-lis.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving gl-goh.prod.surfshark.com: lookup gl-goh.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving us-nl.prod.surfshark.com: lookup us-nl.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving us-nyc-st005.prod.surfshark.com: lookup us-nyc-st005.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving za-jnb.prod.surfshark.com: lookup za-jnb.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving sg-in.prod.surfshark.com: lookup sg-in.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving es-vlc.prod.surfshark.com: lookup es-vlc.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving de-fra-mp001.prod.surfshark.com: lookup de-fra-mp001.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving sg-nl.prod.surfshark.com: lookup sg-nl.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving es-mad.prod.surfshark.com: lookup es-mad.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving uk-de.prod.surfshark.com: lookup uk-de.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving eg-cai.prod.surfshark.com: lookup eg-cai.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving uk-fr.prod.surfshark.com: lookup uk-fr.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving jp-tok-st017.prod.surfshark.com: lookup jp-tok-st017.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving au-syd.prod.surfshark.com: lookup au-syd.prod.surfshark.com: i/o timeout
2023-04-04T01:20:51Z ERROR updating server information: getting servers: not enough servers found: 0 and expected at least 268
2023-04-04T01:20:51Z INFO Shutdown successful

Share your configuration

version: "3"
services:
  'xxx':
    image: qmcgaw/gluetun
    volumes:
      - /var/lib/docker/volumes/server:/gluetun
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_SERVICE_PROVIDER=surfshark
      - VPN_TYPE=wireguard
      - WIREGUARD_PUBLIC_KEY=xxx
      - WIREGUARD_PRIVATE_KEY=xxx
      - WIREGUARD_ADDRESSES=xxx
      - SERVER_COUNTRIES=Singapore
      - UPDATER_PERIOD=24h
      - SHADOWSOCKS=on
      - SHADOWSOCKS_PASSWORD=dd
    ports:
      - 3257:8388/tcp # Shadowsocks
      - 3257:8388/udp # Shadowsocks
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=1
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped
qdm12 commented 1 year ago

I get:

2023-04-20T23:18:57Z INFO merging by most recent 13063 hardcoded servers and 13063 servers read from /gluetun/servers.json
2023-04-20T23:18:57Z INFO updating Surfshark servers...
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ca-us.prod.surfshark.com: lookup ca-us.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving sg-hk.prod.surfshark.com: lookup sg-hk.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving uk-de.prod.surfshark.com: lookup uk-de.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving us-nl.prod.surfshark.com: lookup us-nl.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving sg-nl.prod.surfshark.com: lookup sg-nl.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving uk-fr.prod.surfshark.com: lookup uk-fr.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving de-sg.prod.surfshark.com: lookup de-sg.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving nl-us.prod.surfshark.com: lookup nl-us.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving fr-se.prod.surfshark.com: lookup fr-se.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving au-us.prod.surfshark.com: lookup au-us.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving us-pt.prod.surfshark.com: lookup us-pt.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving de-uk.prod.surfshark.com: lookup de-uk.prod.surfshark.com on 127.0.0.11:53: no such host
2023-04-20T23:19:07Z ERROR updating server information: getting servers: not enough servers found: 188 and expected at least 268
2023-04-20T23:19:07Z INFO Shutdown successful

Which you can go around by using -minratio 0.5. I'm not sure why you get 0 server that's odd.

Anyway, I pushed 804ea7ebd66be152cd478cf1d6a2a533eea1a3c1 which updates all servers data and also removes the few now-dead hostnames such as de-uk.prod.surfshark.com