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.62k stars 312 forks source link

Recent changes don't work #112

Open Junkkk opened 7 months ago

Junkkk commented 7 months ago

I tried to up a new version and nothing worked out for me. last commit hash: 74c4c9c

BeansIsFat commented 7 months ago

There was a change in the wireguard image that broke wireguard-ui. Until there's an upstream fix the current commit of wirehole won't work. Going back to the last release (9f074f4) that used wg-easy seems to work for me. Use git reset --hard 9f074f4.

You can go back to commit https://github.com/IAmStoxe/wirehole/commit/4d8686b0498aa46783fc0936f0bc7d49070b2803 if you want to use wirehole before any of the web config interfaces were added.

Nezteb commented 7 months ago

Dupe of https://github.com/IAmStoxe/wirehole/issues/111

m-karakus commented 7 months ago

try to update your .env file, on my case wireguard mandatory parameters were missing. I added these lines to .env

# Wireguard settings
TZ=Europe/Istanbul
PUID=1000
PGID=1000
SERVERURL=auto  #wireguard.domain.com #optional
SERVERPORT=51820 #optional
PEERS=5 #optional
PEERDNS=10.2.0.100

And the volume path for the wireguard-ui should be like this 

  wireguard-ui:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wireguard-ui
    depends_on:
      - wireguard
    cap_add:
      - NET_ADMIN
    network_mode: service:wireguard
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - ./db:/app/db
      - ./config/wg_confs:/config
    env_file: .env
digitalextremist commented 7 months ago

Thanks @m-karakus: That seems to have resolved the issue for me.

I did need to also add to .env at least this:

INTERNAL_SUBNET=

And in docker-compose.yml I added the network to the wireguard container, otherwise unbound and pihole were unreachable.

Does not feel very stable yet, and seeing weird variations between peers.

m-karakus commented 7 months ago

guys, I forked the project solved some issues, and tried to make it much easier for the user. If you want you can check it from here https://github.com/m-karakus/wirehole

KvizadSaderah commented 7 months ago

try to update your .env file, on my case wireguard mandatory parameters were missing. I added these lines to .env

# Wireguard settings
TZ=Europe/Istanbul
PUID=1000
PGID=1000
SERVERURL=auto  #wireguard.domain.com #optional
SERVERPORT=51820 #optional
PEERS=5 #optional
PEERDNS=10.2.0.100

And the volume path for the wireguard-ui should be like this

  wireguard-ui:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wireguard-ui
    depends_on:
      - wireguard
    cap_add:
      - NET_ADMIN
    network_mode: service:wireguard
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - ./db:/app/db
      - ./config/wg_confs:/config
    env_file: .env

with that peers created, but connection not working :|