You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
gluetun | 2024-06-15T13:14:45+10:00 ERROR VPN settings: OpenVPN settings: custom configuration file: extracting information from custom configuration file: extracting connection from file: on line 24: extracting from remote line: remote line has not 2 fields as expected: remote 103.108.229.98 443 # au-mel-ovpn-302
gluetun | 2024-06-15T13:14:45+10:00 INFO Shutdown successful
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:
# au-mel-ovpn-302
remote 103.108.229.98 443
However, the next snag comes up immediately after:
gluetun | 2024-06-15T13:12:09+10:00 ERROR [openvpn] No client-side authentication method is specified. You must use either --cert/--key, --pkcs12, or --auth-user-pass
gluetun | 2024-06-15T13:12:09+10:00 INFO [openvpn] Use --help for more information.
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:
auth-user-pass /gluetun/mullvad_userpass.txt
(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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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.
All reactions