SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-24 15:03:59 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Connectivity Issue with MQTT Server After Netbird Uptime #1163

New Issue
Closed
opened 2025-11-20 05:25:06 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:25:06 -05:00
Owner
Copy Link

Originally created by @velison1-mbed on GitHub (Aug 20, 2024).

Description:

Hello,

I’m experiencing an issue with the Netbird service on my device. After the service has been running for a while, it fails to connect to the MQTT server at mqtt.xxxx.ai at the same time I can connect the device. This problem occurs intermittently, and a restart of the Netbird service temporarily resolves the issue.

Details:

Devices: Raspberry Pi Zero W

Netbird Versions:
Daemon version: 0.28.7
CLI version: 0.28.7

Network Configuration:

Working Device:
NetBird IP: 100.116.136.203
Connectivity to mqtt.xxxx.ai is successful initially.

Non-Working Device:
NetBird IP: 100.116.106.3
Fails to ping mqtt.xxxx.ai after some time.

Network Routes:

Working Device:
default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.195 metric 100
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.188 metric 600
100.116.0.0/16 dev wt0 proto kernel scope link src 100.116.136.203
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.195 metric 100
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.188 metric 600

Non-Working Device:
default via 192.168.16.1 dev eth0 proto dhcp src 192.168.16.114 metric 100
100.116.0.0/16 dev wt0 proto kernel scope link src 100.116.106.3
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.16.0/24 dev eth0 proto kernel scope link src 192.168.16.114 metric 100

Steps to Reproduce:

Start the Netbird service on both devices.
Monitor connectivity to mqtt.freshsens.ai over time.
Observe that after some time, the non-working device fails to connect to the server.
Restarting Netbird on the non-working device temporarily resolves the issue.

Expected Behavior:

Both devices should consistently be able to connect to mqtt.xxxx.ai without requiring a restart of the Netbird service.

Additional Information:

Restarting the Netbird service resolves the issue temporarily.
The problem seems related to the handling of network routes or connectivity after prolonged uptime.
I would appreciate any assistance or suggestions for resolving this issue.

Thank you!

Originally created by @velison1-mbed on GitHub (Aug 20, 2024). Description: Hello, I’m experiencing an issue with the Netbird service on my device. After the service has been running for a while, it fails to connect to the MQTT server at mqtt.xxxx.ai at the same time I can connect the device. This problem occurs intermittently, and a restart of the Netbird service temporarily resolves the issue. **Details:** Devices: Raspberry Pi Zero W Netbird Versions: Daemon version: 0.28.7 CLI version: 0.28.7 Network Configuration: Working Device: NetBird IP: 100.116.136.203 Connectivity to mqtt.xxxx.ai is successful initially. Non-Working Device: NetBird IP: 100.116.106.3 Fails to ping mqtt.xxxx.ai after some time. Network Routes: Working Device: default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.195 metric 100 default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.188 metric 600 100.116.0.0/16 dev wt0 proto kernel scope link src 100.116.136.203 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.195 metric 100 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.188 metric 600 Non-Working Device: default via 192.168.16.1 dev eth0 proto dhcp src 192.168.16.114 metric 100 100.116.0.0/16 dev wt0 proto kernel scope link src 100.116.106.3 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.16.0/24 dev eth0 proto kernel scope link src 192.168.16.114 metric 100 Steps to Reproduce: Start the Netbird service on both devices. Monitor connectivity to mqtt.freshsens.ai over time. Observe that after some time, the non-working device fails to connect to the server. Restarting Netbird on the non-working device temporarily resolves the issue. Expected Behavior: Both devices should consistently be able to connect to mqtt.xxxx.ai without requiring a restart of the Netbird service. Additional Information: Restarting the Netbird service resolves the issue temporarily. The problem seems related to the handling of network routes or connectivity after prolonged uptime. I would appreciate any assistance or suggestions for resolving this issue. Thank you!
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:25:06 -05:00
saavagebueno commented 2025-11-20 05:25:07 -05:00
Author
Owner
Copy Link

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

Hello @velison1-mbed,

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 @velison1-mbed, 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:25:07 -05:00
Author
Owner
Copy Link

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

Hello @velison1-mbed,

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 @velison1-mbed, 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:25:07 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 1, 2025):

closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.

@mlsmaycon commented on GitHub (Jun 1, 2025): closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.
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 waiting-feedback
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#1163
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?