Thanks. If I did a manual install, could I just run dnsmasq on the server, add custom entries, and just pass the server IP (on WG) as the DNS option to clients?

yeah that should be no problem

netclient join error

[netclient] 2022-09-15 21:57:07 error installing:  error creating node 500 Internal Server Error {"Code":500,"Message":"Key: 'Node.LocalAddress' Error:Field validation for 'LocalA

[netclient] 2022-09-15 21:57:07 error running command: wg-quick down /etc/netclient/config/.conf

[netclient] 2022-09-15 21:57:07 wg-quick: `/etc/netclient/config/.conf' does not exist

[netclient] 2022-09-15 21:57:08 removed systemd remnants if any existed

hello

i'm trying to set up a server on vps

but can't access the dashboard from the domain

got 404 page not found error

nvm, just got it working now

the url of dashboard is https://dashboard.mydomain.com lol

routines:ssl3_read_bytes:sslv3 alert bad certificate

i got this error in mq container

1663401222: OpenSSL Error[0]: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate 1663401222: Client disconnected: Protocol error.

Try following this guide: https://gist.github.com/mattkasun/face2a7c1f32031a2126ff7243caad12

Hi. You stopped publishing docker images for

linux/arm64

? It's not available for 0.15.2

one client reports "{"Version":"v0.15.2","Connected":""}" on the nodes page. (debian) others are ok after the upgrade.

one client reports Versionv0 15 2

Having an issue with setting up a personal VPN (nat) I'm using the NM server for ingress and outgress and created an Ext client so I can use the conf. When I activate the tunnel there is no connection. I can't even ping the server. I am using cloudflare but doesn't seem to be an issue with a full mesh setup I tried with a few nodes.

Hi You stopped publishing docker images

I think I'm a little confused with how I can use coredns in the docker compose. I know that I don't need to use it, but I want to use it for external clients. @jolly-london-20127 You said that I should be able to add the private address to the netmaker node (e.g., from the vpn subnet), but when I'm `docker exec`'d into that container I don't even see a bind active for port 53 even though PORT_FORWARD_SERVICES=dns is set. Is there something I'm missing? E.g., I can't do

dig <known-good-name> @private.ip.address

doesn't work from within the overlay network

E.g.,

# netstat -tlunp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.11:42479        0.0.0.0:*               LISTEN      -
tcp        0      0 :::8081                 :::*                    LISTEN      1/netmaker
udp        0      0 127.0.0.11:60003        0.0.0.0:*                           -
udp        0      0 0.0.0.0:51830           0.0.0.0:*                           -
udp        0      0 :::51830                :::*                                -

Ah nevermind, I decided to just set the coredns container to portforward "53:53/udp" and use the external ip and that works nicely. Thanks!

I've got a node that keeps going red and this is in the new logs:

2022-09-22 01:15:37 error unmarshaling payload invalid character 'v' looking for beginning of value (1089)

@calm-agent-16830 I think if you remove the node from the network and then rejoin then it'll work. There's a couple other posts where other people had the same problem

@big-wolf-4507 OK, I'll make sure I have another way to connect

I set up 0.16 on ubuntu 22.04 on a vultr vps and everything appears to be working. netmaker and netclient seem hapy. wg show shows everything is happy. But I can't ping anything. I have a vps set to be ingres,egress,and relay for my mackbook behind cgnat/464xlat (tmobile home internet). Any glaring mistakes?

I also have an external client for my android phone and ipad. Nobody can ping the two servers or use the vpn for network access

I did leave udp hole punching on but that won't work for my isp as i understand it

Disabling hole punching has not fixed it

have similar issue as @few-carpenter-24293 , nm 0.16 but on debian.. firewall is open on the nm server (80&443/tcp, 51821:51899/udp), hole punching is on for all nm clients.. on the server i can see there's a bit of wg traffic (both recv & send), but can't ping from clients->server, or from server->clients.. all clients have warning (connectivity issues), even a client on another vps (no firewall rules)

do nodes have wireguard handshakes? do both transfer and received have positive numbers in the output of

wg show