Closed geekau closed 3 weeks ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
Just a minor correction to the original submission above...
The only way we can get Gluetun to deploy without error is to revert back to using the original OPENVPN_USER and OPENVPN_PASSWORD variables, and remove all of the "SERVER" variables, except for SERVER_REGIONS=$(SERVER_REGIONS).
The combination below appears to be our only working config.
- OPENVPN_USER=${VPN_USERNAME:?err}
- OPENVPN_PASSWORD=${VPN_PASSWORD:?err}
# - SERVER_COUNTRIES=$(SERVER_COUNTRIES)
- SERVER_REGIONS=$(SERVER_REGIONS)
# - SERVER_CITIES=$(SERVER_CITIES)
# - SERVER_HOSTNAMES=$(SERVER_HOSTNAMES)
# - SERVER_CATEGORIES=$(SERVER_CATEGORIES)
Link to same bug reported in our project: https://github.com/geekau/mediastack/issues/16
We have a workaround until bug is fixed.
WARN You are using the old environment variable OPENVPN_USER, please consider changing it to VPN_PORT_FORWARDING_USERNAME WARN You are using the old environment variable OPENVPN_PASSWORD, please consider changing it to VPN_PORT_FORWARDING_PASSWORD
This is a bug introduced 2 weeks ago in 05017438145d4ed458eeaa185f981662147c05cb and resolved just now with a03041cfea85b670c1c84d6cfbee3a60fdde55b1 my apologies! You should use OPENVPN_USER
and OPENVPN_PASSWORD
, not the other ones.
However, we're getting the following error on value $(SERVER_COUNTRIES):
Ok this is getting interesting. I just saw this in another issue #2367 so it might be a bug. Settings reading might had changed a lot in the last 2 years though, and it looks like Gluetun doesn't like shell variables (it reads them raw without shell). Does this problem still happen for the tags :v3.37
and :v3.38
?
Actually I am trying to use his project with hidemyass vpn :) and I am getting this error.
OK, think I have all of this figured out... not a Gluetun bug.
When I returned to project after a little hiatus, I added the SERVER* variables to our project, but made 2 minor errors:
I corrected the syntax of the variables and noticed the errors where still occurring, however the error logs now showed the "# comments section" from the .ENV file, so that was easy to find / remove.
NEW YAML:
- OPENVPN_USER=${VPN_USERNAME:?err}
- OPENVPN_PASSWORD=${VPN_PASSWORD:?err}
- SERVER_COUNTRIES=${SERVER_COUNTRIES}
- SERVER_REGIONS=${SERVER_REGIONS}
- SERVER_CITIES=${SERVER_CITIES}
- SERVER_HOSTNAMES=${SERVER_HOSTNAMES}
- SERVER_CATEGORIES=${SERVER_CATEGORIES}
NEW ENV:
# You MUST provide at least one entry to the SERVER variables below, that supports your VPN provider's settings.
# If you want to add more than one entry per line, use comma separated values: "one,two,three" etc...
SERVER_COUNTRIES=
SERVER_REGIONS=Europe
SERVER_CITIES=
SERVER_HOSTNAMES=
SERVER_CATEGORIES=
I'll set Europe as the default REGION, so if our users don't update their VPN info, it should be enough for most users to still work.
I've tested this update a bit, and is working as expected, only need to populate one of the variables with a valid option from the servers.json, and it connects to one of the entries, and provide feedback in the log (getter ip).
I've notice Gluetun doesn't like comments after variable=values, this is fine, we can handle this and provide feedback to our users.
Can also confirm the WARN messages have been resolved with https://github.com/qdm12/gluetun/commit/a03041cfea85b670c1c84d6cfbee3a60fdde55b1
@Yakrel I have pushed update to repo https://github.com/geekau/mediastack/commit/3acad522d6aaff9f6c223a7dde108f8e1aa3e439 can you check, it may resolved the bug you logged.
Thanks @geekau for the detailed response, let's close this 👍
I'll set Europe as the default REGION, so if our users don't update their VPN info, it should be enough for most users to still work.
Actually, not setting anything works, a server is picked at random from the pool of servers. These are all optional filters.
Also, one more thing, you might want to pin your Gluetun docker image tag to v3.39.0 once it releases (soon ™️), since the latest image is a bit of a release candidate and prone to be buggier than tagged releases.
Closed issues are NOT monitored, so commenting here is likely to be not seen. If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project which became too popular to monitor issues closed.
Is this urgent?
No
Host OS
Ubuntu Desktop 24.04 LTS x64
CPU arch
x86_64
VPN service provider
NordVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-07-12T19:57:02.146Z (commit 9d50c23)
What's the problem 🤔
We've just updated our project files after 2 years to accommodate the new Docker Compose 2, and to include updated $Variables from Gluetun wiki, however we are having issues with getting the Gluetun container to start with the new set of $Variables.
We've added $Variables into our ENV file, referencing the Gluetun NordVPN wiki: https://github.com/qdm12/gluetun-wiki/blob/main/setup/providers/nordvpn.md
Our updated ENV and YAML files are listed in full at the bottom, however the specific updates to the files are:
UPDATED ENV:
UPDATED YAML:
The stack is started with the following command.... removing the "-d" when we're debugging:
However, we're getting the following error on value $(SERVER_COUNTRIES):
It doesn't seem to matter what SERVER_COUNTRIES we use, it always throws the same error.
Further, If we comment out the SERVER_COUNTRIES=$(SERVER_COUNTRIES) line from the YAML file, then we get the following error from the next listed variable in the YAML file. Again, it doesn't seem to matter what SERVER_CITIES we use, it always throws the same error.
The only way we can get Gluetun to deploy without error is to revert back to using the original OPENVPN_USER and OPENVPN_PASSWORD variables, as per below.
Then we go back to the original WARNING messages in the logs, asking to update to the new variables.
We have Gluetun running for the time being, however we'd like to make sure our users have an easy implementation to keep their issues down.
Thanks for the app and your support.
Share your logs (at least 10 lines)
Share your configuration