Open mtwardawski opened 4 months ago
I've adjusted the logging to now say:
Connected to NetBird Client process via Unix domain socket at '/var/run/netbird.sock'.
(The logging was not supposed to say that it's connected to the NetBird Server, but rather to the NetBird Client.)
While setting up a new peer with
opendut-edgar setup managed <SETUP STRING>
it may get stuck in state netbird connect. To resolve this issue it was enough to stop the netbird service withsudo systemctl stop netbird.service
.This seems to be not a proper solution, because it requires a manual step and we should handle this in a different automated way.
Also the logs seem to be wrong, since it states that Netbird connection was opend up successfully which was not the case.AC:
and correct the statement when it obviously was not connected successful.