Skip to content
CC Switch WikiUnofficial Community Wiki

I selected proxy forwarding to a remote host but it still forwards locally - CC Switch

Quick fix

Delete the .cc-switch config directory to clear the cache, and upgrade to v3.17.0 for the relay restriction and statistics fixes.

Symptom

Section titled “Symptom”
Error output
选择了代理转发到远程，但还是给本地进行转发
English translation

I selected proxy forwarding to a remote host but it still forwards locally

Cause

Section titled “Cause”

This cluster covers several independent CC Switch problems around proxies and relay services. The main one: when switching proxy config, the local routing state or cache is not refreshed correctly, so requests still go to the old address or locally (#5004, #5917). Older versions also have related defects: extra restrictions wrongly applied to some relay vendors causing response timeouts (#503); and in v3.16.5 and earlier, Codex sub-agent usage statistics generating the request_id from the parent thread session_id, so later records were deduplicated away as duplicates and stopped updating (#5287).

Fix

Section titled “Fix”

  1. Clear the local config and cache thoroughly. Close the app, delete the .cc-switch folder in your home directory (C:\Users\{user}\.cc-switch, for example), clean up leftover registry entries if needed, then configure the proxy again.

  2. Upgrade CC Switch to v3.17.0 or newer. The new version removed the extra restrictions on some relay vendors in single-proxy mode, and fixed the sub-agent request_id collision that stopped records updating.

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version3.16.3 - 3.16.5
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 5 real issues

FAQ

Section titled “FAQ”
Why does the relay service speed test fail without a VPN while a browser and terminal reach it fine?
The system network stack or DNS cache may be keeping the CC Switch test request from routing correctly. Try deleting the .cc-switch directory and restarting, or check whether your system proxy settings interfere with a direct local connection.
After configuring my own relay service, why does Codex still need the system proxy on to start?
That usually has nothing to do with CC Switch — the official Codex service, login, or client startup phase may have a hard-coded network dependency. If it keeps running after you turn the proxy off post-launch, your relay config is working.
Why does my relay keep receiving sub-agent requests while the call records in CC Switch stop updating?
A known bug in v3.16.5 and earlier. The old parsing logic generated a sub-agent request_id from the parent thread session_id, so several sub-agent requests under one parent thread were deduplicated away as duplicates. Upgrading to v3.17.0 fixes it.
Section titled “Related problems”
Error running remote compact task - CodexUpgrade cc-switch to v3.12.0 or newer, which added forwarding for the Codex `/responses/compact` route in the local proxy, fixing the 404 or 502.3 issues mergedClaude Official check failed: could not extract base_url - CodexCC Switch proxying and load balancing do not support an official Claude subscription — use a third-party API key. Forcing it errors and risks a ban.4 issues mergedThe apply_patch tool is unavailable with the Codex proxy onUpgrade to cc-switch v3.16.2 or newer. On a relay, make sure the backend model matches what Codex expects or tool calls fail with routing on.2 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.