someone here mentioned getting a 500 error with the install script. This script will fix it, but isn't the one displayed in the access keys page. You'll need to replace the reference from "netclient-install.sh" to "netclient-install.slim.sh"

Apologies for all this, it's due to me not updating the docs thoroughly

No worries. Appreciate your work.

trying a new install based on the above updates

when try add a client using the new client install i get the following

sh: 8: Syntax error: newline unexpected

however ... i skiped the install sh and manually did the install and we are up and running !

now the real fund starts .... lets see if this can replace my tailscale setup !

Spotted this on removal

root@pihole1:/etc/netclient# ./netclient leave 2021/06/09 13:45:36 Error attempting to leave network all 2021/06/09 13:45:36 open /etc/netclient/netconfig-all: no such file or directory

the file was indeed not there

You need to specify the network name

@User which URL were you using for the netclient install. Is it this? https://raw.githubusercontent.com/gravitl/netmaker/v0.5/scripts/netclient-install.slim.sh I just ran and dont hit that error

doh

that one

ok, yeah I think it depends on the shell being used to run the script, but it should be fixed now

just changed it from #!/bin/sh to #!/bin/bash

i'll test again now

yup thats sorted it 🙂

So odd issue, i still dont get a create new admin login once I deploy the containers. But after navigating to the IP and port (since my port 80 is used). I get

Error connecting to backend. Given: http://external_IP:8081 Server may be down, address may be incorrect, or port may not be open. Please investigate.

But the firewall rules are open, but according to

sudo netstat -lp

there is no 8081 listening, and i dont see the port in the container list either.

CONTAINER ID   IMAGE                      COMMAND                  CREATED              STATUS              PORTS                                           NAMES
2e9b8080cdef   gravitl/netmaker-ui:v0.5   "/docker-entrypoint.â¦"   About a minute ago   Up About a minute   0.0.0.0:8181->80/tcp, :::8181->80/tcp           netmaker-ui
83c04f61a46e   coredns/coredns            "/coredns -conf /rooâ¦"   About a minute ago   Up About a minute   53/tcp, 0.0.0.0:53->53/udp, :::53->53/udp       coredns
a71834c3b164   gravitl/netmaker:v0.5      "./app"                  About a minute ago   Up About a minute                                                   netmaker
32cda9a3ebe2   mongo:4.2                  "docker-entrypoint.sâ¦"   About a minute ago   Up About a minute   0.0.0.0:27017->27017/tcp, :::27017->27017/tcp   mongodb

first step if you get that error should always be to run: docker logs netmaker

to make sure the server is running correctly

does setting DNS = on result in the coredns container getting pulled ?

nope, it still needs a section in the docker compose. It just tells the server to write settings to coredns

so if you set DNS=on, you should also make sure the coredns section is in the docker compose

ahh

i need to have a play with the complete compose file and figure all the options

Logs for the net maker container

2021/06/10 14:33:39 Connecting to MongoDB at 127.0.0.1:27017...
2021/06/10 14:33:42 MongoDB Connected.
2021/06/10 14:33:42 Creating default network...
2021/06/10 14:33:42 Default network already exists. Skipping...
2021/06/10 14:33:42 comms network already exists. Skipping...
2021/06/10 14:33:42 WireGuard interface nm-grpc-wg already exists. Skipping...
2021/06/10 14:33:42 controller.go:47: REST Server succesfully started on port 8081 (REST)
2021/06/10 14:33:42 main.go:146: Agent Server succesfully started on port 50051 (gRPC)
2021/06/10 14:33:42 main.go:162: Setup complete. You are ready to begin using netmaker.