Operations

Logs and Diagnostics

Read status, logs, and test the network from the correct location.

Basic Status

docker compose ps
docker compose logs --tail 200 nasdash
curl -i http://127.0.0.1:2504/api/health

Testing from NasDash

The decisive test for an integration is performed from the container:

Docker management is optional. Choose Portainer, Dockhand, an HTTP(S) Docker-compatible API, or a Unix socket. The local socket proxy is one option; Portainer and Dockhand do not require it. See Docker connections.

The default command starts NasDash alone. For the optional local proxy, run the command below, then choose Address in Settings → Integrations → Docker. Enter docker-proxy in the host field and 2375 in the port field; the resulting endpoint is http://docker-proxy:2375. Keep the profile enabled on recreates and preserve the existing data mount.

docker compose --profile docker-proxy up -d
docker compose exec nasdash node -e "fetch('http://docker-proxy:2375/_ping').then(r=>r.text()).then(console.log)"

Adapt the URL for Glances or LHM. For Proxmox and APIs with secrets, avoid writing the token in the shell history.

Useful Information in a Report

  • Image version or digest;
  • Storage type, without archive or secret;
  • Compose file used;
  • Cleaned log excerpt;
  • URL reduced to schema, anonymized host, and port;
  • Result of the test from the container.

Never publish .env, cookies, Tailscale Client Secret, Proxmox token, or private ICS URL.