Boot refusals and warnings

The backend refuses to boot in production

[boot] ERROR: Failed to start the application Error: Insecure secret configuration detected:
  - AUTH_SECRET is too short (9 chars; require >= 32).
  - ADMIN_MCP_API_KEY is too short (19 chars; require >= 32).
  - INTERNAL_API_TOKEN is unset.

or AUTH_SECRET matches placeholder pattern ^docker-dev-.

Why: validateSecrets in backend/src/main.ts. What refuses boot lists every backend check.

Fix: set each one to a fresh value from openssl rand -base64 32. AUTH_SECRET and INTERNAL_API_TOKEN must be the same on the frontend.

A half-configured billing setup stops boot too, in any environment:

STRIPE_SECRET_KEY is set but STRIPE_WEBHOOK_SECRET is missing.

Set STRIPE_WEBHOOK_SECRET, or remove every STRIPE_* variable to run without billing. See Billing.

The frontend exits at startup with Refusing to start

Refusing to start: 1 production env problem(s).
Missing required production env var(s): AUTH_URL, INTERNAL_API_TOKEN. ...

Why: instrumentation.ts exits on any problem frontend/lib/required-runtime-env.ts finds. What refuses boot lists them.

Fix: set the variables it names. Frontend variables says what each one is for.

A warning you can ignore: A Node.js API is used

npm run dev and npm run build in frontend/ print:

Warning: A Node.js API is used (process.stderr at line: 67) which is not supported in the Edge Runtime.

Why: a static scan of instrumentation.ts. That line only runs in the Node runtime, and the comment above it says why the warning stays. Nothing to fix.

Related

• Troubleshooting - all entries
• In the browser