-
-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: PIA random server picked even with SERVER_CITIES
set
#849
Comments
Hello there! That's weird, is it the same behavior with image Gluetun takes care of validating pretty much any settings you set and they are printed out correctly; it might be a problem further downstream in the code, but it looks fine from a quick look at it. |
Salut! It only started doing it today (well late last night according to the logs). I'll try the image tags and report back. I wish the version info included the version number, not just the date and commit. I can never tell the actual version number I'm running, unless I'm missing looking somewhere. In the log, you give the version number of everything EXCEPT GlueTun itself lol. Ahh I see it does show a version number when using an image tag, but on latest it just shows 'You are running on the bleeding edge of latest'. Could you show the version number in that message please? |
v3.27.0 - same thing
v3.26.0 - same, but worse
et ça continue comme ça |
v3.25.0 - yikes!
v3.24.0 - Why ProtonvpnServer??? I'm using PIA. Btw PIA on my Windows desktop (not using a Gluetun container, using the PIA app) is working fine with AU Melbourne server. |
Back to v3.27.0
I've been getting these out of the blue Caught OS signal, shutting down quite a bit lately. |
They do for tagged images. There is no version number for untagged images (latest), although it tells you how far away it is from the latest release once the vpn sets up. Maybe more info could be written in the program though.
you need to use
Because it reads the entire servers.json you have bind mounted and gluetun is retro-compatible from okder to newer versions but not really the other way around 😄 There probably was a change in the protonvpn servers data scheme.
Yeah definitely a problem with gluetun. I'm just trying to figure out when it got introduced.
That's coming from the docker daemon or your OS. You probably are running low on memory? Note gluetun uses 300MBish of ram due to the Unbound block lists, see #813 Anyway, try again previous release image tags with |
Regarding the error you got in v3.25.0 |
SERVER_CITIES
set
Actually PIA only supports Where did you find out about |
It came up in the log. I just happened to notice that a couple of environment variables were flagged as deprecated (not sure what the exact word was now) and that made me decide to use the new ones. Would it make sense to redirect Are you still using Mullvad? And would you recommend it over PIA? If so, why? I ask because it's more expensive. If you prefer, you can message me privately (my github name at live dot com dot au). Merci! |
Yes good point, it's because I changed the code to have the reading of settings decoupled from the validation of settings, and also each 'part' of the reading is quite independent. So gluetun will pretty much eat whatever setting is available even if it doesn't need it (such as
Yes done in a4652c2 for the latest image, it will now error out if you set a server filter variable for a provider that doesn't support it. I think that would be clearer than logging a warning for now, to avoid any confusion.
Yes I'm still with Mullvad. Mullvad supports OpenVPN, Wireguard, IPv6, port forwarding, static IP addresses, their API is great and they have been reliable for a few years now; it's really the perfect gluetun candidate 😄. Next would be Ivpn and then Windscribe which are also great from my 'coding' experience integrating them. And then the rest crossing my mind:
De rien! 😉 |
Is this urgent?
No
Host OS
Synology 920+
CPU arch
x86_64
VPN service provider
Private Internet Access
What are you using to run the container
docker-compose
What is the version of Gluetun
2022-02-13T01:25:21.776Z (commit c40d4e0)
What's the problem 🤔
Even though I've set SERVER_CITIES in my docker-compose file to AU Melbourne or AU Melbourne,AU Sydney (I also tried AU_Melbourne or AU Melbourne,AU_Sydney), I've started to get random cities assigned (see logs of two separate runs).
Share your logs
Share your configuration
The text was updated successfully, but these errors were encountered: