Skip to content
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

Wireguard UI unreachable when used with network_mode: service:wireguard #125

Open
UltraBlackLinux opened this issue Mar 1, 2024 · 2 comments

Comments

@UltraBlackLinux
Copy link

UltraBlackLinux commented Mar 1, 2024

Hey there,
I cannot for the life of me get the network_mode: service:wireguard statement to work. Whenever I insert that, the ports setting cannot be added to the wireguard-ui container, so you'd expect it to be accessible from within the wireguard container, but wrong. The request simply times out, or maybe you get a broken response (curl exits immediately, firefox loads for a long time), even with the correct port setting added to the wireguard container instead.
Any idea what's going on here? The config is basically stock, but this just does not want to work. I'm confused

@matijs-toonen
Copy link

matijs-toonen commented Aug 1, 2024

Hey,
While I was setting this docker compose up I experienced the same thing.
The following solution worked for me, perhaps you can try that.

ngoduykhanh/wireguard-ui#473 (comment)

PEERS=1

This ^ is missing inside the .env.example file, after I added this I was able to access the wireguard ui (with all other other settings left default).

Hopefully this also works for you

@UltraBlackLinux
Copy link
Author

unfortunately I just ended up switching to wg-easy and ditched pihole and unbound entirely.

Very nice that you managed to figured it out though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants