-
-
Notifications
You must be signed in to change notification settings - Fork 334
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
Comments
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 You can go back to commit 4d8686b if you want to use wirehole before any of the web config interfaces were added. |
Dupe of #111 |
try to update your # 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 |
Thanks @m-karakus: That seems to have resolved the issue for me. I did need to also add to
And in Does not feel very stable yet, and seeing weird variations between peers. |
guys, I forked the project solved some issues, and tried to make it much easier for the user. |
with that peers created, but connection not working :| |
I tried to up a new version and nothing worked out for me.
last commit hash: 74c4c9c
The text was updated successfully, but these errors were encountered: