search

key-networks / ztncui

ZeroTier network controller UI
GNU General Public License v3.0
1.53k stars 228 forks source link

Peer status #69

Open Semetra22 opened 3 years ago

Semetra22 commented 3 years ago

Members are shown as offline in the peer status, although the device is pingable and reachable via ssh.

Devices without firewall are displayed correctly. Therefore I assume a firewall problem. Which port is used for this? Can someone help here please?

lideming commented 3 years ago

The peer status info in ztncui comes from the controller peers, which is basically the same as running zerotier-cli peers on the controller. The peer is "offline" when it is not connected to the controller. I also see this happen on some online peers sometimes. No idea why :(

smoothdvd commented 3 years ago

Same here.

brutesque commented 2 years ago

Do you have UDP port 9993 inbound open? Possibly your nodes are being routed through the root servers instead of reaching your network controller directly.

brutesque commented 2 years ago

I have done some testing. Also made sure the UDP inbound port was open. But I have some nodes that I know are shutdown, but still report as online. So i'd guess that the peer status in the web interface is not being refreshed at all.

pete1019 commented 2 years ago

Offline issue here as well. Member shows offline but is clearly online.

Maybe because of?

2327bXXXX - LEAF -1 RELAY
einverne commented 2 years ago

Peers can ping, can ssh login, but the status show OFFLINE.

lifansama commented 2 years ago

I have done some testing. Also made sure the UDP inbound port was open. But I have some nodes that I know are shutdown, but still report as online. So i'd guess that the peer status in the web interface is not being refreshed at all.

Do I only open 9993 port enough?

seanbts commented 2 years ago

Would it be worth in ztncui, peer is displayed as relayed instead of offline, this way it would be easy to distinguish between peers relaying and peers that are actually offline? Would this be possible?

squromiv commented 1 year ago

Same problem.

pete1019 commented 1 year ago

Try: https://github.com/dec0dOS/zero-ui

squromiv commented 1 year ago

Try: dec0dOS/zero-ui

Seen this before. This project looks even more glitchy.

pete1019 commented 1 year ago

Try: dec0dOS/zero-ui

Seen this before. This project looks even more glitchy.

Seen it or installed and tested it? Do it.

key-networks commented 1 year ago

Please check if the new package listed at the end of https://github.com/key-networks/ztncui/issues/91 resolves this issue.

key-networks commented 1 year ago

Please try this one after upgrading to ZT 1.10.4:

For DEB: https://key-networks.s3.us-west-1.amazonaws.com/deb/ztncui/1/x86_64/ztncui_0.8.13_amd64.deb

For RPM: sudo dnf --enablerepo=ztncui-testing upgrade ztncui

Please feed back if that helps or not.

mighty-services commented 1 year ago

same here,

I'm using a nginx reverse proxy, and it's happening on the docker-image and on the normal Debian installation package. I'm running an Ubuntu 22.04lts lcx container on Proxmox. I have it tested with and without the Proxmox firewall, and it's still showing offline, even if the peer itself says OK. I have it installed on Proxmox (Debian) and my Windows machine. I can ping between them without problem.

additionally I forwarded 9993 (tcp and udp) without any luck.

Since I followed your tutorial on your webpage, I have already the latest version installed.