Configuration needed
What went wrong
Section titled “What went wrong”Instead of the app, every page shows Configuration needed with a list of problems. API requests return 503 with "Server configuration needed", and /api/health returns 503 with "configured": false.
Why it happens
Section titled “Why it happens”When it starts, Day Planner checks its environment variables. If a required one is missing, or one has an invalid value, it stops serving the app, because running with a broken configuration could be insecure or lose data. Common causes:
BETTER_AUTH_SECRETorBETTER_AUTH_URLisn’t set, or the secret is shorter than 32 characters.BETTER_AUTH_URLhas nohttps://.- Only some of the
OIDC_settings are set. - A setting has a value it doesn’t accept, such as
RATE_LIMIT_STORAGE=redis.
The page names each setting and says what’s wrong, but never shows values.
How to fix it
Section titled “How to fix it”- Fix each listed setting in
.env(or your platform’s environment settings). The configuration reference gives each one’s accepted values. - Restart the app:
docker compose up -d app.
The check runs once at startup, so the page stays until you restart.
See also
Section titled “See also”- Configuration: every setting and its accepted values
- Health endpoint: check the result from a script