You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current servers.json includes
zrh-00(5-8).vpn.privado.io
Activated periodically update with UPDATER_PERIOD=5m and it runs without an error. But servers.json remains unchanged.
Also tried UPDATER_MIN_RATIO=0.1 (beside the default 0.8)
Manual update works with docker run --rm -v /yourpath:/gluetun qmcgaw/gluetun update -enduser -providers privado
Share your logs (at least 10 lines)
2024-02-18T00:34:10+01:00 INFO [dns] ready
2024-02-18T00:34:10+01:00 INFO [vpn] You are running on the bleeding edge of latest!
2024-02-18T00:34:10+01:00 INFO [ip getter] Public IP address is 98.98.131.240 (Turkey, Istanbul, Istanbul)
2024-02-18T00:39:02+01:00 INFO [updater] updating Privado servers...
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving prg-003.vpn.privado.io: lookup prg-003.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving hkg-001.vpn.privado.io: lookup hkg-001.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving sea-020.vpn.privado.io: lookup sea-020.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving jfk-062.vpn.privado.io: lookup jfk-062.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving zrh-010.vpn.privado.io: lookup zrh-010.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving prg-004.vpn.privado.io: lookup prg-004.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving icn-003.vpn.privado.io: lookup icn-003.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving waw-005.vpn.privado.io: lookup waw-005.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving man-009.vpn.privado.io: lookup man-009.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving prg-002.vpn.privado.io: lookup prg-002.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving nrt-001.vpn.privado.io: lookup nrt-001.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving sin-002.vpn.privado.io: lookup sin-002.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving syd-002.vpn.privado.io: lookup syd-002.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving dca-005.vpn.privado.io: lookup dca-005.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving dca-007.vpn.privado.io: lookup dca-007.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving syd-010.vpn.privado.io: lookup syd-010.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving gru-008.vpn.privado.io: lookup gru-008.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving sfo-005.vpn.privado.io: lookup sfo-005.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving dtw-004.vpn.privado.io: lookup dtw-004.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving sea-013.vpn.privado.io: lookup sea-013.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving pdx-018.vpn.privado.io: lookup pdx-018.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving pdx-004.vpn.privado.io: lookup pdx-004.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving cgk-003.vpn.privado.io: lookup cgk-003.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving tia-004.vpn.privado.io: lookup tia-004.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving dtw-002.vpn.privado.io: lookup dtw-002.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving bru-001.vpn.privado.io: lookup bru-001.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving dtw-007.vpn.privado.io: lookup dtw-007.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving dub-003.vpn.privado.io: lookup dub-003.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving ord-084.vpn.privado.io: lookup ord-084.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] reached the maximum number of consecutive failures: 2 failed attempts resolving arn-001.vpn.privado.io: lookup arn-001.vpn.privado.io on 127.0.0.1:53: dial udp: lookup 1.1.1.1:53: no such host
2024-02-18T00:39:04+01:00 WARN [updater] note: if running the update manually, you can use the flag -minratio to allow the update to succeed with less servers found
Share your configuration
No response
The text was updated successfully, but these errors were encountered:
True. Privado changed again the hostnames, back to zrh-00(5-8).vpn.privado.io.
See #2117
The current servers.json is up to date, at least for Privado Switzerland.
I can try to reproduce it by replacing the servers.json with an older one, i.e. from commit 8a17cd8
to see if it updates from zrh-00(1-4) to zrh-00(5-8) .... will do it this weekend.
No need to manipulate servers.json manually... hostnames for Zurich changed again.
At the moment the following are included in the Privado config file
zrh-009.vpn.privado.io
zrh-010.vpn.privado.io
Expected update: from zrh-00(5-8) to zrh-0(09-10)
Periodically update did not work (with UPDATER_MIN_RATIO=0.1), servers.json is unchanged.
Manual update works with
docker run --rm -v /yourpath:/gluetun qmcgaw/gluetun update -enduser -providers privado -minratio 0.1
-> servers.json includes only zrh-0(09-10)
Slightly off-topic:
Again, these VPN server (zrh-0(09-10)) are not in Switzerland, see also discussion #2117
And zrh-00(5-8) can still be used even it is not listed in the Privado config file anymore...
Is this urgent?
No
Host OS
No response
CPU arch
None
VPN service provider
Privado
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-02-14T07:39:38.933Z (commit 423a5c3)
What's the problem 🤔
There are new hostnames for Privado VPN server in "Switzerland" based on https://privadovpn.com/apps/ovpn_configs.zip
zrh-0(09-12).vpn.privado.io
Current servers.json includes
zrh-00(5-8).vpn.privado.io
Activated periodically update with UPDATER_PERIOD=5m and it runs without an error. But servers.json remains unchanged.
Also tried UPDATER_MIN_RATIO=0.1 (beside the default 0.8)
Manual update works with docker run --rm -v /yourpath:/gluetun qmcgaw/gluetun update -enduser -providers privado
Share your logs (at least 10 lines)
Share your configuration
No response
The text was updated successfully, but these errors were encountered: