Guess I'll use Netmaker then

With uses, is that "How many devices can use this key" or "How many times a device can connect using this key"?

How many devices can use this key. the uses is decremented by one everytime a device joins with a key

I agree the netclient would be best to use to minimize update hassles. Yet the windows netclient seems to only want to use a key in the UI. I wonder why User/Pass was not set up in that - or am I missing something in the client UI? The key also has a max uses, which I assume is a means to force key rotation. So a one key per user set for like 30 uses - is that a "normal" process people follow vs the external client file they have to manually import into the WG app?

the netclient gui was developed before we had user sign-in joining enabled. The team is currently working on a better gui which will include that and more functionality in the coming month or 2

Hey all, I am trying to do a dockerless install on my machine and using Nginx for reverse proxying. I am following the Advanced Installation: Linux Install without Docker. I get stuck at the step where I have to set up mosquitto. It feels like the documentation is not exactly correct. First it was missing the password in the configuration, after that I get stuck on the certificates. It tells me I should copy the certificates from /etc/netmaker but there are no certificates there. If do not specify the certificates in the Mosquitto configuration, netmaker succesfully connects Mosquitto, but still does not generate any certificates. I have NOT yet set up the UI. Am I missing a step or is the documentation incomplete? My next step would be to generate my own certificates and put them in the /etc/netmaker folder manually, but it seems like the documentation implies that netmaker should generate it's own certs.

Netmaker not generating SSL certificates in etc netmaker folder on dockerless install

How to install without using Traefik

Does anyone use NPM and have Netmaker behind it? I was wanting to see if I could either just use a self signed cert without forwarding the ssl port and only forward the WG port? Or use NPM for the SSL part for the webgui and then also forward the port for WG

Is 0.17.0 being explictly treated as a pre-release or only that because it contains a large amount of breaking changes?

Pre-release

I got excited when I saw this pre-release and noticed the switched back to Caddy, but I'm in the same boat as I was with the previous release after a few hours. I have two external docker hosts that run caddy to handle wildcard subdomains, and I've struggled so much to get netmaker running on them.

I'm keen to test 0.17 pre-release, but could one of the dev team expand on the windows + ext clients issue? This is pretty vital for a few of our users. I was about to hose the current setup as things have been quite broken since moving from 0.15 to 0.16.1 in one hop. Seems like a good time to try the latest release as long as external windows clients are somehow functional. Grateful for your insights

Hi, I am trying to setup netmaker on Kubernetes using following instructions: https://github.com/gravitl/netmaker/tree/master/k8s/server but the netmaker container crashes with following message:

$ kubectl logs pod/netmaker-1 -n netmaker
              
 __   __     ______     ______   __    __     ______     __  __     ______     ______    
/\ "-.\ \   /\  ___\   /\__  _\ /\ "-./  \   /\  __ \   /\ \/ /    /\  ___\   /\  == \   
\ \ \-.  \  \ \  __\   \/_/\ \/ \ \ \-./\ \  \ \  __ \  \ \  _"-.  \ \  __\   \ \  __<   
 \ \_\\"\_\  \ \_____\    \ \_\  \ \_\ \ \_\  \ \_\ \_\  \ \_\ \_\  \ \_____\  \ \_\ \_\ 
  \/_/ \/_/   \/_____/     \/_/   \/_/  \/_/   \/_/\/_/   \/_/\/_/   \/_____/   \/_/ /_/ 
                                                                                                                                                                                                                                                                                 

[netmaker] 2022-12-01 14:33:10 connecting to postgres 
[netmaker] 2022-12-01 14:33:11 database successfully connected 
[netmaker] 2022-12-01 14:33:11 no OAuth provider found or not configured, continuing without OAuth 
[netmaker] 2022-12-01 14:33:11 Configuring MQ... 
[netmaker] Fatal: failed to configure MQ:  MQ admin password not provided

Looking into code it seems the it expects evironment variable

MQ_ADMIN_PASSWORD

to be defined but the manifests or the instructions do not mention this setting. Am I missing something?

It is likely the documents have not been updated. MQ_ADMIN_PASSWORD is required after the switch to dynamic security for MQ comms

so I should add it to following manifest, correct? https://github.com/gravitl/netmaker/blob/master/k8s/server/netmaker-server.yaml

that would be great!

@quiet-continent-24852 I am hitting one more problem on the message broker pod:

$ kubectl logs pod/mosquitto-7966bf5f56-4wxnd -n netmaker
chown: /mosquitto/config/mosquitto.conf: Read-only file system
1669908757: mosquitto version 2.0.11 starting
1669908757: Config loaded from /mosquitto/config/mosquitto.conf.
1669908757: Opening ipv4 listen socket on port 8883.
1669908757: Opening ipv6 listen socket on port 8883.
1669908757: Error: Unable to load CA certificates. Check cafile "/mosquitto/certs/root.pem".
1669908757: Error: Unable to load server certificate "/mosquitto/certs/server.pem". Check certfile.
1669908757: OpenSSL Error[0]: error:02001002:system library:fopen:No such file or directory
1669908757: OpenSSL Error[1]: error:20074002:BIO routines:file_ctrl:system lib
1669908757: OpenSSL Error[2]: error:140DC002:SSL routines:use_certificate_chain_file:system lib

Am I missing some other undocumented step ?

the certs should be stored on ReadWriteMany volume so perhaps the certs should be first generated and written down by the netmaker server ? But the netmaker server won't properly start until it succesully connects to the mq, so overall this looks like a deadlock on circular dependency.

hello, new user here. What do I send you to help me trouble shoot my server install? I think I followed all instructions on the walkthorugh. When I ping my public IP a host is up. But visiting my netmaker.techtech.live shows nothing. What should I dig up and post here to see? Here is the output from docker logs netmaker is ___ ___ __ __ __ __ / _ \ / _ \ / __ \ __ __ __ /___/ /___/ /___/ / ___/ / , _// /_/ / /___/ /___/ /___/ /___/ /___/ /___/ /_/ /_/|_| \____/ /___/ /___/ /___/ [netmaker] 2022-11-30 03:11:00 connecting to sqlite [netmaker] 2022-11-30 03:11:00 database successfully connected [netmaker] 2022-11-30 03:11:00 proceeding with Netmaker license validation... [netmaker] 2022-11-30 03:11:01 License validation succeeded! [netmaker] 2022-11-30 03:11:01 proceeding with Free Tier license [netmaker] 2022-11-30 03:11:01 no OAuth provider found or not configured, continuing without OAuth [netmaker] 2022-11-30 03:11:01 Configuring MQ... [netmaker] 2022-11-30 03:11:01 MQ config exists already, So Updating Existing Config... [netmaker] 2022-11-30 03:11:01 REST Server successfully started on port 8081 (REST) [netmaker] 2022-11-30 03:11:01 connecting to mq broker at mq:1883 with TLS? false [netmaker] Fatal: Admin: could not connect to broker, token timeout, exiting ...

New user

"Waiting for netmaker server to startup" that is docker logs mq and traefik time="2022-11-29T08:13:26Z" level=error msg="service \"netmaker-exporter\" error: unable to find the IP address for the container \"/netmaker-exporter\": the server is ignored" providerName=docker container=netmaker-exporter-root-490f1018fd86aa040340bd97f1a5ed6e233d6d6936759cea4df6cf183c2242bd time="2022-11-29T08:13:26Z" level=error msg="Unable to obtain ACME certificate for domains \"broker.netmaker.techtech.live\": unable to generate a certificate for the domains [broker.netmaker.techtech.live]: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/failed-validation-limit/" providerName=http.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory" routerName=mqtt@docker rule="HostSNI(

broker.netmaker.techtech.live

)" time="2022-11-29T08:13:26Z" level=error msg="Unable to obtain ACME certificate for domains \"prometheus.netmaker.techtech.live\": unable to generate a certificate for the domains [prometheus.netmaker.techtech.live]: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating ^Z [3]+ Stopped docker logs traefik

I did run sudo docker-compose up -d prior

you have something incorrect in your set up you are not getting certs; see error message in traefik .. is port 80 open? it the email vailid

I will check

I'm having this same issue, but with caddy on the v0.17.0 prerelease.

@bored-island-21407 Ok, instructions didn't incldue port 80, but I added it anyway. And the email is correct in the yml

follow the links in the traefik errors

ok i read them all

I suspect my wildcard cert with subdomains being handled within caddy instead of on the DNS server are the cause of my issue. [netmaker] 2022-12-01 20:52:24 connecting to mq broker at ws://mq:1883 with TLS? false