Guide
Fix CLI connection and setup errors
Recover public developer onboarding without private repository access.
Fix CLI connection and setup errors
Use the quickstart. Developer setup does not require Core cloning, GitHub tokens, private Composer packages, or local tenant databases. If an older guide asks for those, return to the public CLI path.
Find your symptom
| Symptom | Next step |
|---|---|
nexia is not found | Install Node.js 22+ and npm install --global @nexia/cli@alpha; reopen the terminal and check the npm executable path. |
| Browser approval expires | Run nexia login <project-id> again and approve the new code in the project console. |
| Sandbox is not ready or expired | Open your project workspace page; wait for provisioning or renew the sandbox. |
| Local app cannot connect | Keep nexia dev my-app running and use its loopback address. Check the project and workspace match. |
| App is bound to another project | Run nexia link my-app after approving the intended project. Verify the printed target. |
| Existing version has different contents | Increase the version in nexia.json, validate, and submit again. |
| Connection is revoked | Sign in and approve a new CLI connection. |
Report persistent errors at Developer Support, including OS, CLI version, project name, incident time, and sanitized reproduction steps. Never share tokens, passwords, or customer data.
Verify
Code example
Shell
nexia status
nexia validate my-app