NexoToken technical guide center
Codex 401, 404, 429, and response troubleshooting
Narrow Codex failures through authentication, endpoint, model, limits, and stream boundaries.
Do not replace the key, Base URL, and model at the same time when Codex fails. Reproduce one minimal request: inspect credential loading for 401, endpoint and model for 404, concurrency and quota for 429, then stream and proxy behavior for stalled output. Preserve only a redacted timeline and status codes.
For authentication failures, missing paths or models, rate limits, timeouts, empty responses, and interrupted Codex streams.
Last verified
Steps
Fix the model and input, reproduce once, and record the status.
For 401, confirm the current process can read its variable.
For 404, verify Base URL path and complete model ID separately.
For 429, reduce concurrency and inspect automatic retries.
For stalled output, disable buffering and inspect stream completion boundaries.
Safe example
Order: minimal reproduction → 401 auth → 404 endpoint/model → 429 limits → stream boundary
Record status codes, never complete headers.Common errors and troubleshooting order
- Blind retries amplify limits and duplicate work.
- A UI message can hide the real HTTP status.
- Changing several variables destroys diagnostic evidence.
- Complete public logs can expose credentials or user input.
Completion checklist
- A minimal request reproduces the issue.
- Only one variable changes per test.
- Status and time are recorded.
- Shared evidence is redacted.
Limitations and boundaries
- Public guidance provides a general sequence; account-specific cases require official support.
- Client proxies, plugins, and retries can change the actual request count.