Backend not starting
The command runs, but no backend logs appear and the manager ports never bind.
On this page
Symptom
You run the development command. Vite starts and prints its URL, but there are no backend lines and the manager port never accepts a connection. Or the command exits immediately.
Cause
On Windows, the nested npm and concurrently wrapper chain can leave the tsx watch child resident without binding its ports. A second cause is an orphaned process from a previous crash holding PORT or PROXY_PORT. A third is a boot refusal for a missing key, which prints an error before the server starts.
Fix
Read the last line
If it names a key or a port, go straight to that cause. A missing key is a configuration problem, not a process problem.
Use the direct launcher
Run the cross-platform launcher, which spawns the backend and Vite without the npm wrapper chain.
node scripts/start.mjsCheck the ports
Confirm that the manager and proxy ports are listening, and identify anything that holds them.
netstat -ano -p tcp | Select-String ":24084|:9000"Free the orphans
On Windows use the kill-dev helper; otherwise stop the process that holds the port.
Prevention
Start through node scripts/start.mjs on Windows. Keep one terminal for the stack and stop it with Ctrl+C rather than closing the window.