Doh, the warning status is back..

As I understand it, one is the daemon (programdata) and one is the executable to run commands from (sys32)

One of mine has also slipped back to warning. I'm using this one. Still some problems then

A pull makes it healthy again, no errors

are the nodes pingable? I wonder if it's fw issue, any error logs?

No, none on server, none when checking in. I think wg communication is still working but will test properly if it happens again. my impression is that it just stopped checking in

maybe could be a daemon issue then. However the daemon should run a pull "if" it detects a dropped connection

Hmm, just tried netclient on a linux machine and the install went smooth, but when I'm doing a pull it can't resolve grpc.netmaker.mydomain.com, so my issue might be in nginx 🤔 I thought grpc was working as netclient didn't say anything about it when doing a pull. EDIT: Nwm...I'm dumb as usual... did some unrelated fiddling in opnsense which affected

Checking the logs in the wireguard app I can see this:

2022-03-03 17:10:12.206: [TUN] [nm-default] Sending handshake initiation to peer 3 (192.168.3.174:51821)
2022-03-03 17:10:17.210: [TUN] [nm-default] Handshake for peer 3 (192.168.3.174:51821) did not complete after 5 seconds, retrying (try 14)
2022-03-03 17:10:17.210: [TUN] [nm-default] Sending handshake initiation to peer 3 (192.168.3.174:51821)
2022-03-03 17:10:22.353: [TUN] [nm-default] Handshake for peer 3 (192.168.3.174:51821) did not complete after 5 seconds, retrying (try 15)
2022-03-03 17:10:22.353: [TUN] [nm-default] Sending handshake initiation to peer 3 (192.168.3.174:51821)
2022-03-03 17:10:27.426: [TUN] [nm-default] Handshake for peer 3 (192.168.3.174:51821) did not complete after 5 seconds, retrying (try 16)
2022-03-03 17:10:27.426: [TUN] [nm-default] Sending handshake initiation to peer 3 (192.168.3.174:51821)
2022-03-03 17:10:32.597: [TUN] [nm-default] Handshake for peer 3 (192.168.3.174:51821) did not complete after 5 seconds, retrying (try 17)
2022-03-03 17:10:32.597: [TUN] [nm-default] Sending handshake initiation to peer 3 (192.168.3.174:51821)

So the handshake fails. Haven't figured out why though. Seeing the same on the linux machine.

@User have you definitely added the firewall exceptions to your windows machines and forwarded ports if behind NAT? I don't think we're having the same issue at this point

@User , netmaker is running on a VM on my LAN, and my windows machine is on the same LAN. Windows firewall has added exception, and on the netmaker vm machine I ran the

sudo ufw allow proto tcp from any to any port 443 && sudo ufw allow 53/udp && sudo ufw allow 53/tcp && sudo ufw allow 51821:51830/udp

according to the netmaker docs.

Hi, can someone help me? I connected 3 nodes to the same network but from every node I can only ping the netmaker node. all other nodes can't ping each other. i have also reduce the MTU on 1200 (do i neet a reconnect?) but with same behavior. All nodes are windows, two nodes within the same physical LAN, one in a different LAN.

try turning off UDP hole punching. This can cause issues with comms between devices on the same LAN. You can switch it off at the network level (network settings) and it should propagate to nodes

if successful you should see all the ports change to something like 51821

The ports has changed. But ping does not work. neither within same LAN or between different LANs. On netmaker ui the nodes are in normal mode

it looks like the port changed in the peers list but not on the actual machine (look at the listening port in the first section). That should update automatically if you give it a minute, but if it doesn't, run a "netclient pull" on each machine and that should set the correct port

after netclient pull, the interface dosnt come up anymore. I will reinstall netmaker and restart computer and come back again

hmmm ok, do you have the latest netclient? @User hotfixed it yesterday afternoon

you shouldn't need to reinstall Netmaker entirely, but maybe rejoining would be good ("netclient uninstall" --> "netclient join")

There is definitely an issue with Windows we are working through. At least on my test machine it is not receiving peer updates

Are you only seeing this on the windows netclient? I'm having this issue with peers not checking in with the server both on windows and a pop-os machine. None of the nodes have a peer under the comms network interface when running 'wg show'.

that sounds like a separate issue from the windows issue. That one has a fully functional comms network but the regular network doesn't work

maybe run "netclient pull -n " on yours

also, if you have the latest netclient from this morning there's some extra comms troubleshooting stuff in there

I'll try. Did a docker pull today and noticed that comms peers show up in the nodes list in the gui

yup, so now if you have a comms peer that doesnt get delete for some reason, you can delete it manually

the pull didn't work so well...

root@pop-os:/home/seb# wg show
interface: nm-default
  public key: mwEaz+ocb5YL7SknnEfnaQS8IiDWOlHaL/BpoVP47BY=
  private key: (hidden)
  listening port: 51821

interface: nm-l98wNnui
  public key: u/zgiM7SkUlTYo1TKehefmWVvX5914bFnGUNRR5sYws=
  private key: (hidden)
  listening port: 43526
root@pop-os:/home/seb# netclient pull -n nm-l98wNnui
2022/03/08 22:54:56 [netclient] used backup file for network: nm-l98wNnui
2022/03/08 22:54:56 [netclient] reset network and peer configs
2022/03/08 22:54:56 [netclient] error occurred pulling configs from server
2022/03/08 22:54:56 open /etc/netclient/config/netconfig-nm-l98wNnui: no such file or directory

you may need to delete that network adapter and join the comms network manually

Sorry, I realized my mistake

or just uninstall / reinstall on the machine