825071750290210916 #general

powerful-hydrogen-97244

08/04/2021, 8:17 AM

api.example.com: ?

powerful-hydrogen-97244

08/04/2021, 8:27 AM

@User Ah I see quite a few new variables, also in the connection string - any chance there a list of new env variables :D?

jolly-london-20127

08/04/2021, 3:17 PM

You can check in servercfg the variables it will check (two files in there). I haven’t documented it yet. Also planning on removing a bunch of variables and just making it manual. I tried making it so it would automatically detect the right addresses but turns out that’s more complicated than it seems

jolly-london-20127

08/04/2021, 3:17 PM

Easier to just have people specify the grpc and api address manually on startup

powerful-hydrogen-97244

08/04/2021, 5:10 PM

alright!

powerful-hydrogen-97244

08/04/2021, 6:32 PM

Hm, I'm gonna wait for some more documentation in that regards - it seems to only want to connect via HTTP and I have not figured it out how it changes to HTTPS

jolly-london-20127

08/04/2021, 10:58 PM

@User you just need to set GRPC_SSL=on

jolly-london-20127

08/04/2021, 10:59 PM

This is our unpublished guide for deploying the next version behind nginx (it will have some issues as-is): https://netmaker.readthedocs.io/en/develop/quick-start.html

powerful-hydrogen-97244

08/05/2021, 7:09 AM

It is on, it doesn't seem to affect the attemted connection. Btw, it's not the GRPC, it's the API connection -> It wants to connect to the api via HTTP I'll have a look at the guide :)

brash-tomato-28082

08/11/2021, 7:44 PM

Hi, the buttons to make a node into an ingress gateway or egress gateway are greyed out despite the fact that the node is healthy. I checked the source code, it seems to only enable the button if the node is in the pending status?

jsx
<IconButton aria-label={`make node, ${node.name}, a gateway`} onClick={() => handleOpening(node)} disabled={node.ispending === "no"}>

brash-tomato-28082

08/11/2021, 7:46 PM

Shouldn't it be the other way around?

jolly-london-20127

08/11/2021, 7:48 PM

@User bueller?

quiet-continent-24852

08/11/2021, 7:50 PM

Ah, yes I will look into this @brash-tomato-28082

brash-tomato-28082

08/11/2021, 7:55 PM

I'm also getting a "failed to parse interface" when trying to checkin

jolly-london-20127

08/11/2021, 7:57 PM

logs?

brash-tomato-28082

08/11/2021, 7:57 PM

for netmaker?

brash-tomato-28082

08/11/2021, 7:57 PM

or netclient?

jolly-london-20127

08/11/2021, 7:57 PM

netclient, though if anything is showing on netmaker that would be good too

brash-tomato-28082

08/11/2021, 7:58 PM

1 sec

brash-tomato-28082

08/11/2021, 7:59 PM

the error only seems to appear if theres no nm- interface, which occurs after a reboot

jolly-london-20127

08/11/2021, 7:59 PM

interesting

jolly-london-20127

08/11/2021, 7:59 PM

does the error go away after another checkin?

brash-tomato-28082

08/11/2021, 8:00 PM

nope

brash-tomato-28082

08/11/2021, 8:00 PM

it doesnt readd the interface

brash-tomato-28082

08/11/2021, 8:00 PM

i also still get an exit status 1 regardless

brash-tomato-28082

08/11/2021, 8:00 PM

how do i increase the log level?

jolly-london-20127

08/11/2021, 8:00 PM

hmmm, can you please run "netclient pull -n "

brash-tomato-28082

08/11/2021, 8:01 PM

the network works again after a pull

jolly-london-20127

08/11/2021, 8:02 PM

When you run a "netclient pull" it will do a hard reset on the settings, including re-adding the interface

jolly-london-20127

08/11/2021, 8:02 PM

In general when there's a netclient problem, running a "netclient pull" may fix it