825071750290210916 #general

jolly-london-20127

01/15/2022, 5:29 PM

jolly-london-20127

01/15/2022, 5:29 PM

FYI we were considering adding some sort of email sign up so we could send people recovery emails, but that didn't seem like a good self-hosted practice. Would be good to get some thoughts

bright-autumn-15761

01/15/2022, 5:32 PM

I got in, thanks yeah, the email signup thing is tricky to go for it or not. 10 years ago I would have said sure, but google and others have really fucked everyone that used to self host email. I don't even bother anymore because even on an ecommerce site I self host for over 10 years anymore any of the normie email services just auto blacklist me

bright-autumn-15761

01/15/2022, 5:33 PM

I guess if it just used smtp relay, but then again when you think about netmaker, how many hands are really going to be in the admin panel? Even potential commercial users would only have a few people involved from a department.

bright-autumn-15761

01/15/2022, 5:34 PM

My problem is it's set it and forget it. Once I had all my VPS's connected, I logged out and forgot to write down the password. 6 months down the road when I decide to add a new vps or client, oh crap, let me search online how to reset password

bright-autumn-15761

01/15/2022, 5:34 PM

story of my life.

bright-autumn-15761

01/15/2022, 5:35 PM

But the assistance is much appreciated and it's an amazing project.

jolly-london-20127

01/15/2022, 5:37 PM

lol very true

jolly-london-20127

01/15/2022, 5:37 PM

you've been running for 6 months?

bright-autumn-15761

01/15/2022, 5:57 PM

no, I was just using that as an example of everything else I already run

bright-autumn-15761

01/15/2022, 5:57 PM

like my esxi server for instance

high-magazine-39815

01/16/2022, 8:34 AM

Well that's interesting. I sort of followed the install instructions, but skipped caddy and stuck it behind my nginx reverse proxy with DNS for api, grpc, and dashboard. The dashboard loads, but when I try to create an admin it fails.

high-magazine-39815

01/16/2022, 8:34 AM

Multiple different admin names, multiple passwords, stopped and restarted netmaker. Google search for the error doesn't turn up anything relevant. Any tips? Edit: It also says, "Could not reach server" at the top. So that's probably the issue hmm? ...likely a docker issue, containers not able to reach each other? I'll see if I can resolve that. Update: I had all my subdomains pointed to 8082 via nginx reverse proxy. I saw that api uses 8081 and adjusted the reverse proxy. Success! ✊ Leaving this here in case anyone else has the same issue.

high-magazine-39815

01/19/2022, 8:05 AM

@User Thanks for the pointers on nginx, unfortunately it didn't quite work out for my particular use case. I'm using a system native nginx reverse proxy in front of docker containers. I have my (reusable template) config that I set up per domain/subdomain, proxying traffic to various docker containers/ports. The docs here look like a good start: https://netmaker.readthedocs.io/en/v0.8.0/server-installation.html#nginx-reverse-proxy-setup-with-https ...but not quite there, it's nginx inside docker, not running on the host machine. When joining, I get the following error:

2022/01/18 23:53:20 [netclient] joining <my net name> at grpc.<my domain>:443
2022/01/18 23:53:21 [netclient] error installing: rpc error: code = Unavailable desc = connection closed before server preface received
2022/01/18 23:53:21 Failed to authenticate: rpc error: code = Unauthenticated desc = Something went wrong with Auto Login: rpc error: code = Unavailable desc = connection closed before server preface received

My nginx config: grpc.domain.conf:

server {
        root /var/www/html;
        server_name grpc.<my domain>;
        client_max_body_size 0;
        underscores_in_headers on;

        location / {
            proxy_pass http://127.0.0.1:50051;
            proxy_set_header Host $host;
            proxy_set_header X-Forwarded-Host $server_name;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Ssl on;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_read_timeout  90;
            proxy_redirect http://127.0.0.1:50051 https://$host;
            proxy_pass_request_headers on;
        }

...the rest is Certbot, redirecting 80>443, fairly standard stuff. Half of the nginx config was my standard template, the rest was adapted from the example config.

bored-island-21407

01/19/2022, 1:00 PM

That error looks like you have an invalid token when trying to join. Please try with a new token

bored-island-21407

01/19/2022, 1:04 PM

Also in your nginx conf it should be limited to ssl port 443

high-magazine-39815

01/19/2022, 5:20 PM

OK will do when I get back to the office.

high-magazine-39815

01/19/2022, 5:22 PM

Re 443, The rest of that server block above is certbot listening on 443 and SSL. There's another block listening on 80 redirecting to 443. Both standard config for me.

high-magazine-39815

01/19/2022, 6:17 PM

Generated a new access key, same error:

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

I think it probably has to do with nginx reverse proxy stuff. Are there any other arguments I'm missing above @User ?

high-magazine-39815

01/19/2022, 6:19 PM

nginx config: https://pastebin.com/m2ThAG2f

high-magazine-39815

01/19/2022, 6:20 PM

I'm assuming "connection closed before server prevace received" mean it's trying to open a connection and for some reason it's not compatible and gets closed. This is on a nginx server with multiple subdomains in separate vhosts that do work. FWIW.

bored-island-21407

01/19/2022, 6:20 PM

the way I usually set up nginx is to put something like the following in /etc/nginx/sites-senabled/

bored-island-21407

01/19/2022, 6:21 PM

server {
        listen 443 ssl; # managed by Certbot
        server_name <server-name>;

        location / {
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host $http_host;
                proxy_set_header X-NginX-Proxy true;

                #proxy_pass http://10.0.0.4;
                proxy_pass http://127.0.0.1:8090;
        }

cool-summer-33659

01/20/2022, 11:57 AM

Hi Team, anyone noticed that ipv6 client settingson nodes are not set anymore?

jolly-london-20127

01/20/2022, 12:33 PM

I have not tested with ipv6 lately. If it's not working we'll need a bug for that

cool-summer-33659

01/20/2022, 1:56 PM

I had that in 0.9.3 as vpn internal ipv6 setting per node. now it is gone in running settings. In the config file of netlient it is shown, but netclient does not set it.... 🤨 🤔

jolly-london-20127

01/20/2022, 2:00 PM

Which OS?

cool-summer-33659

01/20/2022, 4:27 PM

Debian 11 x86 and Ubuntu 20.04 arm64

high-magazine-39815

01/21/2022, 8:37 PM

Is this for the grpc subdomain? Looks pretty close to what I have

bored-island-21407

01/21/2022, 8:44 PM

actually it was for something else but the only that would change for a grpc endpoint is the servername and the proxy_pass endpoint