Codex
Troubleshooting
Diagnose Passion8 authentication, /v1, Responses support and unavailable models.
Most connection failures involve the credential file, the /v1 base URL suffix, or whether the route supports Responses.
#Connection troubleshooting
| Symptom | Check first | Action |
|---|---|---|
Unauthenticated / 401 | OPENAI_API_KEY in ~/.codex/auth.json | Store the complete key in auth.json, not config.toml. |
| Cannot connect / wrong address | Whether base_url includes /v1 | Use https://passion8.cc/v1. |
404 /v1/responses | Responses support on the route | Choose a Codex-compatible route or update its backend configuration. |
| Model not found | The model setting | Use an enabled Codex / Responses ID from the catalog. |
| Command not found | Node, npm and PATH | Check node -v and npm -v; reopen the terminal. |
| Insufficient balance / quota | Account balance | See Usage and billing. |
Remember: base URL https://passion8.cc/v1; key in the OPENAI_API_KEY field of ~/.codex/auth.json, not in config.toml.
#Still failing?
Send the specific error to support with keys and other sensitive information removed. See Billing and support.
Support
Need help?
For setup, billing, or model issues, email us. Check the status page for uptime.
WeChat / QQ support is available at the bottom right.
