2021/09/26 15:53:33 Error installing:  rpc error: code = Unknown desc = invalid CIDR address: 
2021/09/26 15:53:34 Failed to authenticate: rpc error: code = Unauthenticated desc = Something went wrong with Auto Login: rpc error: code = Unknown desc = crypto/bcrypt: hashedPassword is not the hash of the given password

Any idea why this is happening? Im still using the same key as with all previous clients, and netmaker and clients are all 0.7 now

getting an error when doing a pull on the server node but everything seems to be working

DNS is fine?

DNS is fine, yes

Hello - I followed the quick setup guide and got netmaker server running on a Ubuntu EC2 sever, created a network with subnet 10.0.3.1 then created a second EC2 server and ran the netmaker install script, got the subnet 10.0.3.2 and it connected to the first node fine but I cannot ping either endpoints. Trying to ping From node 1 (10.0.3.1) -> node 2 (10.0.3.2) I get “destination host unreachable” and when trying to ping vice versa ping command just hangs and results in 100% packet loss. Am I missing something here?

Firewalls

Thought that too but I opened up icmp traffic on the SG and can ping the public IP fine but not the private WG IP. Will continue to troubleshoot.

Do have UDP hole punching enabled? If so, try turning it off

That indicates the second node can’t reach the first node. Does your security group have UDP traffic open on 51821?

@User ok k8s question, deploying on k8s states you should already have a netmaker host deployed, so we are basically just connecting to a vm or other? can we not have k8s be the netmaker host itself ?

I'm still having DNS issues after trying everything I can think of these past few days. Trying to connect an ubuntu node that is running on Azure:

2021/09/28 13:11:15 [netclient] joining mat-net1 at grpc.myhost.mydomain.org.uk:443 2021/09/28 13:11:15 local vpn, getting local address from range: 192.168.16.0/24 2021/09/28 13:11:16 [netclient] node created on remote server...updating configs 2021/09/28 13:11:16 [netclient] retrieving remote peers 2021/09/28 13:11:16 [netclient] starting wireguard 2021/09/28 13:11:16 error running command: resolvectl dns nm-mat-net1 myhost.mydomain.org.uk 2021/09/28 13:11:16 Failed to parse DNS server address: myhost.mydomain.org.uk Failed to set DNS configuration: Invalid argument 2021/09/28 13:11:16 WARNING: Error encountered running resolvectl dns nm-mat-net1 myhost.mydomain.org.uk 2021/09/28 13:11:17 [netclient] joined mat-net1

A DNS server with resolvectl has to be an IP address

to test to make sure this will work, first try running that exact resolvectl command manually: resolvectl dns nm-mat-net1 myhost.mydomain.org.uk

im guessing it will fail with same error

then

do an nslookup on that domain, or if you already know the domain, try : resolvectl dns nm-mat-net1 1.2.3.4 (where 1.2.3.4 is your dns server IP)

if that does not return an error, next try resolving one of your private dns entries

e.g. nslookup nodename.nm-mat-net1

if THAT works, then you will need to do a docker-comose down/up and set the coredns address correctly (to the IP instead of the domain)

Hmmm, so sudo nslookup netmaker.matt-net1 timed out; no servers could be reached

But resolvectrl with IP gave no error

try "nslookup netmaker.matt-net1 1.2.3.4", where 1.2.3.4 is the IP

I'm not sure where in the config the server is pushing the url from instead of the IP address

Same timed out

ok, so it sounds like the nameserver is not bound to port 53 on the machine, OR there is a firewall blocking port 53

I'm behind a router but everything is forwarding the server and the firewall is open for dns

port 53 straight to the netmaker server

hmmmm