general
- b
bored-island-21407
04/27/2022, 10:03 PMon the client (129.151.216.73) do
and the certs will be regeneratednetclient pull -n <network-name> - h
hallowed-finland-99691
04/27/2022, 11:21 PMERROR: for netmaker UnixHTTPConnectionPool(host='localhost', port=None): Read t imed out. (read timeout=60) ERROR: for netmaker UnixHTTPConnectionPool(host='localhost', port=None): Read t imed out. (read timeout=60) ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. If you encounter this issue regularly because of slow network conditions, consid er setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60). - h
hallowed-finland-99691
04/27/2022, 11:21 PMports: - "60000-65535:60000-65535/udp" - "8081:8081" - h
hallowed-finland-99691
04/27/2022, 11:22 PMWhen I change to this ports: - "60000-65535:60000-65535/udp" - "8081:8081" - h
hallowed-finland-99691
04/27/2022, 11:23 PMπ - h
hallowed-finland-99691
04/27/2022, 11:25 PMI'm testing netmaker in an extreme way - h
hallowed-finland-99691
04/27/2022, 11:30 PMports: - "65000-65535:65000-65535/udp" - "8081:8081" - b
billowy-scooter-48638
04/27/2022, 11:31 PMIs coredns no longer reachable by external clients? Just upgraded to 0.13 and I canβt query dns - h
hallowed-finland-99691
04/27/2022, 11:32 PMθΏζ ·ζε―δ»₯η»§η» ports: - "65000-65535:65000-65535/udp" - "8081:8081" So we can continue ports: - "65000-65535:65000-65535/udp" - "8081:8081" - f
few-airline-95046
04/28/2022, 7:24 AMThat did solve the openssl errors in the mq log, but the problem is that the client is hanging during the join process. so I had to ctrl+c that node, and then do the netclient pull. - f
few-airline-95046
04/28/2022, 10:17 AMHmm, might have found a bug in the external client cfg for 0.13.0. One node is acting as egress, so AllowedIPs in the external client config is supposed to have a comma separated list right? The netmaker network, and the egressed network. It looks like an extra comma got it's way in there so the config doesn't workAllowedIPs = 10.10.100.0/24,,192.168.1.0/24 - j
jolly-london-20127
04/28/2022, 10:52 AMcan you try a join with "-vvv"? would be good to get the error logs - j
jolly-london-20127
04/28/2022, 10:52 AMyeah that's definitely a bug, if you dont mind opening a ticket - f
few-airline-95046
04/28/2022, 10:58 AMThis is the only output I get with --vvv when joining with the noderoot@testmaskin:~# ./netclient join -t <access token> --vvv [netclient] 2022-04-28 07:21:38 joining test at api.netmaker.mydomain.se:443 [netclient] 2022-04-28 07:21:38 node created on remote server...updating configs [netclient] 2022-04-28 07:21:38 starting wireguard [netclient] 2022-04-28 07:21:41 waiting for interface... [netclient] 2022-04-28 07:21:41 interface ready - netclient.. ENGAGE [netclient] 2022-04-28 07:21:41 register at https://api.netmaker.mydomain.se:443/api/server/register [netclient] 2022-04-28 07:21:41 certificates/key saved [netclient] 2022-04-28 07:21:41 local port has changed from 0 to 42061 - j
jolly-london-20127
04/28/2022, 11:00 AMAhhh ok yeah, the next step is to publish a message to the broker. It appears to be hanging on this step. This likely means something is wrong with the broker information, either the certificates (most likely) or the address - j
jolly-london-20127
04/28/2022, 11:00 AMwas this an upgrade or a fresh install? - f
few-airline-95046
04/28/2022, 11:14 AMIt was a fresh install. But I agree, it feels like it's related to the certificates. Installing netmaker with the nm-quick script without specifying my domain and thus using the nm..nip.io address everything seem to be working smoothly, but installing with -d netmaker.mydomain.se I'm running into lots of different issues. - f
few-airline-95046
04/28/2022, 11:15 AMI did as you suggested yesterday and waited the whole night before redoing the install with my domain. The caddy logs looked better then, but still running into the join issues, and nodes doesn't seem to be able to ping each other etc. - b
bored-island-21407
04/28/2022, 11:17 AMhow is your dns setup? are you using wildcards or do you have seperate A/CNAME records for dashboard, api and broker? - f
few-airline-95046
04/28/2022, 11:17 AMwildcard - f
few-airline-95046
04/28/2022, 11:18 AMWhich worked fine (afaik) in 0.12.x π - b
bored-island-21407
04/28/2022, 11:22 AMon the client machine can you run (may have to install mosquitto-clients)mosquitto_pub -t hello -m world -d -h <fqdn of server> -p 8883 --cafile /root/certs/root.pem --cert /root/certs/client.pem --key /root/certs/client.key - f
few-airline-95046
04/28/2022, 11:38 AMoh, alright - f
few-airline-95046
04/28/2022, 11:41 AMroot@testmaskin:~# mosquitto_pub -t hello -m world -d -h nm.129-151-201-102.nip.io -p 8883 --cafile /root/certs/root.pem --cert /root/certs/client.pem --key /root/certs/client.key Error: Problem setting TLS options: File not found. - f
few-airline-95046
04/28/2022, 11:41 AMroot@testmaskin:~# ll /root/certs/ total 24 drwxr-xr-x 2 1883 1883 4096 Apr 26 21:02 ./ drwx------ 6 root root 4096 Apr 27 22:28 ../ -rw-r--r-- 1 1883 1883 119 Apr 26 21:02 root.key -rw-r--r-- 1 1883 1883 542 Apr 26 21:02 root.pem -rw-r--r-- 1 1883 1883 119 Apr 26 21:02 server.key -rw-r--r-- 1 1883 1883 583 Apr 26 21:02 server.pem - f
few-airline-95046
04/28/2022, 11:41 AMno client.pem/key? π - b
bored-island-21407
04/28/2022, 11:42 AMsub server for client - f
few-airline-95046
04/28/2022, 11:48 AMroot@testmaskin:~# mosquitto_pub -t hello -m world -d -h nm.129-151-201-102.nip.io -p 8883 --cafile /root/certs/root.pem --cert /root/certs/server.pem --key /root/certs/server.key Client mosq-6IxlYxoUyLQ3HBbtTv sending CONNECT OpenSSL Error[0]: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed Error: A TLS error occurred.