@worried-match-11479 IIRC, letsencrypt/certbot uses 80 for DNS validation. But maybe the docs should mention it.

Alright, I've got it working now. I have removed both DNS support and the Nginx ingress though. Do you want me to put together a PR to update

kube/netmaker-template-nodns-noingress

or something like that? That might be a little too specific though?

The mention of port 80 reminds me that my first attempt to install the Netmaker server failed because the target machine had a private HTTP server listening on port 80 of an interface previously created by another VPN. The current implementation of the server seems to be listening on all interfaces, not just the one bound to the public address of the node, so no other applications can use port 80.

# socat tcp-listen:80,bind=127.0.0.1,fork,reuseaddr,accept-timeout=300 /bin/cat  
2022/01/26 08:07:01 socat[37392] E bind(5, {AF=2 127.0.0.1:80}, 16): Address already in use

@User this must be for a baremetal install then, right?

It was an installation on a KVM VPS that I use as a server for other WireGuard and Nebula VPNs. The attempt to bind to port 80 fails if and only if the Netmaker server is running.

why not have a separate kvm, or run in docker?

I doubt that either approach would work if the Netmaker server is already listening to port 80 of all interfaces of the VPS. I solved my immediate problem by moving the private HTTP server from port 80 to port 81.

if it's running in docker it would just be in the container

/ whatever interface you're binding it to externally on the VPS

The external docker interface to Netmaker server seems to be binding to port 80 on all interfaces of the VPS, which prevents any other usage of port 80, including by any docker container that I might deploy. If possible, the external docker interface to Netmaker server should only bind to port 80 of the interface associated with the public IP address of the VPS so port 80 can be used on all other interfaces.

do you mean the caddy container? the netmaker server itself does not expose 80

and caddy requires port 80 to get certiticates

I know very little about the internal structure of the Netmaker software that is installed on a server; it is probably the caddy container.

we need to include more documentation about running netmaker without the caddy proxy. That's really the limitation here. If you already have a proxy in your environment such as Nginx, you should be using that instead.

true so many thing to document

Hrm. I had half a big message to write up, and realized that somehow I was running the quick install from an older version (of the docs?). FWIW, https://netmaker.readthedocs.io/en/v0.8.0/quick-start.html These instructions conflict due to having nginx as well as caddy. I suspect the docker-compose file it pulls is meant for the more recent version.

One thing in common with both, however, is that it describes configuring UFW, but doesn't include port 22, and doesn't enable UFW.

@User @User I encountered the same error when running Nginx on a separate server. (because I followed the wrong quick start guide)

[netclient] error installing: rpc error: code = Unavailable desc = connection closed before server preface received

Then I removed nginx, re-enabled caddy, and boom, I'm connected. You guys really should get nginx support figured out and documented eventually. But for now, I'm up and ready to test.

i have a question as i am trying to test the netmaker in docker but the command on the help section is not working for me wget -O docker-compose.yml https://raw.githubusercontent.com/gravitl/netmaker/master/scripts/docker-compose.test.yml sed -i ‘s/HOST_IP/< Insert your-host IP Address Here >/g’ docker-compose.yml docker-compose up -d` the sed section is not working in the cli

what is the error?

I'm not sure if this is a NM thing, but I just ran into the following:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
     docker.io is not installed. Attempting install.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 docker.io : Depends: containerd (>= 1.2.6-0ubuntu1~)
E: Unable to correct problems, you have held broken packages.
     failed to install docker.io. Exiting.

This is on a system that ran NM previously, Docker/docker-compose is working, I'm just not sure about docker.io specifically.

I downloaded the script and removed docker.io from the dependencies, I'm pretty sure it's working, I'm positive docker-compose is. That made it install, got the success message. Then this:

🤷‍♂️

@User what are your logs from netmaker (docker logs netmaker)?

Hello! Im trying to install the netmaker on my Synology DS920+ NAS with portainer. I modified the docker-compose file from github. It turn out to be I can create the admin user but I can not create the network.

Here is the log from netmaker

Here is my modified docker-compose file