OpenVPN configuration files not parsed correctly? #2321
-
I am attempting to use the "custom" configuration for mullvad, as the "mullvad" configuration only accepts the username, and not the openvpn config and certificate provided by mullvad. OpenVPN by itself on my system parses the file fine, but the gluetun docker container doesn't. One of the first instances of this is when it fails to parse comments:
It is not recognising "#" as a comment marker, and reads the whole line instead, unlike OpenVPN normally does. This can be bypassed by moving the comment to its own line:
However, the next snag comes up immediately after:
This error is false, as this is supplied in the configuration file, and OpenVPN normally does not throw this error outside of gluetun. The config has the line:
(yes, the container can find that file) So there seems to be something wrong with the OpenVPN version, or some config check script gluetun is using, I use OpenVPN 2.6.9 and it works fine. Anyone have a clue on how to approach this if its not reading the config correctly? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Indeed, fixed in dea4080
This is mentioned in https://github.com/qdm12/gluetun-wiki/blob/main/setup/openvpn-configuration-file.md#added-options |
Beta Was this translation helpful? Give feedback.
Indeed, fixed in dea4080
Next time feel free to create an issue since this is actually a bug 😉
This is mentioned in https://github.com/qdm12/gluetun-wiki/blob/main/setup/openvpn-configuration-file.md#added-options
And it's described you should use environment variables for authentication in step 5 of https://github.com/qdm12/gluetun-wiki/blob/main/setup/openvpn-configuration-file.md#setup