you can try this. delete the /etc/netclient/config/netconfig-sinaowolabi file and force netclient to use the backup file.

suspicion is that the file got corrupted somehow.

I can open the files

How do I force it to use the backup?

delete the main file and it will use the backup file automatically

Ok

Same thing happened

hmm.

can you paste the contents of the file in a direct message to me?

anyone have any thoughts? happy to debug further, just not sure where to start (on my note from yesterday 13:41 EDT)

do you want to join me in the troubleshooting voice channel?

not able to join via voice, but delighted to provide logs or more details here if you have a moment to look

are your nodes behind NAT

essentially, netmaker running on a vps in docker - lots of clients attached from around the internets, works great can't get the actual vps to join successfully though

some nodes are behind a nat, others aren't - all that appears to work great

so what is the issue?

the vps itself, when it joins the netmaker'ed network, cannot even ping the netmaker endpoint (.254) or any of the other clients on the wireguard IP adresses

the netclient on the server is running inside the netmaker container

if you want to ping another node from the netmaker server (over a netmaker network) you have to do it through docker

eg. to ping 10.0.0.1 (assuming that is the wireguard address of one of your node)

perhaps i read the FAQ wrong, my goal was to have the netmaker vps (which runs the netmaker server in docker) participate by also by adding netclient to the vps

docker exec -it netclient ping -c 3 10.0.0.1

so in addition to netmaker, you also installed netclient on the netmaker server?

it's not recommended but should be doable, my guess is just you have conflicting ports

ahhhhhh - yes, i'm wanting the vps itself to participate in one of the networks - conflicting ports makes sense, was going off this statement: https://docs.netmaker.org/troubleshoot.html "If you want to give the physical server / VM a private IP in the netmaker network, you must deploy an additional node using the standard netclient. The only note here is that the server consumes ports 51821-51831, so you will need to give it a port outside this range, e.x. ./netclient join –port 51835. One a netclient is deployed to the underlying server/VM, you will be able to use the private address to reach other nodes from the host, or to reach the server over the private network."

I would just do "./netclient join -t -p 51831 -udpholepunch no"

confirm udpholepunching is off once it's joined, if not, turn it off via UI

attempting right now!

BOOM - that did it - was missing udpholepunch no!!!

thank you so much - that's amazing