Do you running NM inside Docker on your server? I use NM with nginx, too.

Hello! I was wondering: What are the benefits of Netmaker when one can also enable Wireguard for flannel-backend in a regular let's say K3s Multi-Cloud environment?

Yes, I start NM with the nm-quick.sh script which is running netmaker, netmaker-ui, mosquito and coredns with docker-compose AFAIK.

It’s gonna be tough running it from the LAN and we don’t really recommend it. Are you port forwarding to give it a public address? I would also recommend turning off UDP hole punching if that is turned on.

Yes, creating nodes in the same LAN maybe isn't optimal...I've been doing that simply to test/get it working. If I get it working I don't really need any nodes on the same LAN 😅 I did however try to add a node using mobile network to not be on the LAN, but didn't get that working either... That's why I'm thinking if I've maybe configured something wrong in Netmaker. Ports forwarded to the Netmaker machine is 53, 51821-51830 and 50051. I can access dashboard.netmaker.mydomain.com etc.

is udp hole punching turned off?

It was turned off for the default network, but not for the comms network.

that should be fine

oh

if you're using the default caddy installation, you'll also need 443

gRPC traffic reaches the server over 443

I don't, I'm using the nocaddy yml as I have a reverse proxy with nginx

hmm i am not sure then

do you get the log "retrieving peers"

?

Not on the linux machine, but I do on the windows machine.

Hmm, redid the netclient parts on the windows machine.

PS C:\ProgramData\Netclient> .\netclient.exe join -t xxxxx
2022/03/16 12:54:49 [netclient] netclient.exe is in proper location, C:\ProgramData\Netclient\netclient.exe
2022/03/16 12:54:49 Gravitl Netclient on Windows started
2022/03/16 12:54:49 [netclient] joining QwHsDShQ at grpc.netmaker.mydomain.com:443
2022/03/16 12:54:49 [netclient] node created on remote server...updating configs
2022/03/16 12:54:49 [netclient] retrieving peers
2022/03/16 12:54:49 [netclient] starting wireguard
2022/03/16 12:54:52 [netclient] waiting for interface...
2022/03/16 12:54:52 [netclient] interface ready - netclient.. ENGAGE
2022/03/16 12:54:52 [netclient] joining default at grpc.netmaker.mydomain.com:443
2022/03/16 12:54:52 [netclient] node created on remote server...updating configs
2022/03/16 12:54:52 [netclient] retrieving peers
2022/03/16 12:54:52 [netclient] starting wireguard
2022/03/16 12:54:55 [netclient] waiting for interface...
Failed to find the network interface or network interface is not ready.
2022/03/16 12:54:56 [netclient] error installing: could not reliably create interface, please check wg installation and retry
2022/03/16 12:54:56 [netclient] removed machine from default network on remote server
2022/03/16 12:54:56 [netclient] could not flush peer routes when leaving network, default
2022/03/16 12:54:56 [netclient] removed WireGuard interface: nm-default
2022/03/16 12:54:56 [netclient] removed default network locally
2022/03/16 12:54:57 [netclient] stopping Windows, Netclient daemon
2022/03/16 12:54:57 error running command: C:\ProgramData\Netclient\winsw.exe stop
2022/03/16 12:54:57
PS C:\ProgramData\Netclient>

Haven't noticed that error before

aha, that might be because I tested to disable UDP hole punching on the comms network. Reverting that and the error message disappeared.

But I'm still having the issue with the node not having a peer in the comms interface when running

wg show

Is there any way to have some verbose logging server side to see what actually happens when a node is joining?

Does anyone know what the most likely culprits are for this error message?

./netclient join -k <key> -n <network> --apiserver api.<apiserver>:443 --grpcserver grpc.<grpcserver>:443
[netclient] joining <network> at grpc.<grpcserver>:443
[netclient] error installing: rpc error: code = Unavailable desc = connection closed before server preface received
Failed to authenticate: rpc error: code = Unauthenticated desc = Something went wrong with Auto Login: rpc error: code = Unavailable desc = connection closed before server preface received
[netclient] removed <network> network locally
[netclient] removed systemd remnants if any existed
[netclient] removed systemd remnants if any existed

I have seen it mentioned in the chat log but it didn't seem like any conclusive solution was mentioned

that looks like a caddy issue at first glance

I see. One additional detail is that we are able to join the network from most other computers, but here I am trying to join the network on a OpenWRT-based modem/router. May I have to add the SSL/TSL certificate onto my modem somehow to make the authentication succeed? (I am not a network expert, so I might be misunderstanding)

hmmm that should not be necessary

Would I see the same error if the gRPC port (50051) or the HTTPS port is being blocked by the OpenWRT firewall?

i dont think so, but worth checking if you can connect directly from openwrt

this seems like a pretty rare error

it appears to be related to grpc-go specifically

How can I check this?