Closed karserasl closed 1 year ago
Same to me right now!
I had to remove SERVER_COUNTRIES
and SERVER_CITIES
to make it work again!
Same issue here, latest update broke something.
rolling back to 3.34 works in the mean time
Yea im using the tagged v3 image and waiting to upstream fixes
Pretty certain that this commit: https://github.com/qdm12/gluetun/commit/a43973c093662c2b5521eb2e9e3aea053584e96b#diff-e614e18f3fe5d5bdbace977e5feeb42a34c6fd5adbcd469c8cd2ed161acfc885
with a move to gosettings
has made reading the env ignore case.
Yea im using the tagged v3 image and waiting to upstream fixes
how exactly can i revert using docker?
rolling back to 3.34 works in the mean time
how exactly can i revert using docker?
how exactly can i revert using docker?
Instead of tag :latest use :v3.34
the same for nordvpn:
VPN_SERVICE_PROVIDER=nordvpn
SERVER_REGIONS=Netherlands
ERROR VPN settings: provider settings: server selection: for VPN service provider nordvpn: the region specified is not valid: value is not one of the possible choices: value netherlands, choices available are Albania, Argentina, Australia, Austria, Belgium, Bosnia and Herzegovina, Brazil, Bulgaria, Canada, Chile, Costa Rica, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Georgia, Germany, Greece, Hong Kong, Hungary, Iceland, India, Indonesia, Ireland, Israel, Italy, Japan, Latvia, Lithuania, Luxembourg, Malaysia, Mexico, Moldova, Netherlands, New Zealand, North Macedonia, Norway, Poland, Portugal, Romania, Serbia, Singapore, Slovakia, Slovenia, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, Thailand, Turkey, Ukraine, United Kingdom, United States, Vietnam
Also see same issue with VPN Unlimited. Running version latest built on 2023-05-25T12:12:44.932Z (commit a43973c)
2023-05-26T09:14:05-04:00 ERROR VPN settings: provider settings: server selection: for VPN service provider vpn unlimited: the country specified is not valid: value is not one of the possible choices: value france, choices available are Argentina, Australia, Austria, Belarus, Belgium, Bosnia and Herzegovina, Brazil, Bulgaria, Canada, Costa Rica, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, India, Ireland, Isle of Man, Israel, Italy, Japan, Korea, Kuala Lumpur, Latvia, Libya, Lithuania, Mexico, Moldova, Netherlands, New Zealand, Norway, Oman, Poland, Portugal, Romania, Serbia, Singapore, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Thailand, Turkey, United Arab Emirates, United Kingdom, United States, Vietnam
following
Same issue here
having this issue as well. downgrading to v3.34 has mitigated the issue.
Issue also exists for Private Internate Access. Downgrading to v3.34 fixed the issue for me aswell.
Same issue here with Mullvad and "Montreal" being downcased to "montreal" and causing failure.
Same issue with Mullvad and SERVER_CITIES
Same here with Private Internet Access
Same issue here. Mullvad with value SERVER_CITIES=Amsterdam
Confirmed, but I ended up changing my docker compose file for gluetun and qbittorrent to image: qmcgaw/gluetun:v3.34
deleting the container and running docker-compose -f /volume1/docker/qbittorrentvpn.yml up -d
I question why I would need to update if it currently works fine, and updates (like this one) break things? It's like Plex updates, a giant lottery if the server suddenly stops working properly.
I also had the wonderful bug where callmebruce fork of Nightwalker stopped letting me access qbittorrent through the webui, so I have had to revert to the default theme. So I had two things that broke.
Well keeping things up to date is good practice in general, from a security point of view of course, but also as gluetun constantly changes the server list to keep up with changes in the VPN landscape.
In years of using gluetun, this is the first issue Iβve seen.
On Fri, 26 May 2023, at 23:36, Neobond wrote:
Confirmed, but I ended up changing my docker compose file for gluetun and qbittorrent to
image: qmcgaw/gluetun:v3.34
deleting the container and runningdocker-compose -f /volume1/docker/qbittorrentvpn.yml up -d
I question why I would need to update if it currently works fine, and updates (like this one) break things? I(t's like Plex updates, a giant lottery if the server suddenly stops working properly.
I also had the wonderful bug where callmebruce fork of Nightwalker stopped letting me access qbittorrent through the webui, so I have had to revert to the default theme. So I had two things that broke.
β Reply to this email directly, view it on GitHub https://github.com/qdm12/gluetun/issues/1599#issuecomment-1565032317, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEEI24WXDNXSDHVVCAU3BT3XIEV5PANCNFSM6AAAAAAYOZ5K6I. You are receiving this because you commented.Message ID: @.***>
The latest image qmcgaw/gluetun
was fixed a few minutes ago by 7e325715c7a24da73447b29cec94b207bd950745.
The regression was introduced 2 days ago with a43973c093662c2b5521eb2e9e3aea053584e96b which did compare text taking care about case sensitivity (gluetun lowercases everything inputted, but keeps servers data text with case sensitivity). My apologies for the delay fixing it, obviously, and thank you for reporting the issue ποΈ
Just in case you are not aware, you can use released docker images such as qmcgaw/gluetun:v3
or qmcgaw/gluetun:v3.34.1
which should be more stable than the latest image qmcgaw/gluetun
. I always appreciate users using the latest image since this helps fix bugs before bringing them to a stable release which would end up unstable, so ideally keep using the latest image π
qmcgaw/gluetun:v3
Does qmcgaw/gluetun:v3
reference stable? Sorry I just have a NAS for my media server and use tutorials to install these things. π
qmcgaw/gluetun:v3
Does
qmcgaw/gluetun:v3
reference stable? Sorry I just have a NAS for my media server and use tutorials to install these things. π
tl;dr for your use case qmcgaw/gluetun:v3.34.1
would be considered the latest stable version.
@qdm12, I believe follows a Semantic-ish versioning method. Where, for example using v3.34.1, v3 would be the Major release version number, 34 is the Minor version number, and 1 is the Patch version number.
If you are using qmcgaw/gluetun:latest
, you will receive all alpha/beta/rc releases in between the more stable major, minor, or patch release. Unless you are running a business that requires as little downtime as possible the latest patch release (v3.34.1) should be sufficient for reliable stability. Whereas the aforementioned business would likely opt for either the major (v3) or minor (v3.34.0) for greater stability. I, personally, can't recount many, if any at all, times where a patch release of gluetun was broken. I'm sure I'm wrong but I'm not far off if I am.
IMHO, homelabs, unless running a business, should be fine running the latest patch release is more than sufficient. Personally, most of my containers run on :latest
. Homelabs are supposed to be fun and exciting, right? π Plus, you get the added benefit of supporting and being a part of an amazing community.
Is this urgent?
No
Host OS
Arch
CPU arch
x86_64
VPN service provider
Mullvad
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2023-05-25T12:12:44.932Z (commit a43973c)
What's the problem π€
Latest commit i think it uses only lower case server cities/countries, which breaks the check.
Share your logs
Share your configuration