-
-
Notifications
You must be signed in to change notification settings - Fork 360
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: Control Server is broken for Wireguard (works only for OpenVPN) #2438
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
Which route are you using to (re)start wireguard through the control server? |
Hi Quentin, latest behaves the same as log above, but attaching full log using latest for your reference. > curl -X PUT http://localhost:8005/v1/openvpn/status -H "Content-Type: application/json" -d '{"status": "stopped"}'
{"outcome":"stopped"}
> curl -X PUT http://localhost:8005/v1/openvpn/status -H "Content-Type: application/json" -d '{"status": "running"}'
{"outcome":"crashed"} |
The documentation was a bit wrong, this is fixed in qdm12/gluetun-wiki@4a00757 There are routes defined in the code but not documented, because they are subject to change without notice (notably #2238):
These are likely to stay, but default no-access-without-user-defined-authentication might be set on them soon, and the settings JSON object might change in the future, as long as these routes are not documented still. Once it's documented it will stay retro-compatible. |
Hi, so the endpoint was renamed from Since you made the wise choice of starting off with api versioning, if you change the API it would really make sense to use Also #2238 doesn't make sense I think there is a typo? |
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 |
In spirit of easier maintainability, asking for backwards compatibility for undocumented api is a bit much don't you think? @Aubermean |
You are mistaken, the API has never been undocumented. The API /v1/ had its endpoints changed completely and silently and the documentation was not updated. Speaking of easier maintainabilitiy, the solution is definitely not everyone having 'a test suite on their end'. The solution is:
|
Is this urgent?
Yes
Host OS
No response
CPU arch
aarch64
VPN service provider
Custom
What are you using to run the container
docker-compose
What is the version of Gluetun
2024-03-07T12:32:25.391Z (commit 3254fc8)
What's the problem 🤔
Using the Control Server, trying to 'start' a wireguard server results in some bug whereby it switches over to openvpn and the container needs restarting.
This version works: 2024-03-07T12:32:25.391Z (commit 3254fc8)
the latest, v3.39, v3.38, v3.37 tags do not work.
I don't use OpenVPN, I never have. The commit tag above works fine, this log I am adding is from the latest versions so you can see it decides to switch to openvpn after i stop-start via control server.
Share your logs (at least 10 lines)
Share your configuration
no
The text was updated successfully, but these errors were encountered: