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

Recent changes don't work #112

Open
Junkkk opened this issue Nov 11, 2023 · 6 comments
Open

Recent changes don't work #112

Junkkk opened this issue Nov 11, 2023 · 6 comments

Comments

@Junkkk
Copy link

Junkkk commented Nov 11, 2023

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

@BeansIsFat
Copy link

BeansIsFat commented Nov 12, 2023

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 4d8686b if you want to use wirehole before any of the web config interfaces were added.

@Nezteb
Copy link

Nezteb commented Nov 14, 2023

Dupe of #111

@m-karakus
Copy link

m-karakus commented Nov 15, 2023

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
Copy link

digitalextremist commented Nov 20, 2023

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
Copy link

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
Copy link

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 :|

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

6 participants