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

Allow restarting Netbird service on peers from the dashboard or via API #2427

New Issue
Open
opened 2025-11-20 07:09:38 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 07:09:38 -05:00
Owner
Copy Link

Originally created by @marcportabellaclotet-mt on GitHub (Oct 31, 2025).

Is your feature request related to a problem? Please describe.
When managing peers from the Netbird dashboard, it’s currently not possible to trigger a service restart remotely. This can be frustrating when a peer becomes unresponsive, as the only way to recover is to manually restart the Netbird service on the host. This limits operational efficiency, especially in larger environments where peers are distributed across many machines. There are several open issues where restarting the Netbird service resolves connection problems.

Describe the solution you'd like
I’d like to add an option in the Netbird dashboard (and API) to remotely trigger a Netbird service restart for specific peers. This action would allow administrators to restart the Netbird service on a peer from the UI, helping recover connectivity issues or apply configuration changes without requiring SSH or direct host access.

Describe alternatives you've considered
Manually connecting to the peer via SSH and restarting the service (not scalable).

Using external automation tools (e.g., Ansible, MDM, or custom scripts) to restart the service, but these approaches add unnecessary complexity and security overhead.

Additional context
This feature would improve remote management and troubleshooting for distributed peers, especially in production or enterprise setups. It could be implemented with proper authentication and logging to ensure secure and auditable operations.

Originally created by @marcportabellaclotet-mt on GitHub (Oct 31, 2025). **Is your feature request related to a problem? Please describe.** When managing peers from the Netbird dashboard, it’s currently not possible to trigger a service restart remotely. This can be frustrating when a peer becomes unresponsive, as the only way to recover is to manually restart the Netbird service on the host. This limits operational efficiency, especially in larger environments where peers are distributed across many machines. There are several open issues where restarting the Netbird service resolves connection problems. **Describe the solution you'd like** I’d like to add an option in the Netbird dashboard (and API) to remotely trigger a Netbird service restart for specific peers. This action would allow administrators to restart the Netbird service on a peer from the UI, helping recover connectivity issues or apply configuration changes without requiring SSH or direct host access. **Describe alternatives you've considered** Manually connecting to the peer via SSH and restarting the service (not scalable). Using external automation tools (e.g., Ansible, MDM, or custom scripts) to restart the service, but these approaches add unnecessary complexity and security overhead. **Additional context** This feature would improve remote management and troubleshooting for distributed peers, especially in production or enterprise setups. It could be implemented with proper authentication and logging to ensure secure and auditable operations.
saavagebueno added the feature-request label 2025-11-20 07:09:38 -05:00
saavagebueno commented 2025-11-20 07:09:39 -05:00
Author
Owner
Copy Link

@mitchplze commented on GitHub (Nov 1, 2025):

This would be incredibly helpful, agreed. There are many times when a machine comes out of sleep, or just needs a kick to make things work again. This would be a huge timesaver.

@mitchplze commented on GitHub (Nov 1, 2025): This would be incredibly helpful, agreed. There are many times when a machine comes out of sleep, or just needs a kick to make things work again. This would be a huge timesaver.
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 feature-request
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#2427
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?