https://netmaker.org logo
Join Discord
Powered by
hi, ive just done an install of netmaker, after so...
# install
n
hi, ive just done an install of netmaker, after some issues with dns from old documents, figred it out and it seems to be up, but i add my nodes, and after a few minutes each of them goes into an error state, from cloud vps, to laptop at home...the server is on a vps as well. i cant seem to ping anything, and i notice the laptops tnnel keeps dropping and re adding....any suggestions if this is client or server issue?
b
sounds like client connectivity issue -- most likely causes
1. server misconfiguration
2. firewalls (server or client)
n
is there a way i can test? not seeing much in logs...
i think server as no client working at all...not sure how to check if the server up and running
b
best way is to get one node working. in your case I would work with the server and the node on the vps (home internet adds complexity)
1. on client (on vps) -- can you ping api.
2. can you ping broker.
n
yes
b
what is output of 
wg show
on client
n
shows interface and 3 clients
1 of the clients is the server
peers nt clients i guess 🙂
b
in the lines that show tx and rx .... any values?
n
0b recieved, 104 approx sent
b
so you are not getting a handshake
on the client on the vps, do 
netclient pull -n <network name> -vvvv
n
sudo netclient pull -vvvv [netclient] 2022-08-26 22:29:21 [commands.go-67] Pull(): No network selected. Running Pull for all networks. [netclient] 2022-08-26 22:29:21 [common.go-416] informPortChange(): network: knight UDP hole punching enabled for node thebardxxxxcoza [netclient] 2022-08-26 22:29:23 [common.go-165] InitWireguard(): waiting for interface... [netclient] 2022-08-26 22:29:23 [common.go-193] InitWireguard(): interface ready - netclient.. ENGAGE [netclient] 2022-08-26 22:29:23 [commands.go-90] Pull(): pulled network config for knight [netclient] 2022-08-26 22:29:23 [register.go-53] RegisterWithServer(): register at https://api.xxxx.co.za:443/api/server/register [netclient] 2022-08-26 22:29:23 [register.go-97] RegisterWithServer(): network: knight certificates/key saved [netclient] 2022-08-26 22:29:23 [commands.go-116] Pull(): reset network all and peer configs
b
so now does the rx line for the server peer show received bytes when you do wg show
n
no, but i can see the config has changed, theres only 1 peer and allowed ips added more addresses....i think i made a relay earlier to try get it working, looks like its pulled that
still 0 recieved
the server is a fresh ubntu 22.04...
b
is there a firewall on the server? or a cloud firewall
looks like udp 51820 is blocked on server
n
ufw disabled, and there shouldnt be a firewall on that vps...small provider, maybe iptables?
ok so no firewall on control panel....set iptables to allow all(temporariily)
[netclient] 2022-08-26 22:49:26 joining knight at api.xxxxx.co.za:443 [netclient] 2022-08-26 22:49:27 network: knight UDP hole punching enabled for node knightxxxxxxcoza [netclient] 2022-08-26 22:49:27 network: knight certificates/key saved [netclient] 2022-08-26 22:49:27 starting wireguard [netclient] 2022-08-26 22:49:59 unable to connect to broker, retrying ... Ping tcp://broker.xxxxxx.co.za:443(216.27.7.133:443) - Connected - time=12.860083ms Ping tcp://broker.xxxxxxxx.co.za:443(216.27.7.133:443) - Connected - time=18.258246ms Ping tcp://broker.xxxxxxxx.co.za:443 - failed: dial tcp: lookup brokerxxxxxx.co.za: i/o timeout [netclient] 2022-08-26 22:50:34 could not connect to broker at broker.xxxxxxx.co.za:443 [netclient] 2022-08-26 22:50:34 network: knight failed to publish update for join connection timeout 2022/08/26 22:50:34 daemon restart failed failed to find pid could not read pid file open /var/run/netclient.pid: no such file or directory
ok, managed to get all peers can ping each other, but none can ping 254...the server 🙂 so all in warning state but working, gonna call that a win for now 🙂
thanks for helping 🙂
b
something must be blocking udp ports on server
n
yep, im gonna message the vps provider and ask them to check 🙂
just a note, i installed the client directly on the server, and i have udp traffic (can see it with tcpdump) it looks like its the docker thats not recieving udp traffic....but everything works except says nodes error 🙂
2 Views
PreviousNext
Powered by