[GH-ISSUE #2452] Connectivity Issue with MQTT Server After Netbird Uptime #4987

Open
opened 2026-08-05 01:00:45 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @velison1-mbed on GitHub (Aug 20, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2452

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). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2452 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 2026-08-05 01:00:45 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4987