search

IAmStoxe / wirehole

WireHole is a combination of WireGuard, Pi-hole, and Unbound in a docker-compose project with the intent of enabling users to quickly and easily create a personally managed full or split-tunnel WireGuard VPN with ad blocking capabilities thanks to Pi-hole, and DNS caching, additional privacy options, and upstream providers via Unbound.
https://iamstoxe.com
Other
4.77k stars 327 forks source link

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

Open UltraBlackLinux opened 8 months ago

UltraBlackLinux commented 8 months ago

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 commented 3 months ago

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.

https://github.com/ngoduykhanh/wireguard-ui/issues/473#issuecomment-1793604986

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 commented 3 months ago

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!