Status - is empty list - Githubissues

ngoduykhanh / wireguard-ui

Wireguard web interface

MIT License

4.03k stars 498 forks source link

Status - is empty list #556

Open bukiru opened 6 months ago

bukiru commented 6 months ago

Wireguard UI ver v0.6.2 Connected Peers - nothing in list, it's empty. But lots of clients are connected

bserret commented 6 months ago

I am seeing the same thing

bserret commented 6 months ago

clients show in a list on status but there is no traffic listed despite them all working

eliasmainetti commented 5 months ago

clients show in a list on status but there is no traffic listed despite them all working

same for me

bukiru commented 5 months ago

@ngoduykhanh

nfs-aaronmower commented 3 months ago

@bukiru @bserret

Make sure that your docker file has the following:

################## version: '3.8'

services: wireguard-ui: image: ngoduykhanh/wireguard-ui:latest container_name: wireguard-ui cap_add:

NET_ADMIN # Required to show active clients user: root
use the network of the host. this enables to show active clients in the status page (I have Wireguard installed on my host machine, if you have it as another docker container then it would be: 'network_mode: service:wireguard'

network_mode: host environment: ... ... ...

And most importantly don't have any ports: listed in your docker-compose file. I commented mine out.

bukiru commented 3 months ago

@bukiru @bserret

Make sure that your docker file has the following:

################## version: '3.8'

services: wireguard-ui: image: ngoduykhanh/wireguard-ui:latest container_name: wireguard-ui cap_add: - NET_ADMIN # Required to show active clients user: root # use the network of the host. this enables to show active clients in the status page (I have Wireguard installed on my host machine, if you have it as another docker container then it would be: 'network_mode: service:wireguard' network_mode: host environment: ... ... ...

And most importantly don't have any ports: listed in your docker-compose file. I commented mine out.

I don't use docker, only binary

krolingo commented 3 months ago

Any way around this using binary and not docker? I run it on FreeBSD

bukiru commented 3 months ago

I've found 2 two ways to solve the problem:

Zabbix (I have added some items to my template and created custom dashboard)
https://www.procustodibus.com/blog/2021/01/how-to-monitor-wireguard-activity/#pro-custodibus COMMUNITY EDITION is free and completely enough up to 5 hosts e.g. wg-servers

TimChaubet-I4U commented 1 month ago

This cap_add: - NET_ADMIN works indeed if wireguard is installed on the host. However, when you run 2 containers, the 'network_mode: service:wireguard' makes no sense, when you're using the bridged or any other network.