Troubleshooting
Start with doctor
Section titled “Start with doctor”quox doctorquox statusThese check the platform services the CLI can see and report what is unhealthy.
Not signed in (exit code 4)
Section titled “Not signed in (exit code 4)”Run quox login, or pick the right profile with --profile <name>. quox whoami shows the current session. If your default profile is an agent login, it cannot chat: pass -p <your profile>.
“fetch failed” on a self-signed QuoxCORE
Section titled ““fetch failed” on a self-signed QuoxCORE”A local QuoxCORE often uses a self-signed certificate. Trust its certificate for the session:
export NODE_EXTRA_CA_CERTS=/path/to/your-quoxcore-cert.pem--insecure also works but turns off certificate checks, so use it only on a machine you control.
No QuoxCORE to talk to
Section titled “No QuoxCORE to talk to”Quox starts anyway and says No QuoxCORE running at <url>, or that the server is not answering. It cannot do much without one. See the prerequisite.
The wrong organisation
Section titled “The wrong organisation”Use --org <slug> for one command, or quox config to see and change profiles.
Colours look wrong
Section titled “Colours look wrong”Pass --no-color, or set NO_COLOR=1.
Still stuck
Section titled “Still stuck”Run the failing command with --debug to see the HTTP request and response, then check the command reference.