Skip to content
CC Switch WikiUnofficial Community Wiki

Relay Link Speed Test Fails Without VPN - CC Switch

Quick fix

No single confirmed fix is available. Provide a reproducible configuration, request target, and startup logs.

Symptom

Section titled “Symptom”
Error output
开vpn之后就能测通，但是我另外一台电脑就没这个问题，不开梯子就能测通
English translation

After enabling VPN, the test succeeds, but another computer does not have this issue and can complete the test without a VPN.

Cause

Section titled “Cause”

Reports in this cluster do not share one confirmed root cause. #5917 reports relay link speed tests failing on Windows without VPN, while the link opens in a browser and can be pinged from a terminal. #5108 reports Codex requiring a system proxy at startup; the maintainer said the available information was insufficient to show that CC Switch caused it and requested a redacted configuration, request target, and startup logs. #5004 reports that forwarding still uses an old address after switching a remote proxy configuration, but has no clear reproduction or fix.

The timeout issue in #503 received a reply that it was fixed in a new version, without a specific version. #5287 is a separate Codex sub-agent usage-record issue: in v3.16.5, the sub-agent request_id uses the parent thread session_id, so records are discarded as duplicates. It was fixed in v3.17.0 and differs from link speed testing or proxy forwarding-address issues.

Fix

Section titled “Fix”

  1. For speed-test failures or Codex startup requiring a proxy, provide the maintainer with redacted configurations before and after enabling CC Switch, the request target, and startup logs to determine whether CC Switch configuration is involved.

  2. If call records for the Codex sub-agent `gpt-5.6-luna` stop updating, upgrade CC Switch from v3.16.5 to v3.17.0 or later, then retest.

  3. If using single-proxy mode and encountering response timeouts, check whether a version containing the fix is installed; control circuit-breaker settings based on the provider's first character and duration.

Affected Versions

Section titled “Affected Versions”
ToolUnknown
VersionUnknown
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 5 real issues

FAQ

Section titled “FAQ”
Why does forwarding still go to the old address after configuring a new environment address?
#5004 has no clear reproduction or fix conclusion; provide clearer configuration and forwarding-target details.
Why does the speed test fail without VPN when the link opens in a browser and can also be pinged from a terminal?
#5917 only confirms that it works after enabling VPN; it provides no verified cause or fix.
What should I do if Luna sub-agent records still stop updating after upgrading?
The maintainer requested retesting after upgrading to v3.17.0 or later; if the issue persists, reply on that issue for further investigation.
Section titled “Related problems”
Select Model Menu Still Shows Pre-Switch Model List - CodexClose existing Codex sessions, run `codex app-server daemon restart`, and upgrade CC Switch to v4.0.7 or later for detection and restart prompts.3 issues mergedProvider API Key Overwritten: After Codex Restart or SwitchUpgrade to cc-switch v4.0.0 or later to prevent provider keys from overwriting each other and restore the official login state.6 issues mergedError running remote compact task error - CodexUpgrade cc-switch to v3.12.0 or later. It adds forwarding support for the Codex `/responses/compact` route in the local proxy and can resolve 404 or 502 errors.3 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.