-
-
Notifications
You must be signed in to change notification settings - Fork 329
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: gluetun and another Wireguard kills all #2268
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
You could try with |
Is this urgent?
None
Host OS
No response
CPU arch
x86_64
VPN service provider
Mullvad
What are you using to run the container
docker-compose
What is the version of Gluetun
latest built on 2020-03-13T01:30:06Z (commit d0f678c)
What's the problem 🤔
I want to route all the traffic thru "wireguard", but use a VPN to reach that server.
Since gluetun is using
WIREGUARD_ALLOWED_IPS=0.0.0.0/0
, when the 2nd docker tries to do the same, it kills the routing of gluetun.So I tried to WIREGUARD_ALLOWED_IPS=<IP_OF_MY_WG/32>, but then nothing works.
What would you recommend?
Thank you.
EDIT: probably same as #2086 ?
Share your logs (at least 10 lines)
dead here.
The text was updated successfully, but these errors were encountered: