Troubleshooting
Resolve common errors by symptom.
The interface does not start
Check docker compose ps, then the logs. An inaccessible bind mount for UID 1001, a missing secret, or a port already in use are the first causes to rule out.
An integration works in the browser but not in NasDash
Test from the container. Replace localhost with the Compose service name, a private IP, or a routable DNS name. Check the firewall and routing.
Docker displays 403 or an action fails
The proxy is likely blocking the route. Check CONTAINERS, POST, DELETE, and other permissions. Do not globally enable unnecessary capabilities.
Glances returns HTML
NasDash expects JSON on the /api/<version>/all route. Verify that the Glances web server, rather than a proxy authentication page, is responding.
Proxmox displays 401/403
Check the full Token ID, the secret, the exact node name, and the read role on the correct path. Rotate a compromised secret instead of copying it into logs.
CSS makes the interface unusable
Add ?safe-css=1 to the URL, open developer settings, fix or clear the CSS, then reload without the parameter. See Custom CSS.
Viewers see too much or too little
Check category visibility and the user's allowlists, then log back in as a viewer. Existing sessions may require a new login after a significant change.