Rip out and replace problems on Ubuntu 22.04
# installb
broad-elephant-83981
01/26/2023, 10:06 AMJust ripped out and replaced 0.16.3 with 0.17.1 ... but seeing this after starting
``[netmaker] 2023-01-26 10:02:39 connecting to mq broker at ws://mq:1883 with TLS? false
[netmaker] Fatal: Admin: could not connect to broker, token timeout, exiting ...
``
And cannot view the new dashboard because:
``Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.``
broad-elephant-83981
01/26/2023, 10:08 AMMight be a PEBCAT typo error ... trying again
broad-elephant-83981
01/26/2023, 10:12 AMAfter fixing typo, dashboard now works ... but I am seeing my old ripped out network in it.
And I did a docker system prune before installing again from scratch ... is this normal?
b
bored-island-21407
01/26/2023, 10:28 AMdid you include volumes in your system prune? If not, then seeing the old network is expected behaviour
b
broad-elephant-83981
01/26/2023, 11:02 AMI did a prune -a, but I now had to delete all the volume directories too before proceeding
b
bored-island-21407
01/26/2023, 11:03 AMdocker system prune -a --volumesb
broad-elephant-83981
01/26/2023, 11:03 AMOk, thanks
broad-elephant-83981
01/26/2023, 11:40 AM@bored-island-21407 wondering ... can coredns be used for custom dns proxying again?
b
bored-island-21407
01/26/2023, 11:44 AMcoredns is only used for extclients
b
broad-elephant-83981
01/26/2023, 12:11 PMOk
broad-elephant-83981
01/26/2023, 12:15 PMI have node that Im using for dns resolution, also using coredns.
Whenever I create a relay with the netmaker node, for nodes on problematic networks (reason for this is some netclients start to blackhole routes to other nodes), the relayed nodes stop being able to resolve names with the coredns node.
Telnet to coredns works, its pingable, etc.
Any idea why this could happen?
b
bored-island-21407
01/26/2023, 12:18 PMcan the relayed nodes ping the coredns node?
b
broad-elephant-83981
01/26/2023, 12:44 PMYes they can
b
bored-island-21407
01/26/2023, 1:06 PMwhat is response from
nslookup google.com <ip address of coredns node>b
broad-elephant-83981
01/26/2023, 1:06 PMFrom a relayed node?
b
bored-island-21407
01/26/2023, 1:06 PMyes
b
broad-elephant-83981
01/26/2023, 1:06 PMI'll setup relaying again, one moment
broad-elephant-83981
01/26/2023, 1:07 PMBut from old attempts ...
broad-elephant-83981
01/26/2023, 1:12 PM``nslookup google.com 10.254.0.1
Server: 10.254.0.1
Address: 10.254.0.1#53
Non-authoritative answer:
Name: google.com
Address: 172.217.169.46
Name: google.com
Address: 2a00:1450:4009:820::200e
``
broad-elephant-83981
01/26/2023, 1:12 PMThis works
broad-elephant-83981
01/26/2023, 1:12 PMIts resolving names behind egress networks that appears to fail
broad-elephant-83981
01/26/2023, 1:13 PMFor example:
``nslookup gateway.production.qrios.com 10.254.0.1
Server: 10.254.0.1
Address: 10.254.0.1#53
** server can't find gateway.production.qrios.com: NXDOMAIN
``
broad-elephant-83981
01/26/2023, 1:13 PMBut once I delete the relaying it resumes working
3 Views