-
-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netbird won't reconnect to other windows peer on reboot until I ping the peer #2860
Comments
It seems like a crash. @Mikesco3 can you check if there was any event in the event viewer (system and applications)? |
I just have 2 Event ID 86
|
Could you please run the following command in an elevated powershell:
then try to reproduce the issue? If you can reproduce it, you should see a file in C:\ProgramData\netbird\netbird.err. Please share it with us. |
etc...
etc... |
I can refer to the system practically right away from the netbird IP... Update Temporary solution
|
can you share the client logs? You can bundle them with: netbird debug bundle -A |
Here are the logs... |
BTW, I don't know if this makes a difference or not...
So I don't know if there are any leftovers in the registry, that could point to the old vps?? |
However this wouldn't make sense, because I'm also having the issue on machines that never had Netbird before... |
For now my solution has been to add the IP's for the machines I need to reach to the host file and that worked. It's not a pretty fix but it's working like a charm. |
Describe the problem
Windows clients can't reach peers untill I ping them.
I believe the issue is prevalent after reboots and I haven't het monitored if it drops later during the day.
To Reproduce
Steps to reproduce the behavior:
Are you using NetBird Cloud?
I'm using the NetBird SelfHosted control plane.
NetBird version
0.31.0
Expected behavior
A clear and concise description of what you expected to happen.
I have a few computers connected on different locations and I'm using Netbird to connect them together.
Installed the Netbird client and joined it to the control pane and did the same on other windows PCs across the internet
When I reboot the computer, I cannot reach the other Peer across netbird.
What seems to help is if I ping the computer, and then after that I can reach the computer.
I haven't checked if after a while it drops or not.
What I would hope is that if I have another windows computer connected from a different location via netbird, I would be able to reconnect to it, even if I have to wait for a bit untill the other services come back online (at least that works with zerotier and other similar products)
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Then if I ping the peer I'm trying to access, after a (3 to 5 second) pause it starts replying to pings and then I can connect to it fine
Slight pause (3 to 5 seconds)
Then we can connect to the Peer Windows PC with no issues...
Attachments
I've attached a copy of my config files:
docker-compose.yml
management.json
config.json
NetBird status -dA output:
If applicable, add the `netbird status -dA' command output.
I grabbed the output while the computer wasn't having the connection issues and before I pinged the peer.
The text was updated successfully, but these errors were encountered: