After upgrading a node from 0.13.0 to 0.14.2 I stop being able to connect to it #281

Open
opened 2025-11-20 05:09:02 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @rgl on GitHub (Mar 4, 2023).

Describe the problem

After upgrading a ubuntu machine from 0.13.0 to 0.14.2 I stop being able to connect to it tru the netbird/wireguard IP address. If I downgrade to 0.13.0 it works again.

The ubuntu machine is inside an unknown corporate network. So I do not really known what is going on between it and my windows home machine (using netbird 0.14.2).

Any help trying to troubleshoot this would be welcome.

Expected behavior

I expected to keep using netbird/wireguard network after upgrade.

NetBird status -d output:

With 0.13.0:

Peers detail:
 home.netbird.cloud:
  NetBird IP: 100.X.X.123
  Public key: XXX
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/prflx
  Last connection update: 2023-03-04 12:38:51
...
Daemon version: 0.13.0
CLI version: 0.13.0
Daemon status: Connected
Management: Connected to https://api.wiretrustee.com:443
Signal: Connected to https://signal2.wiretrustee.com:443
Domain: xxx.netbird.cloud
NetBird IP: 100.X.X.124/16
Interface type: Kernel
Peers count: 2/5 Connected

With 0.14.2, it never leaves the Connecting state:

Peers detail:
 home.netbird.cloud:
  NetBird IP: 100.X.X.123
  Public key: XXX
  Status: Connecting
  -- detail --
  Connection type:
  Direct: false
  ICE candidate (Local/Remote): -/-
  Last connection update: 2023-03-04 12:53:13
Originally created by @rgl on GitHub (Mar 4, 2023). **Describe the problem** After upgrading a ubuntu machine from 0.13.0 to 0.14.2 I stop being able to connect to it tru the netbird/wireguard IP address. If I downgrade to 0.13.0 it works again. The ubuntu machine is inside an unknown corporate network. So I do not really known what is going on between it and my windows home machine (using netbird 0.14.2). Any help trying to troubleshoot this would be welcome. **Expected behavior** I expected to keep using netbird/wireguard network after upgrade. **NetBird status -d output:** With 0.13.0: ``` Peers detail: home.netbird.cloud: NetBird IP: 100.X.X.123 Public key: XXX Status: Connected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote): relay/prflx Last connection update: 2023-03-04 12:38:51 ... Daemon version: 0.13.0 CLI version: 0.13.0 Daemon status: Connected Management: Connected to https://api.wiretrustee.com:443 Signal: Connected to https://signal2.wiretrustee.com:443 Domain: xxx.netbird.cloud NetBird IP: 100.X.X.124/16 Interface type: Kernel Peers count: 2/5 Connected ``` With 0.14.2, it never leaves the `Connecting` state: ```plain Peers detail: home.netbird.cloud: NetBird IP: 100.X.X.123 Public key: XXX Status: Connecting -- detail -- Connection type: Direct: false ICE candidate (Local/Remote): -/- Last connection update: 2023-03-04 12:53:13 ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#281