Page 1 of 1

Optional environment variables

Posted: Wed Jun 19, 2024 8:52 pm
by rhodes

Hello,

and thanks very much for sharing/maintaining your project.

During my initial install the vpn-setup failed, so I had to do the Manual configuration.
Using the recommended vpn-provider, I hoped to end up in their country or at least on one of the servers they own.
This was not the case; ended up in a city they do not even list on their server page. I tried using the Optional environment variables mentioned in the gluetun-wiki

Code: Select all

- SERVER_CITIES=<CityFromTheirServerList> qmcgaw/gluetun

or

Code: Select all

- OWNED_ONLY=yes

No success in getting the container running after editing.

Since the device with openvpn does not log into the official provider-app or use a generated configuration file, it does not show on the My devices on the provider-website.
Is there any way to influence the server city or server ownership.

Sorry, for being annoying.


Re: Optional environment variables

Posted: Wed Jun 19, 2024 10:52 pm
by rogs

Hey @rhodes!

You aren't being anoying at all :mrgreen:

YAMS is currently using an old version of Gluetun that might use a different documentation. Try removing the gluetun version pin in the docker-compose (everything after the : including the :).

We've had some instability issues with the newer versions though! But try that and see if it works for you.

Also, you might find more help in our Discord server! You can join here: https://discord.gg/Gwae3tNMST

Cheers!


Re: Optional environment variables

Posted: Sun Jun 23, 2024 7:09 pm
by rhodes

Thanks.

Enabling the option

Code: Select all

- OWNED_ONLY=yes

works. the qbt-container runs. The other option does not work.

During the mentioned "instability issues", some kill-switch function keeps working?


Re: Optional environment variables

Posted: Sun Jun 23, 2024 8:15 pm
by rogs

As far as I know, the kills witch has always worked, the issues we were having were mostly instability stuff and some VPNs downright not working