Netbird seems to "die" on my server #3107
Labels
Comments
|
Hello @GronbergInfo thanks for reporting the issue, can you please run the following commands on the server and one of the clients? Enable debug information # enable trace logs:
netbird debug log level trace
# enable network map report
netbird debug persistence onWhen the issue happens again: netbird debug bundle -SAThis will generate an anonymized bundle file with log information. Then, please share them with us. |
mlsmaycon
added
bug
|
Also, can you confirm that the issue happens on SSH connections with the server or, in general, the peer connection 'dies' and you can't even ping it? and how long does it take to have issues? |
From client: netbird.debug.3148610165.zip From Server: netbird.debug.1025569393.zip |
It seems everything "dies" but hostname lookup |
|
@GronbergInfo it doesn't seem like you executed the commands as shared in #3107 (comment). Can you please do the exact steps? Also, can you provide an answer to the following questions?
|
nbd.txt - client
|
|
still 15 or so minutes later, it still up and running. |
|
It is caused by the key not being rotated due to a firewall issue. We are missing a default allow rule for rosenpass. If this continues, can you add a UDP rule like the one in the image and try again? We will be working on a permanent fix. 
|
Even with this setting, it seems it dies with quantum enabled. |
|
Thanks @GronbergInfo , can you please enable the logs and share them with us once the connection fail? we are running the same test on our side too. |
Did the log thing on both ends. client server this time the connection died nearly instantly when switching both sides to --enable-rosenpass=true |
|
Update: forgot to mention the downtime detection was at around I am not sure if this is related, but each time, one of my servers, which does auto-upgrade at around 6 pm, dies after upgrading to 0.35.1. Right now, it would seem that at least for me, client 0.29.4 is the last stable version I can rely on to work well: /var/log/apt/history.log cat /var/log/netbird/client.log |
|
same issue I have. |
|
Same for me. Seems to be something from 0.31 upwards. With 0.31 I don't see those problems. Maybe it's related to the fix for this issue: #2973 ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I run
sudo netbird down && sudo netbird up --allow-server-sshOn the server, and it starts to work, then after a uncertain time, it just stops communicate, resolve dns and such until i run that command again
client and server has netbird 0.35.0.
If i ssh into the server using lan ip and check netbird status, it looks ok/normal
EDIT: just added 2 peers (laptop + android tablet) and it died for the server again.
The text was updated successfully, but these errors were encountered: