Stratum guide

Troubleshoot Stratum

Diagnose startup, persistence, browser, WebSocket, database, SSO, and container issues.

Start with the health endpoint, container logs, browser network panel, and stateless-mode banner. Never post tokens, passwords, connection strings, or proprietary architecture payloads publicly.

The UI does not open

  • Confirm port 8080 is published.
  • Open http://localhost:8080/healthz.
  • Ensure the reverse proxy does not block compiled assets with an incompatible Content Security Policy.

Changes disappear after restart

Stratum is stateless. Configure DATABASE_URL or connect PostgreSQL through admin storage, test it, and migrate bootstrap users.

The backend reports pending migrations

Run /migrate status from the same image tag as the application, take a verified backup, apply /migrate up with the migration role, and require /migrate check to succeed. Do not edit migration files or enable automatic migration merely to bypass a failed deployment gate.

API or WebSocket requests fail

For split deployments, route /api and /ws to the backend, include the UI origin in ALLOWED_ORIGINS, and allow WebSocket upgrades.

SSO redirects fail

Compare the exact HTTPS callback URL in Okta and Stratum. Verify issuer, client ID, secret, scopes, and group claim.

The canvas reports an error

Refresh once and verify the selected design/version. Reset only when you accept losing the unsaved local draft. Record a reproducible action sequence without architecture data.

Release information

Check the container package for tags and the public repository for product guidance and feedback.