-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: OpenVPN no client-side authentication method is specified. #2217
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
I have multiple Gluetun instances running in my environment. I've left one running with the image noted above and it just barfed. Full log is attached. Other instances are using Here's a snippet with debug on:
You'll see alot of:
in this log. I'm used to this and it comes up regularly in normal, non-disrupted operation. I run automated speed tests every so often.
|
The problem is really just an OpenVPN problem:
I just ran Mullvad+Openvpn successfully with the latest image, are you sure it's not a configuration error? The configuration you shared indicates |
I'm unsure how to match up current tags with commit 7b4befc. I've had v3 running since the time I mentioned this. I just tested with latest, gluetun:test, gluetun:v3.38, v3.37 and was unable to reproduce. What I recall from the event on Apr 8 inspiring this report is a restart of multiple containers with the exact configuration shown above. All containers then failed with the logs included earlier. Confidence is very high this wasn't a configuration issue. Since this can't be reproduced at this time, I'd be fine with closing the issue. However, I'd really like to know if there's a practical means of following a commit id (ie, 7b4befc) to a digest reference, specific image tag, or whatever was 'latest' at that time. This has been an ongoing knowledge gap of mine that I'd like to address. If you could show me how to do that I'd be happy to test against that image. If no reproducer, then I'll close in spite of the mysterious nature. |
It was likely due to a large settings refactoring I've done starting with ecc80a5 about a month ago. It should be all fixed up now given there is no directly related issue report about it for now. If it's working now, let's just move on and close this, since that was on the latest image and it's now fixed (this would different if it would be a tagged "more-stable" image such as
The git commit is injected as a docker build argument from the automated build system and is set in the Gluetun Go program at compilation time (here), and is also set as a the
Note the revision has to be the full git commit hash digest, not just the first 7 characters. Although I have no idea how to find that image on Gchr or docker hub once it's deleted locally, I would even say it's likely impossible at this time. But it's still re-buildable too! For example: docker build -t qmcgaw/gluetun https://github.com/qdm12/gluetun.git#7b4befce61a56d945c3558188d79a856ba22880a |
Closed issues are NOT monitored, so commenting here is likely to be not seen. This is an automated comment setup because @qdm12 is the sole maintainer of this project |
Is this urgent?
Yes
Host OS
Ubuntu 22.04.4
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 2024-04-08T07:43:05.096Z (commit 7b4befc)
What's the problem 🤔
I'm near certain this is a new bug. I have no openvpn configuration. I can't spot it exactly (go weakling here) but there are references to openvpn here: 7b4befc
qmcgaw/gluetun:latest (note digest match):
https://hub.docker.com/layers/qmcgaw/gluetun/latest/images/sha256-bfcf38ffbfbb2f5668e9f718e461b013ca6917129df34ae7a76ad5343fcf35fe?context=explore
I just turned on
LOG_LEVEL=debug
to get more details. Will update when available.Also, will determine if there's a tag to use to avoid this. Could be
qmcgaw/gluetun:v3
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: