Failed to create access key - Githubissues

gravitl / netmaker

Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.

https://netmaker.io

Other

9.4k stars 547 forks source link

Failed to create access key #837

Closed gkl1368 closed 2 years ago

gkl1368 commented 2 years ago

On version 0.11.0, when I want to create access key, it always show

afeiszli commented 2 years ago

Was this an upgrade or a fresh install? And do you have a comms network in your dashboard? Please provide as much information as possible.

gkl1368 commented 2 years ago

Was this an upgrade or a fresh install? And do you have a comms network in your dashboard? Please provide as much information as possible.

It's a fresh install, and this occurs after I create a network and then to get access key to allow client join the network.

0xdcarns commented 2 years ago

Did you install via the nm-quick.sh script? If not, please make sure your env variables/config matches the required ones in the latest docker-compose.contained.yml and restart your netmaker server after doing so. It should auto generate a comms network, but it seems your instance did not.

gkl1368 commented 2 years ago

Did you install via the nm-quick.sh script? If not, please make sure your env variables/config matches the required ones in the latest docker-compose.contained.yml and restart your netmaker server after doing so. It should auto generate a comms network, but it seems your instance did not.

I install with docker and config all env variables. You mean I need restart netmaker after create a network?

0xdcarns commented 2 years ago

No, it should have created it. But I may try a docker restart netmaker and you should see in the logs in the beginning if it created the comms network or not (docker logs netmaker). If not I would attempt the nm-quick.sh on another machine (if possible) and compare the differences in the environments.

gkl1368 commented 2 years ago

No, it should have created it. But I may try a docker restart netmaker and you should see in the logs in the beginning if it created the comms network or not (docker logs netmaker). If not I would attempt the nm-quick.sh on another machine (if possible) and compare the differences in the environments.

this is a log of netmaker

this is the auto generate comm network after I create the network

gkl1368 commented 2 years ago

I found the problem, the auto generate comm network is miss netid, this is I use api to get information of nodes.

0xdcarns commented 2 years ago

Nevermind, I was just shown your configuration. You need to run with CLIENT_MODE=on and PORT_FORWARD_SERVICES should be "mq,ssh", not "mq.ssh"

gkl1368 commented 2 years ago

after turn on client_mode, it worked. Thakns.