Skip to content
CC Switch WikiUnofficial Community Wiki

Request forwarding failed: error sending request for url - cc-switch

Quick fix

Check your local network connection and proxy configuration so cc-switch can reach the Nvidia API endpoint, resolving the 502 timeout.

Symptom

Section titled “Symptom”
Error output
{"error":{"message":"请求转发失败: error sending request for url      (https://integrate.api.nvidia.com/v1/chat/completions?beta=true)","type":"proxy_error"}}
English translation

{"error":{"message":"request forwarding failed: error sending request for url (https://integrate.api.nvidia.com/v1/chat/completions?beta=true)","type":"proxy_error"}}

Cause

Section titled “Cause”

This 502 means cc-switch timed out or failed to connect while forwarding the request to the Nvidia API. Per community feedback, that usually comes from the proxy not being enabled correctly, or from local network instability leaving the proxy unable to reach the external API. Some users report it appearing suddenly after a period of normal use — a typical connectivity problem.

Fix

Section titled “Fix”

  1. Check that your system or cc-switch has a proxy configured and enabled correctly.

  2. Check your local network connection and confirm the proxy node can reach https://integrate.api.nvidia.com.

Affected Versions

Section titled “Affected Versions”
ToolUnknown
VersionUnknown
PlatformsUnknown

Source Issues

Section titled “Source Issues”

This page is distilled from 2 real issues

FAQ

Section titled “FAQ”
It worked before and started erroring in the last couple of days. Why?
Usually a 502 timeout from local network instability or a dead proxy node. Check your network connection and proxy state.
I already enabled the proxy — why does it still error?
Still erroring with the proxy on means the proxy itself cannot reach the target server. Check the proxy node connectivity, or try another node.
Section titled “Related problems”
Nvidia check failed: Not found (404)Upgrade cc-switch to v3.16.3+; new version uses lightweight HTTP probing, fixing NVIDIA interface false 404 errors.2 issues mergedUpstream HTTP 404 cc-switchUpgrade cc-switch to remove ?beta=true from NVIDIA requests. Kimi does not support Codex's Responses API; use Claude Code or a local adapter.2 issues mergedThe proxy shows no requests at all - Claude CodeA known cc-switch bug: when an upstream such as Nvidia returns no usage data, the openai_chat path drops the log outright. No official fix yet.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.