mirror of
https://github.com/netbirdio/docs.git
synced 2026-10-19 03:59:05 +02:00
31 lines
1.8 KiB
Plaintext
31 lines
1.8 KiB
Plaintext
export const description =
|
|
"Self-hosted NetBird dashboard troubleshooting: blank pages and unauthorized or 403 errors."
|
|
|
|
# Dashboard issues
|
|
|
|
Problems with the self-hosted dashboard. For other areas, start from [Troubleshooting](/selfhosted/troubleshooting).
|
|
|
|
## Dashboard shows blank page
|
|
|
|
**Symptom**: The dashboard loads but renders a blank page, sometimes with errors in the browser console.
|
|
|
|
**Likely causes and fixes** (most common first):
|
|
|
|
1. **The dashboard can't reach the Management API.** Open the browser console (F12 → Console) and look for failed requests. Confirm `NETBIRD_MGMT_API_ENDPOINT` in `dashboard.env` is your public NetBird URL and is reachable from the browser.
|
|
2. **CORS (Cross-Origin Resource Sharing) errors behind a custom reverse proxy.** netbird-server already sends CORS headers, so don't add them on the proxy: duplicate `Access-Control-Allow-Origin` headers make browsers reject the response. CORS errors can also mean the proxy doesn't route `/api` and `/oauth2` to netbird-server, so the browser gets a response from something else.
|
|
3. **A stale cached bundle.** Hard-reload the page or clear the browser cache.
|
|
|
|
**Confirm**: Reload the dashboard. The login or peers view renders, and the console shows no failed API requests.
|
|
|
|
## "Unauthorized" or "403" errors
|
|
|
|
**Symptom**: API calls return 401 Unauthorized or 403 Forbidden.
|
|
|
|
**Likely causes and fixes** (most common first):
|
|
|
|
1. **An expired or invalid token.** Re-authenticate. For direct API access, use a valid Personal Access Token (PAT).
|
|
2. **The user lacks permission** for the action. Check the user's role in the dashboard.
|
|
3. **Management can't validate the token.** Review `docker compose logs netbird-server` (`management` on installs from before v0.65.0) for token-validation errors.
|
|
|
|
**Confirm**: Re-run the action. It succeeds, and the Management logs show no auth errors.
|