my monkey brain isn't good at multi tasking, so i gotta dedicate some days to business and others to coding

no it's because you are a man hahaha

its fine - i cant multi-task either. i was wondering if i needed to dig into it more if its my specific problem or a general problem.

since i have a reliable workaround (restarting the service), for now its not hindering me

do you want me to raise an issue so we dont lose it, or shall i wait?

ah.. he's gone. i'll raise an issue, and i can retract it later on if it turns out to be my fault

tracking it here: https://github.com/gravitl/netmaker/issues/188

does the netclient have a UI or is it just the server?

only the server has a ui

root@wg-netmaker:~# ping 192.168.2.9 PING 192.168.2.9 (192.168.2.9) 56(84) bytes of data. 64 bytes from 192.168.2.9: icmp_seq=1 ttl=63 time=6.99 ms 64 bytes from 192.168.2.9: icmp_seq=2 ttl=63 time=7.13 ms 64 bytes from 192.168.2.9: icmp_seq=3 ttl=63 time=6.88 ms 64 bytes from 192.168.2.9: icmp_seq=4 ttl=63 time=7.06 ms 64 bytes from 192.168.2.9: icmp_seq=5 ttl=63 time=7.14 ms 64 bytes from 192.168.2.9: icmp_seq=6 ttl=63 time=7.44 ms and now it works...

need to test it from a different node as well still but from the netmaker server itself I can ping them now at least

Hi!! I am trying to connect to the server using a raspberry pi 4, but after following the quick-start guide I get the following errors : ./netclient: 1: ./netclient: �ELF: not found ./netclient: 1: ./netclient: Wv: not found ./netclient: 1: ./netclient: v: not found ./netclient: 1: ./netclient: ��m�m�$$: not found ./netclient: 2: ./netclient: @$: not found ./netclient: 1: ./netclient: �: not found ./netclient: 1: ./netclient: {�: not found ./netclient: 3: ./netclient: @�@$@q�t�e@*Ev: not found ./netclient: 4: ./netclient:��{��{�� v�: not found ./netclient: 4: ./netclient: ������� ����: not found ./netclient: 6: ./netclient: Syntax error: "(" unexpected Here the steps that I did: 1. Installed wireguard: apt install wireguard 2. Join the network using: curl -sfL https://raw.githubusercontent.com/gravitl/netmaker/v0.5/scripts/netclient-install.slim.sh | KEY=MY_TOKEN Did I forget anything?

You will to recompile netclient for arm64 architecture. You are trying to run an x86 executable on an arm processor

I read smth like, but could not find how to recompile it... could you guide me on how to do so?

Clone the repository; change to the netclient directory and run go build . If you are not building on the pi itself, the command is GOOS=Linux GOARCH=arm64 go build .

Oh thanks a lot! but when I ran it in the PI i ran into an error

go: error loading module requirements

. However, when I build it on another machine (as you suggested) I cannot find an output that I can export to the PI in order to proceed with the installation😓.

If it still doesn't work

@User @User I was able to join using a netclient compiled on arm64 (pi). Can either of you provide logs?

I'll upload the latest binary

This is the latest binary: https://github.com/gravitl/netmaker/releases/download/v0.5-beta/netclient-arm64

if you're having problems after that it is probably the config info

I don't have an arm64 device I just did that ^ because @icy-soccer-17326 couldnt get the compile to work

Ah! ok, thank you for that

Hi i tried to put the backend behind a nginx reverse proxy. From backend.netmaker.example.org/ i get a 404 From backend.netmaker.example.org/api/users/adm/hasadmin i get a json with false as response. In my docker-compose i defined: environment: BACKEND_URL: "https://backend.netmaker.kazies.win:443/" http 301 redirects to https per default for all my services. May this be the issue?

Hi, sounds like your backend is set up properly behind the proxy. The root path wont return anything, thus the 404, and false should be the response for "hasadmin" if you're just setting it up

what is the issue you are encountering? something in the front end?

Error connecting to backend. Given: https://backend.netmaker.example.org Server may be down, address may be incorrect, or port may not be open. Please investigate.

Thats the error i get

The backend doesn't spit out any messeges on log