CC Switch troubleshooting
Find the stage that failed: browser launch → import → activate → model request. Success at one stage does not confirm the next one.
Open CC Switch does nothing
- Confirm the app is installed and launch it manually once.
- Reopen the import window in the Guangji console. Check for the browser's external-application prompt.
- If you previously cancelled it, retry and allow the browser to open CC Switch using the
ccswitch://link. - If a portable installation or broken protocol association prevents launch, follow the official installation instructions to repair it. Use manual setup in the meantime.
Do not send a complete credential-bearing import link to others or paste it into a third-party link checker.
Import succeeded, but the old provider is still used
- Confirm the configuration belongs to the right application.
- Activate the Guangji API card and check its current status.
- Close the old session and reopen the terminal and tool. Verify its model.
- If CC Switch shows an environment-variable conflict, review the variable and its source. An old address or key can override the configuration.
Before changing environment variables, check whether another application needs them. Modify only confirmed conflicts, retain a backup and restart affected applications. Do not delete all environment variables.
A request returns an error
| Symptom | First checks |
|---|---|
401 / authentication failed | Correct complete Guangji key, enabled and unexpired; configuration reactivated after changes |
403 / access denied | Key group, model permissions, IP restrictions and account status |
404 / HTML response | Console URL entered by mistake, duplicate /v1, or unsupported endpoint protocol |
| Model not found / no channel | Exact model ID and availability in the key's group |
429 / quota error | Read the response; check balance, key quota and frequency |
| Local connection refused | Routing or aggregation requires the CC Switch service to be running |
| Timeout / connection reset | Check networking and proxy settings; distinguish the local service from the Guangji endpoint |
See general troubleshooting. Changing a model name or adding and removing /v1 at random will not reliably fix a protocol mismatch.
It stops working when CC Switch closes
Routing and aggregation depend on the local service. Keep it running, or use Return to direct, choose a protocol-compatible Guangji configuration, and reopen the target tool. Do not leave a local routing address configured after shutting down its service.
Speed test passes, but chat fails
A speed test mainly checks connectivity. Actual calls still need valid authentication, model permissions, quota and a matching protocol. Send a short request in the target tool and check the Guangji logs.
Restore the previous setup
Reactivate the previous provider for a temporary switch. To restore official account login, choose the appropriate official configuration and follow the tool's login flow.
For broader changes, restore a CC Switch backup after exporting the current configuration. See backup instructions.
Ask for help
Provide the CC Switch version, operating system, target app, connection mode, model ID, time and error screenshot. You can share a domain and path, but redact keys, login credentials and credential-bearing links.
- Guangji accounts, models, balance or endpoints: QQ support.
- CC Switch installation or app issues: official manual or GitHub Issues. Check logs and screenshots for secrets before posting publicly.