"AUTH_SECRET is missing or too short"
.env has no AUTH_SECRET, or it is shorter than 16 characters. Generate one (see Installation) and restart.
"Settings row missing: run npm run db:seed"
The tables exist but are empty. Run npm run db:seed.
I cannot sign in to the dashboard
- The owner account is created only when the staff table is empty. If you changed
OWNER_EMAILafter the first seed, the old address is still the owner. Reset withnpm run db:reset(this deletes all data) or update the email in the database. - After 8 failed attempts on one email, or 10 per minute from one IP, sign-in answers "Too many requests" for a few minutes.
- A deactivated account cannot sign in.
Every change in the dashboard says "read-only demo"
DEMO_MODE is true in .env. Set it to false and restart. See Demo mode.
Uploaded photos do not appear
- Uploads are saved in
UPLOAD_DIR(defaultstorage/uploads) and served at/uploads/<file>. The folder must be writable by the app. - Files larger than
UPLOAD_MAX_MB(default 8) are refused. Behind Nginx, raiseclient_max_body_sizetoo. - Only JPEG, PNG and WebP are accepted; the file type is checked from its content, not its name.
An agent cannot see a listing or an inquiry
That is by design: agents see only the listings and inquiries assigned to them. An admin can assign them (listing editor > Agent, or Inquiries > Assigned agent). See Admins and roles.
A status change is refused ("bad_transition")
Listings, inquiries and viewings follow fixed status flows (for example a rental can be RENTED but not SOLD, and a viewing must be confirmed before it is done). The dashboard only offers allowed steps; the API refuses the rest. The flows are in src/lib/rules.ts.
The AI pages say they are not switched on
Set the variables in AI assistant or AI staging studio and restart. If the provider answers with an error, the dashboard shows it ("The AI service did not answer properly: HTTP 401" usually means a wrong key).
Several server instances
The request limiter in src/lib/api.ts keeps counts in memory, per process. With more than one instance, replace it with a shared store (Redis, or a database table), use PostgreSQL, and put uploads on shared storage.
Port 3303 is already in use
Another process (often an earlier next start) holds the port. Stop it, or change the port in the dev and start scripts of package.json.