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

Unable to reach /api/peers, receive 404 #1148

New Issue
Closed
opened 2025-11-20 05:24:51 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:24:51 -05:00
Owner
Copy Link

Originally created by @velopsiraptor-github on GitHub (Aug 11, 2024).

Describe the problem

I deployed netbird (self-hosted) via the advanced guide. I have netbird running successfully and authenticating with Zitadel. However, when attempting to query /api/peers via curl or anything else to use the API, I get a 404. It seems that the management UI has /peers, and when I go to /api/peers in the UI, it redirects me back to /peers.

I can only assume that I have something misconfigured, but I swear I've looked over everything and I can't seem to find anything that would point me in the right direction. Has this been seen before? Is there an easy solution or place I can start looking to resolve this?

Are you using NetBird Cloud?

Self-hosted

NetBird version

0.28.7

NetBird status -dA output:

Unable to run this, netbird running in docker, no apparent netbird binary in any of the containers.

Additional context

Clients seem to connect just fine and are able to ping each other over the tunnel IPs. Just not sure why /api/peers is returning a 404, along with other /api/* routes.

Originally created by @velopsiraptor-github on GitHub (Aug 11, 2024). **Describe the problem** I deployed netbird (self-hosted) via the advanced guide. I have netbird running successfully and authenticating with Zitadel. However, when attempting to query `/api/peers` via curl or anything else to use the API, I get a 404. It seems that the management UI has `/peers`, and when I go to `/api/peers` in the UI, it redirects me back to `/peers`. I can only assume that I have something misconfigured, but I swear I've looked over everything and I can't seem to find anything that would point me in the right direction. Has this been seen before? Is there an easy solution or place I can start looking to resolve this? **Are you using NetBird Cloud?** Self-hosted **NetBird version** 0.28.7 **NetBird status -dA output:** Unable to run this, netbird running in docker, no apparent `netbird` binary in any of the containers. **Additional context** Clients seem to connect just fine and are able to ping each other over the tunnel IPs. Just not sure why `/api/peers` is returning a `404`, along with other `/api/*` routes.
saavagebueno added the triage-needed label 2025-11-20 05:24:51 -05:00
saavagebueno commented 2025-11-20 05:24:51 -05:00
Author
Owner
Copy Link

@pascal-fischer commented on GitHub (Aug 12, 2024):

Hi @velopsiraptor-github,
the /api/* paths are part of the management backend service while /peers is part of the dashboard. So depending on your setup those will most likely have different domains configured. Your dashboard (opening /peers) is running fine correct? You can use the developer tools in your browser and check the API calls to find the correct address.

@pascal-fischer commented on GitHub (Aug 12, 2024): Hi @velopsiraptor-github, the `/api/*` paths are part of the management backend service while `/peers` is part of the dashboard. So depending on your setup those will most likely have different domains configured. Your dashboard (opening `/peers`) is running fine correct? You can use the developer tools in your browser and check the API calls to find the correct address.
saavagebueno commented 2025-11-20 05:24:51 -05:00
Author
Owner
Copy Link

@velopsiraptor-github commented on GitHub (Aug 12, 2024):

Ah, so that makes sense! I appreciate the reply! It looks like the /api routes are over 33073 (which is the management port). Thanks for at least getting me to a place where I can confirm the information I needed. Much appreciated.

@velopsiraptor-github commented on GitHub (Aug 12, 2024): Ah, so that makes sense! I appreciate the reply! It looks like the `/api` routes are over `33073` (which is the management port). Thanks for at least getting me to a place where I can confirm the information I needed. Much appreciated.
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#1148
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?