Open casudo opened 10 months ago
EDIT: Every other IP on the 10.2.0.0/16 can successfully ping cloudflare.com / make requests to the internet
Update: Without doing anything, the problem fixed itself. I've went offline and when I came back I've found this in the logs:
2024-01-06T22:02:19+01:00 WARN [openvpn] TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
๐๐๐๐๐๐จ๐จ๐จ๐จ๐จ๐จ๐๐๐๐๐
That error usually happens because either:
1. The VPN server IP address you are trying to connect to is no longer valid ๐
Check out https://github.com/qdm12/gluetun-wiki/blob/main/setup/servers.md#update-the-vpn-servers-list
2. The VPN server crashed ๐ฅ, try changing your VPN servers filtering options such as SERVER_REGIONS
3. Your Internet connection is not working ๐คฏ, ensure it works
4. Something else โก๏ธ https://github.com/qdm12/gluetun/issues/new/choose
2024-01-06T22:02:19+01:00 INFO [openvpn] TLS Error: TLS handshake failed
2024-01-06T22:02:19+01:00 INFO [openvpn] SIGTERM received, sending exit notification to peer
2024-01-06T22:02:19+01:00 INFO [openvpn] SIGTERM[soft,tls-error] received, process exiting
2024-01-06T22:02:19+01:00 INFO [vpn] retrying in 15s
2024-01-06T22:02:34+01:00 INFO [firewall] allowing VPN connection...
2024-01-06T22:02:34+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-06T22:02:34+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-06T22:02:34+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.109.154:443
2024-01-06T22:02:34+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-06T22:02:34+01:00 INFO [openvpn] UDP link remote: [AF_INET]216.131.109.154:443
2024-01-06T22:02:34+01:00 WARN [openvpn] 'link-mtu' is used inconsistently, local='link-mtu 1569', remote='link-mtu 1570'
2024-01-06T22:02:34+01:00 WARN [openvpn] 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
2024-01-06T22:02:34+01:00 INFO [openvpn] [prg-c19.ipvanish.com] Peer Connection Initiated with [AF_INET]216.131.109.154:443
2024-01-06T22:02:34+01:00 INFO [openvpn] TUN/TAP device tun0 opened
2024-01-06T22:02:34+01:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2024-01-06T22:02:34+01:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2024-01-06T22:02:34+01:00 INFO [openvpn] /sbin/ip addr add dev tun0 172.21.21.28/23
2024-01-06T22:02:34+01:00 INFO [openvpn] UID set to nonrootuser
2024-01-06T22:02:34+01:00 INFO [openvpn] Initialization Sequence Completed
2024-01-06T22:02:34+01:00 INFO [dns] downloading DNS over TLS cryptographic files
2024-01-06T22:02:35+01:00 INFO [healthcheck] healthy!
2024-01-06T22:02:37+01:00 INFO [dns] downloading hostnames and IP block lists
2024-01-06T22:02:40+01:00 INFO [dns] init module 0: validator
2024-01-06T22:02:40+01:00 INFO [dns] init module 1: iterator
2024-01-06T22:02:40+01:00 INFO [dns] start of service (unbound 1.17.1).
2024-01-06T22:02:40+01:00 INFO [dns] generate keytag query _ta-4a5c-4f66. NULL IN
2024-01-06T22:02:41+01:00 INFO [dns] ready
2024-01-06T22:02:41+01:00 INFO [vpn] You are running on the bleeding edge of latest!
2024-01-06T22:02:41+01:00 INFO [ip getter] Public IP address is 216.131.109.156 (Czech Republic, Prague, Prague)
2024-01-06T22:44:57+01:00 INFO [http server] 200 GET /ip wrote 266B to 10.2.255.254:45262 in 29.614ยตs
Reopening this since it worked for 3h, then it disconnected again with the same TLS error message. :(
I am having the same issue with IPVanish.
Local IPVanish app can connect and gives me an IP address, but I've lost Gluetun connection. This is in a Synology Docker
This is a log of when it was working (2 days ago)
2024-01-05 18:14:03 stdout 2024-01-05T19:14:03+01:00 INFO [dns] downloading hostnames and IP block lists
2024-01-05 18:14:02 stdout 2024-01-05T19:14:02+01:00 INFO [healthcheck] healthy!
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [dns] downloading DNS over TLS cryptographic files
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [openvpn] Initialization Sequence Completed
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [openvpn] UID set to nonrootuser
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [openvpn] /sbin/ip addr add dev tun0 172.21.23.116/23
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [openvpn] TUN/TAP device tun0 opened
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 INFO [openvpn] [ams-c06.ipvanish.com] Peer Connection Initiated with [AF_INET]216.131.112.32:443
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 WARN [openvpn] 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
2024-01-05 18:14:01 stdout 2024-01-05T19:14:01+01:00 WARN [openvpn] 'link-mtu' is used inconsistently, local='link-mtu 1569', remote='link-mtu 1570'
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [openvpn] UDP link remote: [AF_INET]216.131.112.32:443
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.112.32:443
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [firewall] allowing VPN connection...
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [vpn] starting
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [vpn] stopping
2024-01-05 18:14:00 stdout 2024-01-05T19:14:00+01:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [openvpn] UDP link remote: [AF_INET]37.120.218.101:443
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.218.101:443
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [firewall] allowing VPN connection...
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [healthcheck] listening on 127.0.0.1:9999
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [http server] http server listening on [::]:8000
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [dns] using plaintext DNS at address 1.1.1.1
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [routing] adding route for 192.168.0.0/24
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [routing] adding route for 172.17.0.0/16
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [routing] default route found: interface eth0, gateway 172.17.0.1, assigned IP 172.17.0.5 and family v4
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [firewall] setting allowed subnets...
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [routing] adding route for 0.0.0.0/0
2024-01-05 18:13:54 stdout 2024-01-05T19:13:54+01:00 INFO [routing] default route found: interface eth0, gateway 172.17.0.1, assigned IP 172.17.0.5 and family v4
2024-01-05 18:13:54 stdout +-- Enabled: yes
2024-01-05 18:13:54 stdout +-- Version settings:
2024-01-05 18:13:54 stdout | +-- IP file path: /tmp/gluetun/ip
2024-01-05 18:13:54 stdout | +-- Fetching: every 12h0m0s
2024-01-05 18:13:54 stdout +-- Public IP settings:
2024-01-05 18:13:54 stdout | +-- Timezone: europe/amsterdam
2024-01-05 18:13:54 stdout | +-- Process GID: 100
2024-01-05 18:13:54 stdout | +-- Process UID: 1026
2024-01-05 18:13:54 stdout +-- OS Alpine settings:
2024-01-05 18:13:54 stdout | +-- Logging: yes
2024-01-05 18:13:54 stdout | +-- Listening address: :8000
2024-01-05 18:13:54 stdout +-- Control server settings:
2024-01-05 18:13:54 stdout | +-- Enabled: no
2024-01-05 18:13:54 stdout +-- HTTP proxy settings:
2024-01-05 18:13:54 stdout | +-- Enabled: no
2024-01-05 18:13:54 stdout +-- Shadowsocks server settings:
2024-01-05 18:13:54 stdout | +-- Additional duration: 5s
2024-01-05 18:13:54 stdout | +-- Initial duration: 6s
2024-01-05 18:13:54 stdout | +-- VPN wait durations:
2024-01-05 18:13:54 stdout | +-- Read timeout: 500ms
2024-01-05 18:13:54 stdout | +-- Read header timeout: 100ms
2024-01-05 18:13:54 stdout | +-- Duration to wait after success: 5s
2024-01-05 18:13:54 stdout | +-- Target address: cloudflare.com:443
2024-01-05 18:13:54 stdout | +-- Server listening address: 127.0.0.1:9999
2024-01-05 18:13:54 stdout +-- Health settings:
2024-01-05 18:13:54 stdout | +-- Log level: INFO
2024-01-05 18:13:54 stdout +-- Log settings:
2024-01-05 18:13:54 stdout | +-- 192.168.0.0/24
2024-01-05 18:13:54 stdout | +-- 172.17.0.0/16
2024-01-05 18:13:54 stdout | +-- Outbound subnets:
2024-01-05 18:13:54 stdout | +-- Enabled: yes
2024-01-05 18:13:54 stdout +-- Firewall settings:
2024-01-05 18:13:54 stdout | +-- ::ffff:192.168.0.0/112
2024-01-05 18:13:54 stdout | +-- ::ffff:172.16.0.0/108
2024-01-05 18:13:54 stdout | +-- ::ffff:169.254.0.0/112
2024-01-05 18:13:54 stdout | +-- ::ffff:10.0.0.0/104
2024-01-05 18:13:54 stdout | +-- ::ffff:127.0.0.1/104
2024-01-05 18:13:54 stdout | +-- fe80::/10
2024-01-05 18:13:54 stdout | +-- fc00::/7
2024-01-05 18:13:54 stdout | +-- ::1/128
2024-01-05 18:13:54 stdout | +-- 169.254.0.0/16
2024-01-05 18:13:54 stdout | +-- 192.168.0.0/16
2024-01-05 18:13:54 stdout | +-- 172.16.0.0/12
2024-01-05 18:13:54 stdout | +-- 10.0.0.0/8
2024-01-05 18:13:54 stdout | +-- 127.0.0.1/8
2024-01-05 18:13:54 stdout | +-- Blocked IP networks:
2024-01-05 18:13:54 stdout | +-- Block surveillance: no
2024-01-05 18:13:54 stdout | +-- Block ads: no
2024-01-05 18:13:54 stdout | +-- Block malicious: yes
2024-01-05 18:13:54 stdout | +-- DNS filtering settings:
2024-01-05 18:13:54 stdout | | +-- ::/0
2024-01-05 18:13:54 stdout | | +-- 0.0.0.0/0
2024-01-05 18:13:54 stdout | | +-- Allowed networks:
2024-01-05 18:13:54 stdout | | +-- System user: root
2024-01-05 18:13:54 stdout | | +-- Validation log level: 0
2024-01-05 18:13:54 stdout | | +-- Verbosity details level: 0
2024-01-05 18:13:54 stdout | | +-- Verbosity level: 1
2024-01-05 18:13:54 stdout | | +-- IPv6: no
2024-01-05 18:13:54 stdout | | +-- Caching: yes
2024-01-05 18:13:54 stdout | | | +-- cloudflare
2024-01-05 18:13:54 stdout | | +-- Authoritative servers:
2024-01-05 18:13:54 stdout | +-- Unbound settings:
2024-01-05 18:13:54 stdout | +-- Update period: every 24h0m0s
2024-01-05 18:13:54 stdout | +-- Enabled: yes
2024-01-05 18:13:54 stdout | +-- DNS over TLS settings:
2024-01-05 18:13:54 stdout | +-- DNS server address to use: 127.0.0.1
2024-01-05 18:13:54 stdout | +-- Keep existing nameserver(s): no
2024-01-05 18:13:54 stdout +-- DNS settings:
2024-01-05 18:13:54 stdout | +-- Verbosity level: 1
2024-01-05 18:13:54 stdout | +-- Run OpenVPN as: root
2024-01-05 18:13:54 stdout | +-- Network interface: tun0
2024-01-05 18:13:54 stdout | +-- Password: [set]
2024-01-05 18:13:54 stdout | +-- User: [set]
2024-01-05 18:13:54 stdout | +-- OpenVPN version: 2.5
2024-01-05 18:13:54 stdout | +-- OpenVPN settings:
2024-01-05 18:13:54 stdout | | +-- Protocol: UDP
2024-01-05 18:13:54 stdout | | +-- OpenVPN server selection settings:
2024-01-05 18:13:54 stdout | | +-- Countries: netherlands, belgium
2024-01-05 18:13:54 stdout | | +-- VPN type: openvpn
2024-01-05 18:13:54 stdout | | +-- Server selection settings:
2024-01-05 18:13:54 stdout | | +-- Name: ipvanish
2024-01-05 18:13:54 stdout | +-- VPN provider settings:
2024-01-05 18:13:54 stdout +-- VPN settings:
And this is what is showing up currently
2024-01-07 19:08:17 stdout 2024-01-07T20:08:17+01:00 INFO [healthcheck] program has been unhealthy for 26s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [openvpn] UDP link remote: [AF_INET]216.131.112.44:443
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.112.44:443
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [firewall] allowing VPN connection...
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [vpn] starting
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [vpn] stopping
2024-01-07 19:07:51 stdout 2024-01-07T20:07:51+01:00 INFO [healthcheck] program has been unhealthy for 21s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [openvpn] UDP link remote: [AF_INET]216.131.88.75:443
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.88.75:443
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [firewall] allowing VPN connection...
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [vpn] starting
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [vpn] stopping
2024-01-07 19:07:29 stdout 2024-01-07T20:07:29+01:00 INFO [healthcheck] program has been unhealthy for 16s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [openvpn] UDP link remote: [AF_INET]37.120.218.81:443
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.218.81:443
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [firewall] allowing VPN connection...
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [vpn] starting
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [vpn] stopping
2024-01-07 19:07:13 stdout 2024-01-07T20:07:13+01:00 INFO [healthcheck] program has been unhealthy for 11s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [openvpn] UDP link remote: [AF_INET]216.131.88.230:443
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.88.230:443
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [firewall] allowing VPN connection...
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [vpn] starting
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [vpn] stopping
2024-01-07 19:07:02 stdout 2024-01-07T20:07:02+01:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [openvpn] UDP link remote: [AF_INET]37.120.218.74:443
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [openvpn] UDP link local: (not bound)
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.218.74:443
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 2 2022
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [firewall] allowing VPN connection...
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [healthcheck] listening on 127.0.0.1:9999
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [http server] http server listening on [::]:8000
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [dns] using plaintext DNS at address 1.1.1.1
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [routing] adding route for 192.168.0.0/24
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [routing] adding route for 172.17.0.0/16
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [routing] default route found: interface eth0, gateway 172.17.0.1, assigned IP 172.17.0.2 and family v4
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [firewall] setting allowed subnets...
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [routing] adding route for 0.0.0.0/0
2024-01-07 19:06:56 stdout 2024-01-07T20:06:56+01:00 INFO [routing] default route found: interface eth0, gateway 172.17.0.1, assigned IP 172.17.0.2 and family v4
2024-01-07 19:06:56 stdout +-- Enabled: yes
2024-01-07 19:06:56 stdout +-- Version settings:
2024-01-07 19:06:56 stdout | +-- IP file path: /tmp/gluetun/ip
2024-01-07 19:06:56 stdout | +-- Fetching: every 12h0m0s
2024-01-07 19:06:56 stdout +-- Public IP settings:
2024-01-07 19:06:56 stdout | +-- Timezone: europe/amsterdam
2024-01-07 19:06:56 stdout | +-- Process GID: 100
2024-01-07 19:06:56 stdout | +-- Process UID: 1026
2024-01-07 19:06:56 stdout +-- OS Alpine settings:
2024-01-07 19:06:56 stdout | +-- Logging: yes
2024-01-07 19:06:56 stdout | +-- Listening address: :8000
2024-01-07 19:06:56 stdout +-- Control server settings:
2024-01-07 19:06:56 stdout | +-- Enabled: no
2024-01-07 19:06:56 stdout +-- HTTP proxy settings:
2024-01-07 19:06:56 stdout | +-- Enabled: no
2024-01-07 19:06:56 stdout +-- Shadowsocks server settings:
2024-01-07 19:06:56 stdout | +-- Additional duration: 5s
2024-01-07 19:06:56 stdout | +-- Initial duration: 6s
2024-01-07 19:06:56 stdout | +-- VPN wait durations:
2024-01-07 19:06:56 stdout | +-- Read timeout: 500ms
2024-01-07 19:06:56 stdout | +-- Read header timeout: 100ms
2024-01-07 19:06:56 stdout | +-- Duration to wait after success: 5s
2024-01-07 19:06:56 stdout | +-- Target address: cloudflare.com:443
2024-01-07 19:06:56 stdout | +-- Server listening address: 127.0.0.1:9999
2024-01-07 19:06:56 stdout +-- Health settings:
2024-01-07 19:06:56 stdout | +-- Log level: INFO
2024-01-07 19:06:56 stdout +-- Log settings:
2024-01-07 19:06:56 stdout | +-- 192.168.0.0/24
2024-01-07 19:06:56 stdout | +-- 172.17.0.0/16
2024-01-07 19:06:56 stdout | +-- Outbound subnets:
2024-01-07 19:06:56 stdout | +-- Enabled: yes
2024-01-07 19:06:56 stdout +-- Firewall settings:
2024-01-07 19:06:56 stdout | +-- ::ffff:192.168.0.0/112
2024-01-07 19:06:56 stdout | +-- ::ffff:172.16.0.0/108
2024-01-07 19:06:56 stdout | +-- ::ffff:169.254.0.0/112
2024-01-07 19:06:56 stdout | +-- ::ffff:10.0.0.0/104
2024-01-07 19:06:56 stdout | +-- ::ffff:127.0.0.1/104
2024-01-07 19:06:56 stdout | +-- fe80::/10
2024-01-07 19:06:56 stdout | +-- fc00::/7
2024-01-07 19:06:56 stdout | +-- ::1/128
2024-01-07 19:06:56 stdout | +-- 169.254.0.0/16
2024-01-07 19:06:56 stdout | +-- 192.168.0.0/16
2024-01-07 19:06:56 stdout | +-- 172.16.0.0/12
2024-01-07 19:06:56 stdout | +-- 10.0.0.0/8
2024-01-07 19:06:56 stdout | +-- 127.0.0.1/8
2024-01-07 19:06:56 stdout | +-- Blocked IP networks:
2024-01-07 19:06:56 stdout | +-- Block surveillance: no
2024-01-07 19:06:56 stdout | +-- Block ads: no
2024-01-07 19:06:56 stdout | +-- Block malicious: yes
2024-01-07 19:06:56 stdout | +-- DNS filtering settings:
2024-01-07 19:06:56 stdout | | +-- ::/0
2024-01-07 19:06:56 stdout | | +-- 0.0.0.0/0
2024-01-07 19:06:56 stdout | | +-- Allowed networks:
2024-01-07 19:06:56 stdout | | +-- System user: root
2024-01-07 19:06:56 stdout | | +-- Validation log level: 0
2024-01-07 19:06:56 stdout | | +-- Verbosity details level: 0
2024-01-07 19:06:56 stdout | | +-- Verbosity level: 1
2024-01-07 19:06:56 stdout | | +-- IPv6: no
2024-01-07 19:06:56 stdout | | +-- Caching: yes
2024-01-07 19:06:56 stdout | | | +-- cloudflare
2024-01-07 19:06:56 stdout | | +-- Authoritative servers:
2024-01-07 19:06:56 stdout | +-- Unbound settings:
2024-01-07 19:06:56 stdout | +-- Update period: every 24h0m0s
2024-01-07 19:06:56 stdout | +-- Enabled: yes
2024-01-07 19:06:56 stdout | +-- DNS over TLS settings:
2024-01-07 19:06:56 stdout | +-- DNS server address to use: 127.0.0.1
2024-01-07 19:06:56 stdout | +-- Keep existing nameserver(s): no
2024-01-07 19:06:56 stdout +-- DNS settings:
2024-01-07 19:06:56 stdout | +-- Verbosity level: 1
2024-01-07 19:06:56 stdout | +-- Run OpenVPN as: root
2024-01-07 19:06:56 stdout | +-- Network interface: tun0
2024-01-07 19:06:56 stdout | +-- Password: [set]
2024-01-07 19:06:56 stdout | +-- User: [set]
2024-01-07 19:06:56 stdout | +-- OpenVPN version: 2.5
2024-01-07 19:06:56 stdout | +-- OpenVPN settings:
2024-01-07 19:06:56 stdout | | +-- Protocol: UDP
2024-01-07 19:06:56 stdout | | +-- OpenVPN server selection settings:
2024-01-07 19:06:56 stdout | | +-- Countries: netherlands, belgium
2024-01-07 19:06:56 stdout | | +-- VPN type: openvpn
2024-01-07 19:06:56 stdout | | +-- Server selection settings:
2024-01-07 19:06:56 stdout | | +-- Name: ipvanish
2024-01-07 19:06:56 stdout | +-- VPN provider settings:
2024-01-07 19:06:56 stdout +-- VPN settings:
I have the same problem.
I also have been having the same issues for the past week-ish. I have tried using different server countries, cities, etc. all last maybe 2-4 hours then have constant connection issues. I'm not sure if this may be some issue with ISP's or IPvanish as during the same time that gluetun cannot connect to IPvanish, i try to load an IPvanish connection on my phone using their app and it's not able to establish a connection while on my home network. But If I switch to cellular connection, the IPvanish connection works. I'm using the openvpn protocol through gluetun and the wireguard protocol through the app on my phone, if that helps at all.
after first startup during the time it's not working: _gluetun_logs (1).txt
after it's been not working for a while: _gluetun_logs.txt
Hello, has anyone been able to find the problem? Do you know if we have any approximate time to solve it?
Hello, has anyone been able to find the problem? Do you know if we have any approximate time to solve it?
Haven't found the problem yet.
Hello, has anyone been able to find the problem? Do you know if we have any approximate time to solve it?
I also have not found a fix. Other than switching to a different vpn provider.
I switched to mullvad for the time being, but plan to try out airvpn or protonvpn to ensure port forwarding is an option, which mullvad does not support anymore.
I was trying with openvpn in a docker and it also fails and the log I get is:
Options error: Unrecognized option or missing or extra parameter(s) in ./ipvanish-BR-Sao-Paulo-gru-c01.ovpn:17: keysize (2.6.8)
Reviewing that file, notice that line key size
client
dev tun
proto udp
remote gru-c01.ipvanish.com 443
resolv-retry infinite
nobind
persist-key
persist-tun
persist-remote-ip
ca ca.ipvanish.com.crt
verify-x509-name gru-c01.ipvanish.com name
auth-user-pass
comp-lzo
verb 3
auth SHA256
cipher AES-256-CBC
keysize 256 <------------- Line
tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA:TLS-DHE-DSS-WITH-AES-256-CBC-SHA:TLS-RSA-WITH-AES-256-CBC-SHA
I just deleted it and ran it again and it worked correctly. I don't know the language in the project so I don't know how to apply the fix in a fork, but I'm attaching this comment in case you think it might be of some use.
Greetings
Another thing I noticed is that the host says this resource https://raw.githubusercontent.com/qdm12/gluetun/master/internal/storage/servers.json
does not correspond to the name of the files that contain this other resource: https://configs.ipvanish.com/configs/configs.zip
I don't know the language in the project so I don't know how to apply the fix in a fork
What fix though? ๐ค Gluetun generates openvpn configuration files, and keysize 256
isn't part of it (I remember it's windows only thing I think). All the values in the config file are part of the Gluetun config as well (didn't check if the ca.ipvanish.com.crt
matched though). The IP address of gru-c01.ipvanish.com didn't change either. Have you tried running Gluetun using SERVER_HOSTNAMES=gru-c01.ipvanish.com
to check if it works?
@qdm12
....but I'm attaching this comment in case you think it might be of some use.
For IPvanish I ended up using another image while this gluetun issue is resolved. However, I was surprised because the image consumes 10x less memory than gluetun, but that is another topic. Thank you in the same way.
@qdm12
....but I'm attaching this comment in case you think it might be of some use.
For IPvanish I ended up using another image while this gluetun issue is resolved. However, I was surprised because the image consumes 10x less memory than gluetun, but that is another topic. Thank you in the same way.
Which one are you using?
I have the same problem.
@qdm12 Is there any fix for this issue? The error still occures.
same issue, provider ipvanish, inconsistent patches of uptime, virtually identical logs.
same issue, provider ipvanish, inconsistent patches of uptime, virtually identical logs.
If it helps you, I've switched to NordVPN as provider and it works flawlessly. Couldn't fix it with IPVanish.
In case it helps, I have included my current logs -- I see only one difference with the previously posted logs (an error that seems inconsequential, deleting a non-existent iptables entry). Behavior is identical on 'v3' and 'latest'.
Other containers in the same stack have no issues with connectivity (except those that depend on gluetun, natch).
From a shell within the gluetun container, accessing local or remote addresses is blocked
docker exec -it gluetun sh
/ # ping 10.10.2.1
PING 10.10.2.1 (10.10.2.1): 56 data bytes
ping: sendto: Operation not permitted
/ # nslookup google.com
nslookup: write to '1.1.1.1': Operation not permitted
;; connection timed out; no servers could be reached
Attempting to update the server list likewise fails:
/ # ./gluetun-entrypoint update -enduser -providers ipvanish
2024-05-24T12:15:52-04:00 INFO merging by most recent 19425 hardcoded servers and 19759 servers read from /gluetun/servers.json
2024-05-24T12:15:52-04:00 INFO Using ipvanish servers from file which are 718 days more recent
2024-05-24T12:15:52-04:00 INFO updating Ipvanish servers...
2024-05-24T12:15:52-04:00 ERROR updating server information: getting servers: Get "https://configs.ipvanish.com/configs/configs.zip": dial tcp: lookup configs.ipvanish.com on 1.1.1.1:53: write udp 10.10.11.3:52782->1.1.1.1:53: write: operation not permitted
2024-05-24T12:15:52-04:00 INFO Shutdown successful
Spinning up the container with command: update -enduser -providers ipvanish
seems to work? No errors are logged, although the update runs in a continuous loop:
2024-05-24T12:28:14-04:00 INFO merging by most recent 19425 hardcoded servers and 19759 servers read from /gluetun/servers.json
2024-05-24T12:28:14-04:00 INFO Using ipvanish servers from file which are 718 days more recent
2024-05-24T12:28:15-04:00 INFO updating Ipvanish servers...
2024-05-24T12:28:23-04:00 INFO merging by most recent 19425 hardcoded servers and 19759 servers read from /gluetun/servers.json
2024-05-24T12:28:23-04:00 INFO Using ipvanish servers from file which are 718 days more recent
2024-05-24T12:28:23-04:00 INFO updating Ipvanish servers...
2024-05-24T12:28:27-04:00 INFO merging by most recent 19425 hardcoded servers and 19759 servers read from /gluetun/servers.json
2024-05-24T12:28:27-04:00 INFO Using ipvanish servers from file which are 718 days more recent
2024-05-24T12:28:27-04:00 INFO updating Ipvanish servers...
Singling out the iptables error message from the full log below:
2024-05-24T15:48:48.922591262Z 2024-05-24T11:48:48-04:00 ERROR [firewall] cannot remove outdated VPN interface rule: command failed: "ip6tables --delete OUTPUT -o tun0 -j ACCEPT": ip6tables: Bad rule (does a matching rule exist in that chain?).: exit status 1
Complete log:
2024-05-24T15:48:42.123342861Z ========================================
2024-05-24T15:48:42.123379478Z ========================================
2024-05-24T15:48:42.123383699Z =============== gluetun ================
2024-05-24T15:48:42.123387293Z ========================================
2024-05-24T15:48:42.123390579Z =========== Made with โค๏ธ by ============
2024-05-24T15:48:42.123394368Z ======= https://github.com/qdm12 =======
2024-05-24T15:48:42.123397631Z ========================================
2024-05-24T15:48:42.123400971Z ========================================
2024-05-24T15:48:42.123404200Z
2024-05-24T15:48:42.123407777Z Running version latest built on 2024-05-18T18:08:57.405Z (commit 4218dba)
2024-05-24T15:48:42.123411207Z
2024-05-24T15:48:42.123414336Z ๐ง Need help? https://github.com/qdm12/gluetun/discussions/new
2024-05-24T15:48:42.123417846Z ๐ Bug? https://github.com/qdm12/gluetun/issues/new
2024-05-24T15:48:42.123421208Z โจ New feature? https://github.com/qdm12/gluetun/issues/new
2024-05-24T15:48:42.123424532Z โ Discussion? https://github.com/qdm12/gluetun/discussions/new
2024-05-24T15:48:42.123427857Z ๐ป Email? quentin.mcgaw@gmail.com
2024-05-24T15:48:42.123431400Z ๐ฐ Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2024-05-24T15:48:42.127569140Z 2024-05-24T11:48:42-04:00 INFO [routing] default route found: interface eth0, gateway 10.10.11.1, assigned IP 10.10.11.3 and family v4
2024-05-24T15:48:42.127613148Z 2024-05-24T11:48:42-04:00 INFO [routing] local ethernet link found: eth0
2024-05-24T15:48:42.127617956Z 2024-05-24T11:48:42-04:00 INFO [routing] local ipnet found: 10.10.11.0/24
2024-05-24T15:48:42.127621914Z 2024-05-24T11:48:42-04:00 INFO [routing] local ipnet found: fe80::/64
2024-05-24T15:48:42.171912406Z 2024-05-24T11:48:42-04:00 INFO [firewall] enabling...
2024-05-24T15:48:42.239496353Z 2024-05-24T11:48:42-04:00 INFO [firewall] enabled successfully
2024-05-24T15:48:42.783918717Z 2024-05-24T11:48:42-04:00 INFO [storage] merging by most recent 19425 hardcoded servers and 19759 servers read from /gluetun/servers.json
2024-05-24T15:48:42.784743277Z 2024-05-24T11:48:42-04:00 INFO [storage] Using ipvanish servers from file which are 718 days more recent
2024-05-24T15:48:42.888926596Z 2024-05-24T11:48:42-04:00 INFO Alpine version: 3.19.1
2024-05-24T15:48:42.900647054Z 2024-05-24T11:48:42-04:00 INFO OpenVPN 2.5 version: 2.5.8
2024-05-24T15:48:42.906078034Z 2024-05-24T11:48:42-04:00 INFO OpenVPN 2.6 version: 2.6.8
2024-05-24T15:48:42.909964665Z 2024-05-24T11:48:42-04:00 INFO Unbound version: 1.20.0
2024-05-24T15:48:42.910556395Z 2024-05-24T11:48:42-04:00 INFO IPtables version: v1.8.10
2024-05-24T15:48:42.910699039Z 2024-05-24T11:48:42-04:00 INFO Settings summary:
2024-05-24T15:48:42.910704850Z โโโ VPN settings:
2024-05-24T15:48:42.910709215Z | โโโ VPN provider settings:
2024-05-24T15:48:42.910735200Z | | โโโ Name: ipvanish
2024-05-24T15:48:42.910739079Z | | โโโ Server selection settings:
2024-05-24T15:48:42.910742756Z | | โโโ VPN type: openvpn
2024-05-24T15:48:42.910746605Z | | โโโ Countries: United States
2024-05-24T15:48:42.910750233Z | | โโโ OpenVPN server selection settings:
2024-05-24T15:48:42.910753905Z | | โโโ Protocol: UDP
2024-05-24T15:48:42.910757563Z | โโโ OpenVPN settings:
2024-05-24T15:48:42.910771736Z | โโโ OpenVPN version: 2.6
2024-05-24T15:48:42.910775519Z | โโโ User: [set]
2024-05-24T15:48:42.910779148Z | โโโ Password: [set]
2024-05-24T15:48:42.910782729Z | โโโ Network interface: tun0
2024-05-24T15:48:42.910786242Z | โโโ Run OpenVPN as: root
2024-05-24T15:48:42.910789657Z | โโโ Verbosity level: 1
2024-05-24T15:48:42.910793301Z โโโ DNS settings:
2024-05-24T15:48:42.910796923Z | โโโ Keep existing nameserver(s): no
2024-05-24T15:48:42.910800402Z | โโโ DNS server address to use: 127.0.0.1
2024-05-24T15:48:42.910803852Z | โโโ DNS over TLS settings:
2024-05-24T15:48:42.910807283Z | โโโ Enabled: yes
2024-05-24T15:48:42.910810951Z | โโโ Update period: every 24h0m0s
2024-05-24T15:48:42.910814442Z | โโโ Unbound settings:
2024-05-24T15:48:42.910817962Z | | โโโ Authoritative servers:
2024-05-24T15:48:42.910821487Z | | | โโโ cloudflare
2024-05-24T15:48:42.910825000Z | | โโโ Caching: yes
2024-05-24T15:48:42.910828498Z | | โโโ IPv6: no
2024-05-24T15:48:42.910832557Z | | โโโ Verbosity level: 1
2024-05-24T15:48:42.910836041Z | | โโโ Verbosity details level: 0
2024-05-24T15:48:42.910849390Z | | โโโ Validation log level: 0
2024-05-24T15:48:42.910853019Z | | โโโ System user: root
2024-05-24T15:48:42.910856733Z | | โโโ Allowed networks:
2024-05-24T15:48:42.910860285Z | | โโโ 0.0.0.0/0
2024-05-24T15:48:42.910863999Z | | โโโ ::/0
2024-05-24T15:48:42.910867569Z | โโโ DNS filtering settings:
2024-05-24T15:48:42.910871163Z | โโโ Block malicious: yes
2024-05-24T15:48:42.910874763Z | โโโ Block ads: no
2024-05-24T15:48:42.910878317Z | โโโ Block surveillance: no
2024-05-24T15:48:42.910881914Z | โโโ Blocked IP networks:
2024-05-24T15:48:42.910885558Z | โโโ 127.0.0.1/8
2024-05-24T15:48:42.910892332Z | โโโ 10.0.0.0/8
2024-05-24T15:48:42.910896048Z | โโโ 172.16.0.0/12
2024-05-24T15:48:42.910899623Z | โโโ 192.168.0.0/16
2024-05-24T15:48:42.910903221Z | โโโ 169.254.0.0/16
2024-05-24T15:48:42.910906686Z | โโโ ::1/128
2024-05-24T15:48:42.910910178Z | โโโ fc00::/7
2024-05-24T15:48:42.910922984Z | โโโ fe80::/10
2024-05-24T15:48:42.910926716Z | โโโ ::ffff:127.0.0.1/104
2024-05-24T15:48:42.910930241Z | โโโ ::ffff:10.0.0.0/104
2024-05-24T15:48:42.910933786Z | โโโ ::ffff:169.254.0.0/112
2024-05-24T15:48:42.910937284Z | โโโ ::ffff:172.16.0.0/108
2024-05-24T15:48:42.910941474Z | โโโ ::ffff:192.168.0.0/112
2024-05-24T15:48:42.910945100Z โโโ Firewall settings:
2024-05-24T15:48:42.910948691Z | โโโ Enabled: yes
2024-05-24T15:48:42.910952140Z โโโ Log settings:
2024-05-24T15:48:42.910955864Z | โโโ Log level: info
2024-05-24T15:48:42.910977161Z โโโ Health settings:
2024-05-24T15:48:42.910982514Z | โโโ Server listening address: 127.0.0.1:9999
2024-05-24T15:48:42.911004722Z | โโโ Target address: cloudflare.com:443
2024-05-24T15:48:42.911008646Z | โโโ Duration to wait after success: 5s
2024-05-24T15:48:42.911012208Z | โโโ Read header timeout: 100ms
2024-05-24T15:48:42.911016367Z | โโโ Read timeout: 500ms
2024-05-24T15:48:42.911019860Z | โโโ VPN wait durations:
2024-05-24T15:48:42.911023347Z | โโโ Initial duration: 6s
2024-05-24T15:48:42.911026832Z | โโโ Additional duration: 5s
2024-05-24T15:48:42.911030430Z โโโ Shadowsocks server settings:
2024-05-24T15:48:42.911034037Z | โโโ Enabled: no
2024-05-24T15:48:42.911037792Z โโโ HTTP proxy settings:
2024-05-24T15:48:42.911041370Z | โโโ Enabled: no
2024-05-24T15:48:42.911044850Z โโโ Control server settings:
2024-05-24T15:48:42.911048667Z | โโโ Listening address: :8000
2024-05-24T15:48:42.911052205Z | โโโ Logging: yes
2024-05-24T15:48:42.911055860Z โโโ OS Alpine settings:
2024-05-24T15:48:42.911059522Z | โโโ Process UID: 1000
2024-05-24T15:48:42.911063021Z | โโโ Process GID: 1000
2024-05-24T15:48:42.911076205Z | โโโ Timezone: America/New_York
2024-05-24T15:48:42.911080759Z โโโ Public IP settings:
2024-05-24T15:48:42.911084518Z | โโโ Fetching: every 12h0m0s
2024-05-24T15:48:42.911088014Z | โโโ IP file path: /tmp/gluetun/ip
2024-05-24T15:48:42.911094368Z | โโโ Public IP data API: ipinfo
2024-05-24T15:48:42.911097933Z โโโ Server data updater settings:
2024-05-24T15:48:42.911101507Z | โโโ Update period: 24h0m0s
2024-05-24T15:48:42.911104988Z | โโโ DNS address: 1.1.1.1:53
2024-05-24T15:48:42.911108434Z | โโโ Minimum ratio: 0.8
2024-05-24T15:48:42.911111892Z | โโโ Providers to update: ipvanish
2024-05-24T15:48:42.911115405Z โโโ Version settings:
2024-05-24T15:48:42.911118961Z โโโ Enabled: yes
2024-05-24T15:48:42.912327071Z 2024-05-24T11:48:42-04:00 INFO [routing] default route found: interface eth0, gateway 10.10.11.1, assigned IP 10.10.11.3 and family v4
2024-05-24T15:48:42.912362770Z 2024-05-24T11:48:42-04:00 INFO [routing] adding route for 0.0.0.0/0
2024-05-24T15:48:42.912432688Z 2024-05-24T11:48:42-04:00 INFO [firewall] setting allowed subnets...
2024-05-24T15:48:42.912557471Z 2024-05-24T11:48:42-04:00 INFO [routing] default route found: interface eth0, gateway 10.10.11.1, assigned IP 10.10.11.3 and family v4
2024-05-24T15:48:42.913032148Z 2024-05-24T11:48:42-04:00 INFO [dns] using plaintext DNS at address 1.1.1.1
2024-05-24T15:48:42.913416626Z 2024-05-24T11:48:42-04:00 INFO [http server] http server listening on [::]:8000
2024-05-24T15:48:42.913491962Z 2024-05-24T11:48:42-04:00 INFO [healthcheck] listening on 127.0.0.1:9999
2024-05-24T15:48:42.924637898Z 2024-05-24T11:48:42-04:00 INFO [firewall] allowing VPN connection...
2024-05-24T15:48:42.968219843Z 2024-05-24T11:48:42-04:00 INFO [openvpn] OpenVPN 2.6.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-05-24T15:48:42.968263357Z 2024-05-24T11:48:42-04:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-05-24T15:48:42.968268433Z 2024-05-24T11:48:42-04:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.79.56:443
2024-05-24T15:48:42.968272945Z 2024-05-24T11:48:42-04:00 INFO [openvpn] UDPv4 link local: (not bound)
2024-05-24T15:48:42.968277120Z 2024-05-24T11:48:42-04:00 INFO [openvpn] UDPv4 link remote: [AF_INET]216.131.79.56:443
2024-05-24T15:48:48.917865075Z 2024-05-24T11:48:48-04:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN
2024-05-24T15:48:48.917888976Z 2024-05-24T11:48:48-04:00 INFO [healthcheck] ๐ See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-24T15:48:48.917899497Z 2024-05-24T11:48:48-04:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-24T15:48:48.917903297Z 2024-05-24T11:48:48-04:00 INFO [vpn] stopping
2024-05-24T15:48:48.918875156Z 2024-05-24T11:48:48-04:00 INFO [vpn] starting
2024-05-24T15:48:48.919882618Z 2024-05-24T11:48:48-04:00 INFO [firewall] allowing VPN connection...
2024-05-24T15:48:48.922591262Z 2024-05-24T11:48:48-04:00 ERROR [firewall] cannot remove outdated VPN interface rule: command failed: "ip6tables --delete OUTPUT -o tun0 -j ACCEPT": ip6tables: Bad rule (does a matching rule exist in that chain?).: exit status 1
2024-05-24T15:48:48.927485845Z 2024-05-24T11:48:48-04:00 INFO [openvpn] OpenVPN 2.6.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-05-24T15:48:48.927504077Z 2024-05-24T11:48:48-04:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-05-24T15:48:48.928877367Z 2024-05-24T11:48:48-04:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.74.196:443
2024-05-24T15:48:48.928919708Z 2024-05-24T11:48:48-04:00 INFO [openvpn] UDPv4 link local: (not bound)
2024-05-24T15:48:48.928970904Z 2024-05-24T11:48:48-04:00 INFO [openvpn] UDPv4 link remote: [AF_INET]216.131.74.196:443
2024-05-24T15:49:00.025812375Z 2024-05-24T11:49:00-04:00 INFO [healthcheck] program has been unhealthy for 11s: restarting VPN
2024-05-24T15:49:00.025832953Z 2024-05-24T11:49:00-04:00 INFO [healthcheck] ๐ See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-24T15:49:00.025837391Z 2024-05-24T11:49:00-04:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-24T15:49:00.025840664Z 2024-05-24T11:49:00-04:00 INFO [vpn] stopping
2024-05-24T15:49:00.026109928Z 2024-05-24T11:49:00-04:00 INFO [vpn] starting
2024-05-24T15:49:00.027049236Z 2024-05-24T11:49:00-04:00 INFO [firewall] allowing VPN connection...
2024-05-24T15:49:00.034641422Z 2024-05-24T11:49:00-04:00 INFO [openvpn] OpenVPN 2.6.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-05-24T15:49:00.034654412Z 2024-05-24T11:49:00-04:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-05-24T15:49:00.036069616Z 2024-05-24T11:49:00-04:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.75.57:443
2024-05-24T15:49:00.036152367Z 2024-05-24T11:49:00-04:00 INFO [openvpn] UDPv4 link local: (not bound)
2024-05-24T15:49:00.036208480Z 2024-05-24T11:49:00-04:00 INFO [openvpn] UDPv4 link remote: [AF_INET]216.131.75.57:443
2024-05-24T15:49:16.132760491Z 2024-05-24T11:49:16-04:00 INFO [healthcheck] program has been unhealthy for 16s: restarting VPN
2024-05-24T15:49:16.132799996Z 2024-05-24T11:49:16-04:00 INFO [healthcheck] ๐ See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-24T15:49:16.132805838Z 2024-05-24T11:49:16-04:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-24T15:49:16.132810071Z 2024-05-24T11:49:16-04:00 INFO [vpn] stopping
2024-05-24T15:49:16.133102201Z 2024-05-24T11:49:16-04:00 INFO [vpn] starting
2024-05-24T15:49:16.134190348Z 2024-05-24T11:49:16-04:00 INFO [firewall] allowing VPN connection...
2024-05-24T15:49:16.143227798Z 2024-05-24T11:49:16-04:00 INFO [openvpn] OpenVPN 2.6.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-05-24T15:49:16.143243706Z 2024-05-24T11:49:16-04:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-05-24T15:49:16.144926342Z 2024-05-24T11:49:16-04:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]216.131.83.33:443
2024-05-24T15:49:16.145042281Z 2024-05-24T11:49:16-04:00 INFO [openvpn] UDPv4 link local: (not bound)
2024-05-24T15:49:16.145141782Z 2024-05-24T11:49:16-04:00 INFO [openvpn] UDPv4 link remote: [AF_INET]216.131.83.33:443
2024-05-24T15:49:37.240534296Z 2024-05-24T11:49:37-04:00 INFO [healthcheck] program has been unhealthy for 21s: restarting VPN
2024-05-24T15:49:37.240558138Z 2024-05-24T11:49:37-04:00 INFO [healthcheck] ๐ See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-24T15:49:37.240563420Z 2024-05-24T11:49:37-04:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-24T15:49:37.240567924Z 2024-05-24T11:49:37-04:00 INFO [vpn] stopping
2024-05-24T15:49:37.240973555Z 2024-05-24T11:49:37-04:00 INFO [vpn] starting
2024-05-24T15:49:37.242283048Z 2024-05-24T11:49:37-04:00 INFO [firewall] allowing VPN connection...
2024-05-24T15:49:37.251521507Z 2024-05-24T11:49:37-04:00 INFO [openvpn] OpenVPN 2.6.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-05-24T15:49:37.251539609Z 2024-05-24T11:49:37-04:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-05-24T15:49:37.253318418Z 2024-05-24T11:49:37-04:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]207.204.248.151:443
2024-05-24T15:49:37.253494861Z 2024-05-24T11:49:37-04:00 INFO [openvpn] UDPv4 link local: (not bound)
2024-05-24T15:49:37.253502135Z 2024-05-24T11:49:37-04:00 INFO [openvpn] UDPv4 link remote: [AF_INET]207.204.248.151:443
2024-05-24T15:50:03.348881365Z 2024-05-24T11:50:03-04:00 INFO [healthcheck] program has been unhealthy for 26s: restarting VPN
2024-05-24T15:50:03.348919208Z 2024-05-24T11:50:03-04:00 INFO [healthcheck] ๐ See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-05-24T15:50:03.348925185Z 2024-05-24T11:50:03-04:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-05-24T15:50:03.348929257Z 2024-05-24T11:50:03-04:00 INFO [vpn] stopping
2024-05-24T15:50:03.349313300Z 2024-05-24T11:50:03-04:00 INFO [vpn] starting
2024-05-24T15:50:03.350591874Z 2024-05-24T11:50:03-04:00 INFO [firewall] allowing VPN connection...
2024-05-24T15:50:03.359547723Z 2024-05-24T11:50:03-04:00 INFO [openvpn] OpenVPN 2.6.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-05-24T15:50:03.359753967Z 2024-05-24T11:50:03-04:00 INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-05-24T15:50:03.361080300Z 2024-05-24T11:50:03-04:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]173.245.203.236:443
2024-05-24T15:50:03.361215904Z 2024-05-24T11:50:03-04:00 INFO [openvpn] UDPv4 link local: (not bound)
2024-05-24T15:50:03.361349602Z 2024-05-24T11:50:03-04:00 INFO [openvpn] UDPv4 link remote: [AF_INET]173.245.203.236:443
I am having the same issue with IPVanish, i'm trying to get an IP from Peru:
docker run --rm --cap-add=NET_ADMIN --device /dev/net/tun \
-e VPN_SERVICE_PROVIDER=ipvanish \
-e OPENVPN_USER=abc \
-e OPENVPN_PASSWORD=abc \
-e SERVER_COUNTRIES=Peru \
-e BLOCK_MALICIOUS=off \
qmcgaw/gluetun
With the following result:
2024-06-13T21:23:21Z INFO [routing] default route found: interface eth0, gateway 172.17.0.1, assigned IP 172.17.0.3 and family v4
2024-06-13T21:23:21Z INFO [routing] adding route for 0.0.0.0/0
2024-06-13T21:23:21Z INFO [firewall] setting allowed subnets...
2024-06-13T21:23:21Z INFO [routing] default route found: interface eth0, gateway 172.17.0.1, assigned IP 172.17.0.3 and family v4
2024-06-13T21:23:21Z INFO [dns] using plaintext DNS at address 1.1.1.1
2024-06-13T21:23:21Z INFO [http server] http server listening on [::]:8000
2024-06-13T21:23:21Z INFO [healthcheck] listening on 127.0.0.1:9999
2024-06-13T21:23:21Z INFO [firewall] allowing VPN connection...
2024-06-13T21:23:21Z INFO [openvpn] OpenVPN 2.6.8 aarch64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-06-13T21:23:21Z INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-06-13T21:23:21Z INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]191.101.24.13:443
2024-06-13T21:23:21Z INFO [openvpn] UDPv4 link local: (not bound)
2024-06-13T21:23:21Z INFO [openvpn] UDPv4 link remote: [AF_INET]191.101.24.13:443
2024-06-13T21:23:27Z INFO [healthcheck] program has been unhealthy for 6s: restarting VPN
2024-06-13T21:23:27Z INFO [healthcheck] ๐ See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-06-13T21:23:27Z INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-06-13T21:23:27Z INFO [vpn] stopping
2024-06-13T21:23:27Z INFO [vpn] starting
2024-06-13T21:23:27Z INFO [firewall] allowing VPN connection...
2024-06-13T21:23:27Z INFO [openvpn] OpenVPN 2.6.8 aarch64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2024-06-13T21:23:27Z INFO [openvpn] library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-06-13T21:23:27Z INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]191.101.24.13:443
2024-06-13T21:23:27Z INFO [openvpn] UDPv4 link local: (not bound)
2024-06-13T21:23:27Z INFO [openvpn] UDPv4 link remote: [AF_INET]191.101.24.13:443
After reading the comments, I tried using SERVER_HOSTNAMES with a random server name from https://configs.ipvanish.com/configs/configs.zip, but I encountered the same issue because Gluetun keeps using the same IP in the map.
docker run --rm --cap-add=NET_ADMIN --device /dev/net/tun \
-e VPN_SERVICE_PROVIDER=ipvanish \
-e OPENVPN_USER=abc \
-e OPENVPN_PASSWORD=abc \
-e SERVER_HOSTNAMES=lim-c03.ipvanish.com \
-e BLOCK_MALICIOUS=off \
qmcgaw/gluetun
{
"vpn": "openvpn",
"country": "Peru",
"city": "Lima",
"hostname": "lim-c03.ipvanish.com",
"udp": true,
"ips": [
"191.101.24.13"
]
}
I checked the host for IPVanish, and I can ping and get an IP from the server in Peru:
$ ping lim-c03.ipvanish.com
PING lim-c03.ipvanish.com (205.185.218.17): 56 data bytes
64 bytes from 205.185.218.17: icmp_seq=0 ttl=56 time=40.665 ms
64 bytes from 205.185.218.17: icmp_seq=0 ttl=56 time=44.290 ms (DUP!)
64 bytes from 205.185.218.17: icmp_seq=1 ttl=56 time=41.019 ms
64 bytes from 205.185.218.17: icmp_seq=1 ttl=56 time=44.878 ms (DUP!)
64 bytes from 205.185.218.17: icmp_seq=2 ttl=56 time=40.297 ms
64 bytes from 205.185.218.17: icmp_seq=2 ttl=56 time=44.301 ms (DUP!)
64 bytes from 205.185.218.17: icmp_seq=3 ttl=56 time=48.476 ms
64 bytes from 205.185.218.17: icmp_seq=3 ttl=56 time=52.148 ms (DUP!)
64 bytes from 205.185.218.17: icmp_seq=4 ttl=56 time=40.270 ms
64 bytes from 205.185.218.17: icmp_seq=4 ttl=56 time=45.960 ms (DUP!)
64 bytes from 205.185.218.17: icmp_seq=5 ttl=56 time=40.935 ms
64 bytes from 205.185.218.17: icmp_seq=5 ttl=56 time=44.703 ms (DUP!)
64 bytes from 205.185.218.17: icmp_seq=6 ttl=56 time=39.663 ms
64 bytes from 205.185.218.17: icmp_seq=6 ttl=56 time=43.499 ms (DUP!)
^C
--- lim-c03.ipvanish.com ping statistics ---
7 packets transmitted, 7 packets received, +7 duplicates, 0.0% packet loss
round-trip min/avg/max/stddev = 39.663/43.650/52.148/3.444 ms
After reading the wiki, I tried to update the server list by running the command:
docker run --rm \
--name gluetun \
-v /tmp/gluetun:/gluetun \
qmcgaw/gluetun update -enduser -providers ipvanish -minratio 0.0
However, Gluetun can't get any IP from IPVanish. I tried with other providers, and it works. The error message is: updating server information: getting servers: not enough servers found: 0 and expected at least 1648
.
Could there be a bug or a missing configuration in my Docker setup?
2024-06-13T21:33:02Z INFO merging by most recent 19425 hardcoded servers and 19426 servers read from /gluetun/servers.json
2024-06-13T21:33:02Z INFO Using surfshark servers from file which are 45 days more recent
2024-06-13T21:33:02Z INFO updating Ipvanish servers...
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b58.ipvanish.com: lookup atl-b58.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a28.ipvanish.com: lookup ams-a28.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b56.ipvanish.com: lookup atl-b56.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c10.ipvanish.com: lookup bhx-c10.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a18.ipvanish.com: lookup ams-a18.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a19.ipvanish.com: lookup ams-a19.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving adl-c05.ipvanish.com: lookup adl-c05.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a22.ipvanish.com: lookup ams-a22.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a26.ipvanish.com: lookup ams-a26.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving akl-c02.ipvanish.com: lookup akl-c02.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a24.ipvanish.com: lookup ams-a24.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a15.ipvanish.com: lookup ams-a15.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b09.ipvanish.com: lookup atl-b09.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a16.ipvanish.com: lookup ams-a16.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a27.ipvanish.com: lookup ams-a27.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a20.ipvanish.com: lookup ams-a20.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c19.ipvanish.com: lookup tlv-c19.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tll-c10.ipvanish.com: lookup tll-c10.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c11.ipvanish.com: lookup tlv-c11.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tll-c11.ipvanish.com: lookup tll-c11.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c13.ipvanish.com: lookup tlv-c13.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c16.ipvanish.com: lookup tlv-c16.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c17.ipvanish.com: lookup tlv-c17.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a17.ipvanish.com: lookup ams-a17.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b61.ipvanish.com: lookup atl-b61.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b62.ipvanish.com: lookup atl-b62.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b59.ipvanish.com: lookup atl-b59.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b60.ipvanish.com: lookup atl-b60.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b14.ipvanish.com: lookup atl-b14.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b19.ipvanish.com: lookup atl-b19.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b20.ipvanish.com: lookup atl-b20.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b64.ipvanish.com: lookup atl-b64.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b65.ipvanish.com: lookup atl-b65.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b07.ipvanish.com: lookup tor-b07.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c20.ipvanish.com: lookup tlv-c20.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c21.ipvanish.com: lookup tlv-c21.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c22.ipvanish.com: lookup tlv-c22.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tlv-c23.ipvanish.com: lookup tlv-c23.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b01.ipvanish.com: lookup tor-b01.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b02.ipvanish.com: lookup tor-b02.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c06.ipvanish.com: lookup ams-c06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b03.ipvanish.com: lookup tor-b03.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b04.ipvanish.com: lookup tor-b04.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a29.ipvanish.com: lookup ams-a29.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b06.ipvanish.com: lookup tor-b06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a31.ipvanish.com: lookup ams-a31.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a51.ipvanish.com: lookup ams-a51.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c02.ipvanish.com: lookup ams-c02.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c04.ipvanish.com: lookup ams-c04.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a32.ipvanish.com: lookup ams-a32.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a37.ipvanish.com: lookup ams-a37.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a36.ipvanish.com: lookup ams-a36.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-a34.ipvanish.com: lookup ams-a34.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b11.ipvanish.com: lookup tor-b11.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b08.ipvanish.com: lookup tor-b08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b09.ipvanish.com: lookup tor-b09.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a12.ipvanish.com: lookup atl-a12.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c07.ipvanish.com: lookup ams-c07.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c08.ipvanish.com: lookup ams-c08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c09.ipvanish.com: lookup ams-c09.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c16.ipvanish.com: lookup ams-c16.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ams-c18.ipvanish.com: lookup ams-c18.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ath-c04.ipvanish.com: lookup ath-c04.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ath-c05.ipvanish.com: lookup ath-c05.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ath-c06.ipvanish.com: lookup ath-c06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ath-c08.ipvanish.com: lookup ath-c08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving ath-c09.ipvanish.com: lookup ath-c09.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a79.ipvanish.com: lookup atl-a79.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vie-c12.ipvanish.com: lookup vie-c12.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a07.ipvanish.com: lookup atl-a07.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c11.ipvanish.com: lookup bhx-c11.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a08.ipvanish.com: lookup atl-a08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vlc-c02.ipvanish.com: lookup vlc-c02.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a09.ipvanish.com: lookup atl-a09.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b14.ipvanish.com: lookup tor-b14.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b15.ipvanish.com: lookup tor-b15.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a82.ipvanish.com: lookup atl-a82.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b16.ipvanish.com: lookup tor-b16.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a10.ipvanish.com: lookup atl-a10.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b17.ipvanish.com: lookup tor-b17.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b71.ipvanish.com: lookup atl-b71.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b70.ipvanish.com: lookup atl-b70.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vlc-c03.ipvanish.com: lookup vlc-c03.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a01.ipvanish.com: lookup atl-a01.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c13.ipvanish.com: lookup bhx-c13.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a84.ipvanish.com: lookup atl-a84.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b18.ipvanish.com: lookup tor-b18.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c10.ipvanish.com: lookup tpe-c10.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vlc-c07.ipvanish.com: lookup vlc-c07.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c11.ipvanish.com: lookup tpe-c11.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c04.ipvanish.com: lookup tpe-c04.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vie-c06.ipvanish.com: lookup vie-c06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b19.ipvanish.com: lookup tor-b19.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b20.ipvanish.com: lookup tor-b20.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vie-c08.ipvanish.com: lookup vie-c08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c01.ipvanish.com: lookup tpe-c01.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vie-c10.ipvanish.com: lookup vie-c10.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c02.ipvanish.com: lookup tpe-c02.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a06.ipvanish.com: lookup atl-a06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c03.ipvanish.com: lookup tpe-c03.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tor-b13.ipvanish.com: lookup tor-b13.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving waw-a01.ipvanish.com: lookup waw-a01.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c08.ipvanish.com: lookup tpe-c08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c05.ipvanish.com: lookup tpe-c05.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving vlc-c04.ipvanish.com: lookup vlc-c04.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c07.ipvanish.com: lookup tpe-c07.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving tpe-c09.ipvanish.com: lookup tpe-c09.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a86.ipvanish.com: lookup atl-a86.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving waw-a04.ipvanish.com: lookup waw-a04.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a88.ipvanish.com: lookup atl-a88.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving waw-a03.ipvanish.com: lookup waw-a03.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a87.ipvanish.com: lookup atl-a87.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b45.ipvanish.com: lookup atl-b45.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b50.ipvanish.com: lookup atl-b50.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b39.ipvanish.com: lookup atl-b39.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b47.ipvanish.com: lookup atl-b47.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b40.ipvanish.com: lookup atl-b40.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b48.ipvanish.com: lookup atl-b48.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b41.ipvanish.com: lookup atl-b41.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c12.ipvanish.com: lookup bhx-c12.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b43.ipvanish.com: lookup atl-b43.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b51.ipvanish.com: lookup atl-b51.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b75.ipvanish.com: lookup atl-b75.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b42.ipvanish.com: lookup atl-b42.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b52.ipvanish.com: lookup atl-b52.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-a91.ipvanish.com: lookup atl-a91.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c30.ipvanish.com: lookup bhx-c30.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a35.ipvanish.com: lookup bos-a35.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c15.ipvanish.com: lookup bhx-c15.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c16.ipvanish.com: lookup bhx-c16.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a40.ipvanish.com: lookup bos-a40.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving chi-a30.ipvanish.com: lookup chi-a30.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c31.ipvanish.com: lookup bhx-c31.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c17.ipvanish.com: lookup bhx-c17.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c33.ipvanish.com: lookup bhx-c33.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c19.ipvanish.com: lookup bhx-c19.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving zrh-c15.ipvanish.com: lookup zrh-c15.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c34.ipvanish.com: lookup bhx-c34.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c20.ipvanish.com: lookup bhx-c20.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving waw-a06.ipvanish.com: lookup waw-a06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c35.ipvanish.com: lookup bhx-c35.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c21.ipvanish.com: lookup bhx-c21.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving waw-a18.ipvanish.com: lookup waw-a18.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c22.ipvanish.com: lookup bhx-c22.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bkk-c01.ipvanish.com: lookup bkk-c01.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving waw-a19.ipvanish.com: lookup waw-a19.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bkk-c02.ipvanish.com: lookup bkk-c02.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c01.ipvanish.com: lookup yul-c01.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c25.ipvanish.com: lookup bhx-c25.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bkk-c04.ipvanish.com: lookup bkk-c04.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c28.ipvanish.com: lookup bhx-c28.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c12.ipvanish.com: lookup yul-c12.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bne-c01.ipvanish.com: lookup bne-c01.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bhx-c29.ipvanish.com: lookup bhx-c29.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c13.ipvanish.com: lookup yul-c13.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bne-c05.ipvanish.com: lookup bne-c05.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c15.ipvanish.com: lookup yul-c15.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a42.ipvanish.com: lookup bos-a42.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c16.ipvanish.com: lookup yul-c16.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving waw-a07.ipvanish.com: lookup waw-a07.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bne-c06.ipvanish.com: lookup bne-c06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c17.ipvanish.com: lookup yul-c17.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a27.ipvanish.com: lookup bos-a27.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a26.ipvanish.com: lookup bos-a26.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b83.ipvanish.com: lookup atl-b83.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c19.ipvanish.com: lookup yul-c19.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a57.ipvanish.com: lookup bos-a57.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c20.ipvanish.com: lookup yul-c20.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bod-c08.ipvanish.com: lookup bod-c08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b76.ipvanish.com: lookup atl-b76.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a32.ipvanish.com: lookup bos-a32.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c21.ipvanish.com: lookup yul-c21.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bog-c06.ipvanish.com: lookup bog-c06.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b78.ipvanish.com: lookup atl-b78.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a33.ipvanish.com: lookup bos-a33.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c23.ipvanish.com: lookup yul-c23.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bog-c08.ipvanish.com: lookup bog-c08.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b80.ipvanish.com: lookup atl-b80.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a34.ipvanish.com: lookup bos-a34.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c24.ipvanish.com: lookup yul-c24.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bog-c10.ipvanish.com: lookup bog-c10.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving atl-b81.ipvanish.com: lookup atl-b81.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c28.ipvanish.com: lookup yul-c28.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bog-c11.ipvanish.com: lookup bog-c11.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c29.ipvanish.com: lookup yul-c29.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yul-c18.ipvanish.com: lookup yul-c18.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving bos-a24.ipvanish.com: lookup bos-a24.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving yvr-c05.ipvanish.com: lookup yvr-c05.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN reached the maximum number of consecutive failures: 2 failed attempts resolving zag-c12.ipvanish.com: lookup zag-c12.ipvanish.com: i/o timeout
2024-06-13T21:33:22Z WARN note: if running the update manually, you can use the flag -minratio to allow the update to succeed with less servers found
2024-06-13T21:33:22Z ERROR updating server information: getting servers: not enough servers found: 0 and expected at least 1648
2024-06-13T21:33:22Z INFO Shutdown successful
Running into the same issue. Has anyone been able to resolve this? Or a work around?
Using the ipvanish app on mac, I see that when I select the openvpn option it doesn't work, but if I use wireguard it does work. So, is it that they stopped supporting openvpn?
Is this urgent?
None
Host OS
Ubuntu
CPU arch
None
VPN service provider
IPVanish
What are you using to run the container
Portainer
What is the version of Gluetun
Running version latest built on 2024-01-01T18:24:19.221Z (commit c826707)
What's the problem ๐ค
The issue can possibly be closed quickly if it turns out that this is not a problem with Gluetun.
Since this morning I have been receiving the following error message:
I have already unsuccessfully tried to update the server list. The problem seems to be related to the fact that the Gluetun container cannot reach anything outside its own 10.2.0.0/16 network. I can successfully ping other IP addresses from the network, but not e.g. cloudflare.com or other IPs outside the network.
I have not changed anything on my network infrastructure and this error came out of nowhere this morning. Maybe a problem with IPVanish?
Every other IP on the 10.2.0.0/16 network can successfully make a connection to the internet.
Share your logs (at least 10 lines)
Share your configuration