Closed CplPwnies closed 6 months ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
Set the environment variable WIREGUARD_CONF_SECRETFILE
to /gluetun/wireguard/wg0.conf
as a workaround.
setting WIREGUARD_CONF_SECRETFILE didn't work for me either with the latest pull, but I changed my compose file to mount the volume like this and it worked
Thanks for reporting this, working on it! It's due to a rather large config rework in ecc80a5a9e3f5ba8c3096eb47c9ed8544a7e8867
You can revert to v3.38.0 for the time being, which is just before this commit.
Fixed in e01ce9c6d87172f565b813523314daba7ebb2c5b
The path was changed to /gluetun/wg0.conf
, it's now fixed to be back to /gluetun/wireguard/wg0.conf
by default.
Closed issues are NOT monitored, so commenting here is likely to be not seen. If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project which became too popular to monitor issues closed.
6b2f350ec960a8e07fd1a78fd180260645f1b25e should also further resolve this.
Is this urgent?
Yes
Host OS
Debian Bullseye
CPU arch
x86_64
VPN service provider
Custom
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-03-25T19:19:45.506Z (commit ecc80a5)
What's the problem 🤔
I have a gluetun container where I map in a wg0.conf file instead of defining all the wireguard env variables, and the latest docker container build seems to be ignoring the mapped wg0.conf file and looking for the env variables, then stopping when it does not find them.
Share your logs (at least 10 lines)
Share your configuration