How do I troubleshoot slow connections or failed requests?
Read the status code and the error text before you change the address. A backup domain does not fix a bad key, a wrong model, or a missing endpoint.
Match the symptom
| What you see | Check first |
|---|---|
| 401 | The key is complete and has not been rotated or disabled. A new terminal has picked up the environment variable |
| 403 or model unavailable | Endpoint selection has a saved endpoint for this model family. The model ID is in the capability catalog |
| 429 | Requests are too close together. Wait, add backoff, and do not resend in a tight loop |
| Timeout, connection reset, or a spinner that never ends | The address is https://api.icodeeasy.cc. If it is still slow, switch to a backup domain below |
| Gemini path returns 404 | GOOGLE_GEMINI_BASE_URL is the domain only. Do not add /v1beta |
Backup domains. Keep the original path and key:
https://jp.icodeeasy.cc
https://sg.icodeeasy.cc
Fields to change: ANTHROPIC_BASE_URL for Claude Code, GLM, and MiniMax; base_url for Codex; base_url for Kimi Code CLI, keeping /v1; GOOGLE_GEMINI_BASE_URL for Gemini CLI.
Confirm the change
Send one short message from the same client. Open request logs and confirm the model, status, and charge belong to that request. If it still fails, send the status code and error text to Tickets. Do not include the full API key.
Full client setup is in Claude Code, Codex, Gemini CLI, and the FAQ.
Related guides
FAQ
Troubleshoot API keys, 401 and 429 responses, Windows environment variables, client connectivity, quotas, and support reporting.
Install Claude Code, Configure a Custom API, and Troubleshoot Windows
Install Claude Code, configure a custom API key and URL, verify Windows or Unix settings, and troubleshoot authentication, rate limits, and connections.
Codex Setup
Install Codex CLI, store the API key in auth.json, configure the I Code Easy provider and Base URL, and start a first Codex session.