Skip to main content

​
Sign-in fails

Check that both ROOT_EMAIL and ROOT_PASSWORD are configured on the API and that it was restarted after changing them. The password is exact; email comparison ignores case and surrounding whitespace. Invalid credentials share the same error. A rate limit returns HTTP 429; wait for Retry-After before trying again. Confirm that API and UI UI_BASE_URL values match the exact browser origin. Public origins must use HTTPS. /api-keys creates keys independently of a dashboard session; Settings → API Keys requires a separate root verification for management.

​
A metric is missing

The API distinguishes unknown values from measured zero. Daily numeric dashboard cards display zero when no usable measurement exists; unrecorded mood displays Not recorded, and unavailable weight displays a dash. These display defaults do not create observations. Choose the observation’s date in the installation’s timezone and expand its log. A reported daily total takes precedence over compatible entry subtotals. Incompatible units/definitions, qualified values, voided records and unresolved overlapping workouts can exclude a value from an aggregate. Water means logged water. Exercise uses active energy and explicitly supplied exercise duration. Mood uses the latest valid enum check-in; numeric mood ratings are separate. Use record contracts and goal progress to inspect the returned coverage and exclusions.

​
Weight progress has no start weight

Set a weight goal through REST or MCP with an explicit baseline. Vitalog does not infer it from the first weigh-in. Changing a target retains its baseline unless a replacement is supplied. The current value uses a usable scalar weight on or before the selected date.

​
An API write fails

For an MCP connection issue, see MCP setup and troubleshooting.

​
A deployment is unhealthy

Inspect the API and web service health separately. Check required secrets, database credentials and forward migration logs. Verify ALLOWED_HOSTS, public origins and trusted proxy settings before testing OAuth. Towbar’s manifests and build/resource verification are described in Deploy with Towbar.