Closed dokzlo13 closed 3 months ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
Thanks for reporting this with such great details 💯 👍 TLDR: Fixed in e859c603430628c7cfbf84d29bcc66878a0632be
The longer story: This is due to a rather large refactor I've done recently to the configuration reading code. For v3.38.0 and before, it was:
environment variables would reject an address without a /bits
suffix (usually /32
for a single address):
reading from the Wireguard config file would auto-add a /32
if no /
would be found in the address
So all in all, rather inconsistent.
Now it will auto-add the /32
suffix for everything, so it's consistent and it maintains retro-compatibility.
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.
Is this urgent?
No
Host OS
Synology DSM
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-26T07:27:44.668Z (commit 6b2f350)
What's the problem 🤔
After automatic (with watchtower, sorry because of it I don't track last working version of gluetun) update to new version of the gluetun, custom wireguard configuration stops working without any changes in the config file. Here wireguard config:
gluetun provides this log line with error:
Seems like
Interface.Address
field parsing logging was changed. The possible workaround, which fixes config parsing is:Seems like only IP part is required for gluetun to operate normally, but mask is now required for IP parsing.
Share your logs (at least 10 lines)
Share your configuration
synobridge
network configured by this guide