SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-11 09:52:11 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

netbird could not connect after windows 11 updates #1459

New Issue
Open
opened 2025-11-20 05:30:58 -05:00 by saavagebueno · 7 comments
saavagebueno commented 2025-11-20 05:30:58 -05:00
Owner
Copy Link

Originally created by @Slava-Gll on GitHub (Nov 29, 2024).

Describe the problem

netbird could not connect after windows 11 updates

CPU: snapdragon X elite (ARM64, running via windows translation)
OS: Windows 11 24H2 latest

before the update, netbird has worked like a charm.
Also netbird works fine on my other non-ARM machines(though i don't know if they are latest)

To Reproduce

  1. have an ARM laptop with WIN11
  2. install windows updates(KB5048162, or older, i did not update for a week or two)
  3. reboot
  4. try to open some webUI on my remote network(it does not work)
  5. open netbird UI, try to connect(nothing happens)
  6. try to open some webui on my remote subnet(it does not work)

Expected behavior

i expect netbird to connect succesefully

Are you using NetBird Cloud?

No i run a self-hosted NetBird's control plane.

NetBird version

0.33.0

NetBird status -dA output:

command hangs

Do you face any (non-mobile) client issues?

Please provide the file created by netbird debug for 1m -AS.
command also hangs

Screenshots

изображение

Additional context

my relevant programs:
wireguard(at most times turned off)
OpenVPN Connect (at most times turned off)
V2RayN (off while writing this and capturing logs)

i don't know if it has anything to do with my problem,
but recently i had installed java jre8 and supermicro IPMIView20

found the log file at C:\ProgramData\Netbird
client.log part(i removed sensitive information):

2024-11-30T01:20:26+03:00 INFO client/internal/connect.go:242: connecting to the Relay service(s): rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:66: try to connecting to relay server: rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:165: create new relay connection: local peerID: *****************************************, local peer hashedID: ******************************************
2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:171: connecting to relay server
2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:188: relay connection established
2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:84: connected to Relay server: rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:58: chosen home Relay server: rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO client/iface/wgproxy/factory_usp.go:15: WireGuard Proxy Factory will produce bind proxy
2024-11-30T01:20:26+03:00 INFO client/internal/routemanager/manager.go:144: Routing setup complete
2024-11-30T01:20:26+03:00 INFO client/iface/device/device_windows.go:59: create tun interface
2024-11-30T01:20:41+03:00 ERRO client/internal/engine.go:365: failed creating tunnel interface wt0: [error creating tun device: Error creating interface: The device is not ready for use.]
2024-11-30T01:20:41+03:00 INFO client/iface/iface.go:220: interface wt0 has been removed
2024-11-30T01:20:41+03:00 ERRO client/internal/connect.go:266: error while starting Netbird Connection Engine: create wg interface: error creating tun device: Error creating interface: The device is not ready for use.
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:536: closing all peer connections
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:345: start to Relay read loop exit
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:544: waiting for read loop to close
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:546: relay connection closed
2024-11-30T01:20:41+03:00 WARN [relay: rels://netbird.example.com:443] relay/client/client.go:531: relay connection was already marked as not running
2024-11-30T01:20:51+03:00 INFO client/internal/connect.go:242: connecting to the Relay service(s): rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:66: try to connecting to relay server: rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:165: create new relay connection: local peerID: *******************************, local peer hashedID: ****************************
2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:171: connecting to relay server
2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:188: relay connection established
2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:84: connected to Relay server: rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:58: chosen home Relay server: rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO client/iface/wgproxy/factory_usp.go:15: WireGuard Proxy Factory will produce bind proxy
2024-11-30T01:20:51+03:00 INFO client/internal/routemanager/manager.go:144: Routing setup complete
2024-11-30T01:20:51+03:00 INFO client/iface/device/device_windows.go:59: create tun interface

i think the most important part is 2024-11-30T01:20:41+03:00 ERRO client/internal/engine.go:365: failed creating tunnel interface wt0: [error creating tun device: Error creating interface: The device is not ready for use.]

i also bump this #2624, i think that Windows ARM64 build could resolve the issue.

feel free to ask any additional information

Originally created by @Slava-Gll on GitHub (Nov 29, 2024). **Describe the problem** netbird could not connect after windows 11 updates CPU: snapdragon X elite (ARM64, running via windows translation) OS: Windows 11 24H2 latest before the update, netbird has worked like a charm. Also netbird works fine on my other non-ARM machines(though i don't know if they are latest) **To Reproduce** 1. have an ARM laptop with WIN11 2. install windows updates(KB5048162, or older, i did not update for a week or two) 3. reboot 4. try to open some webUI on my remote network(it does not work) 5. open netbird UI, try to connect(nothing happens) 6. try to open some webui on my remote subnet(it does not work) **Expected behavior** i expect netbird to connect succesefully **Are you using NetBird Cloud?** No i run a self-hosted NetBird's control plane. **NetBird version** 0.33.0 **NetBird status -dA output:** command hangs **Do you face any (non-mobile) client issues?** Please provide the file created by `netbird debug for 1m -AS`. command also hangs **Screenshots** ![изображение](https://github.com/user-attachments/assets/efeadb8f-c04b-454d-b11e-f4e4e0e2eb8d) **Additional context** my relevant programs: wireguard(at most times turned off) OpenVPN Connect (at most times turned off) V2RayN (off while writing this and capturing logs) i don't know if it has anything to do with my problem, but recently i had installed java jre8 and supermicro IPMIView20 found the log file at **C:\ProgramData\Netbird** client.log part(i removed sensitive information): ```client.log 2024-11-30T01:20:26+03:00 INFO client/internal/connect.go:242: connecting to the Relay service(s): rels://netbird.example.com:443 2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:66: try to connecting to relay server: rels://netbird.example.com:443 2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:165: create new relay connection: local peerID: *****************************************, local peer hashedID: ****************************************** 2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:171: connecting to relay server 2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:188: relay connection established 2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:84: connected to Relay server: rels://netbird.example.com:443 2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:58: chosen home Relay server: rels://netbird.example.com:443 2024-11-30T01:20:26+03:00 INFO client/iface/wgproxy/factory_usp.go:15: WireGuard Proxy Factory will produce bind proxy 2024-11-30T01:20:26+03:00 INFO client/internal/routemanager/manager.go:144: Routing setup complete 2024-11-30T01:20:26+03:00 INFO client/iface/device/device_windows.go:59: create tun interface 2024-11-30T01:20:41+03:00 ERRO client/internal/engine.go:365: failed creating tunnel interface wt0: [error creating tun device: Error creating interface: The device is not ready for use.] 2024-11-30T01:20:41+03:00 INFO client/iface/iface.go:220: interface wt0 has been removed 2024-11-30T01:20:41+03:00 ERRO client/internal/connect.go:266: error while starting Netbird Connection Engine: create wg interface: error creating tun device: Error creating interface: The device is not ready for use. 2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:536: closing all peer connections 2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:345: start to Relay read loop exit 2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:544: waiting for read loop to close 2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:546: relay connection closed 2024-11-30T01:20:41+03:00 WARN [relay: rels://netbird.example.com:443] relay/client/client.go:531: relay connection was already marked as not running 2024-11-30T01:20:51+03:00 INFO client/internal/connect.go:242: connecting to the Relay service(s): rels://netbird.example.com:443 2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:66: try to connecting to relay server: rels://netbird.example.com:443 2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:165: create new relay connection: local peerID: *******************************, local peer hashedID: **************************** 2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:171: connecting to relay server 2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:188: relay connection established 2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:84: connected to Relay server: rels://netbird.example.com:443 2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:58: chosen home Relay server: rels://netbird.example.com:443 2024-11-30T01:20:51+03:00 INFO client/iface/wgproxy/factory_usp.go:15: WireGuard Proxy Factory will produce bind proxy 2024-11-30T01:20:51+03:00 INFO client/internal/routemanager/manager.go:144: Routing setup complete 2024-11-30T01:20:51+03:00 INFO client/iface/device/device_windows.go:59: create tun interface ``` i think the most important part is `2024-11-30T01:20:41+03:00 ERRO client/internal/engine.go:365: failed creating tunnel interface wt0: [error creating tun device: Error creating interface: The device is not ready for use.]` i also bump this #2624, i think that Windows ARM64 build could resolve the issue. feel free to ask any additional information
saavagebueno added the triage-needed label 2025-11-20 05:30:58 -05:00
saavagebueno commented 2025-11-20 05:30:59 -05:00
Author
Owner
Copy Link

@Slava-Gll commented on GitHub (Dec 5, 2024):

finally it works.
steps i took to fix it:

  1. uninstall netbird
  2. clear ProgramData\Netbird
  3. delete wt2 interface in win control panel
  4. delete wireguard
  5. reboot
  6. fresh install of latest version

i think you should dive deeper in this problem, i couldn't find any information about the settings screen.
also i'm not confident that settings validates input as Netbird stops working on non-standard settings.

@Slava-Gll commented on GitHub (Dec 5, 2024): finally it works. steps i took to fix it: 1. uninstall netbird 2. clear ProgramData\Netbird 3. delete wt2 interface in win control panel 4. delete wireguard 5. reboot 6. fresh install of latest version i think you should dive deeper in this problem, i couldn't find any information about the settings screen. also i'm not confident that settings validates input as Netbird stops working on non-standard settings.
saavagebueno commented 2025-11-20 05:30:59 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @Slava-Gll,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @Slava-Gll, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:30:59 -05:00
Author
Owner
Copy Link

@Slava-Gll commented on GitHub (Apr 28, 2025):

Hi and thanks for reaching out.
The problem appears from time to time, most times after a reboot, so I
tend to not power off my laptop.
NB service freaks out and can't connect due to some bug, i mentioned it in
my issue including some logs.
The only way to fix it is to go to network adapters and delete wt0, then netbird service restart.
I am also confused about the adapter name option in settings, changing
it to anything other than wt0 makes NB not work.
I am willing to hear more news about a possibility of a WIN Arm64 version,
because wireguard is already built for Arm64.

@Slava-Gll commented on GitHub (Apr 28, 2025): Hi and thanks for reaching out. The problem appears from time to time, most times after a reboot, so I tend to not power off my laptop. NB service freaks out and can't connect due to some bug, i mentioned it in my issue including some logs. The only way to fix it is to go to network adapters and delete wt0, then `netbird service restart`. I am also confused about the adapter name option in settings, changing it to anything other than wt0 makes NB not work. I am willing to hear more news about a possibility of a WIN Arm64 version, because wireguard is already built for Arm64.
saavagebueno commented 2025-11-20 05:30:59 -05:00
Author
Owner
Copy Link

@spoletum commented on GitHub (May 1, 2025):

finally it works. steps i took to fix it:

  1. uninstall netbird
  2. clear ProgramData\Netbird
  3. delete wt2 interface in win control panel
  4. delete wireguard
  5. reboot
  6. fresh install of latest version

i think you should dive deeper in this problem, i couldn't find any information about the settings screen. also i'm not confident that settings validates input as Netbird stops working on non-standard settings.

Fixed it for me too.

@spoletum commented on GitHub (May 1, 2025): > finally it works. steps i took to fix it: > > 1. uninstall netbird > 2. clear ProgramData\Netbird > 3. delete wt2 interface in win control panel > 4. delete wireguard > 5. reboot > 6. fresh install of latest version > > i think you should dive deeper in this problem, i couldn't find any information about the settings screen. also i'm not confident that settings validates input as Netbird stops working on non-standard settings. Fixed it for me too.
saavagebueno commented 2025-11-20 05:31:00 -05:00
Author
Owner
Copy Link

@zpnielsen commented on GitHub (Jun 24, 2025):

Wanted to drop in and provide my 2c.

We were facing this issue as well, though in our case, it was observed across both Intel and ARM systems running Windows 11. It looks like the Netbird service that wraps the Wintun driver enters a kind of perpetual crash loop state. If you pop open Windows Device Manager, you'll see the tun interface is being created and deleted repeatedly. The netbird service doesn't gracefully respond to stop requests and times out.

What we did to remedy this problem was was simpler that what was suggested. Our approach was to just to go into Device Manager, right click the Wireguard tunnel interface, and hit, "Uninstall Device." After that, bounce the netbird service (you may not even need to; there's a good chance the netbird service will just crash as a result of us ripping out the tun device in this manner).

When the netbird service re-starts, it will create the tun device as normal and things start working again (until the driver / service screws up again?).

Totally not certain on this, but I'm guessing there could be some relation to this Wintun patch.

@zpnielsen commented on GitHub (Jun 24, 2025): Wanted to drop in and provide my 2c. We were facing this issue as well, though in our case, it was observed across both Intel and ARM systems running Windows 11. It looks like the Netbird service that wraps the Wintun driver enters a kind of perpetual crash loop state. If you pop open Windows Device Manager, you'll see the tun interface is being created and deleted repeatedly. The netbird service doesn't gracefully respond to stop requests and times out. What we did to remedy this problem was was simpler that what was suggested. Our approach was to just to go into Device Manager, right click the Wireguard tunnel interface, and hit, "Uninstall Device." After that, bounce the netbird service (you may not even need to; there's a good chance the netbird service will just crash as a result of us ripping out the tun device in this manner). When the netbird service re-starts, it will create the tun device as normal and things start working again (until the driver / service screws up again?). Totally not certain on this, but I'm guessing there could be some relation to [this Wintun patch](https://git.zx2c4.com/wintun/commit/?id=28627e00f0889f19ecb0abbf013e04bc897ab9f5).
saavagebueno commented 2025-11-20 05:31:00 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Jun 26, 2025):

@zpnielsen could you provide us with an debug bundle upload when you encounter this the next time? https://docs.netbird.io/how-to/troubleshooting-client#debug-bundle-uploads

@nazarewk commented on GitHub (Jun 26, 2025): @zpnielsen could you provide us with an debug bundle upload when you encounter this the next time? https://docs.netbird.io/how-to/troubleshooting-client#debug-bundle-uploads
saavagebueno commented 2025-11-20 05:31:00 -05:00
Author
Owner
Copy Link

@YapWC commented on GitHub (Jul 19, 2025):

I faced the same issue but after uninstalling the Netbird Program via Control Panel and reinstalled the latest Netbird v0.51.1 everything was working again!

@YapWC commented on GitHub (Jul 19, 2025): I faced the same issue but after uninstalling the Netbird Program via Control Panel and reinstalled the latest Netbird v0.51.1 everything was working again!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label triage-needed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1459
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?