2026-02-11 06:15:54 +00:00
|
|
|
# Troubleshooting
|
|
|
|
|
|
2026-02-11 06:30:08 +00:00
|
|
|
## Deep dives
|
|
|
|
|
|
|
|
|
|
- [Troubleshooting deep dive](troubleshooting/README.md)
|
2026-02-11 06:15:54 +00:00
|
|
|
|
2026-02-11 06:30:08 +00:00
|
|
|
This is the high-level troubleshooting entry point (minimal churn).
|
2026-02-11 06:15:54 +00:00
|
|
|
|
|
|
|
|
## Quick triage
|
|
|
|
|
|
|
|
|
|
### Symptom: frontend loads but shows API errors
|
|
|
|
|
- Confirm `NEXT_PUBLIC_API_URL` points to a reachable backend.
|
|
|
|
|
- Check backend `/healthz`.
|
|
|
|
|
|
|
|
|
|
### Symptom: frontend keeps redirecting / Clerk errors
|
|
|
|
|
- If you are running locally without Clerk, ensure `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` is **unset/blank**.
|
|
|
|
|
- See: [repo README Clerk note](../README.md#note-on-auth-clerk).
|
|
|
|
|
|
|
|
|
|
### Symptom: backend 5xx
|
|
|
|
|
- Check DB connectivity (`DATABASE_URL`) and migrations.
|
|
|
|
|
- Check backend logs.
|
|
|
|
|
|
|
|
|
|
## Next
|
|
|
|
|
- Promote the most common issues from `docs/troubleshooting/README.md` into this page once we see repeated incidents.
|
