authentication in proxy url

[bidzhao]

In General Settings, does Proxy URL support authentication like "http://user:pass@host:port"? Looks like CCR depends on undici for http/https proxy. Not sure if it requires extra logic for authentication? e.g. https://stackoverflow.com/questions/66459770/how-to-use-authenticated-proxies-with-undici

[MentalOfCrow]

Authenticated upstream proxies are supported now, but the current configuration deliberately stores the credentials separately rather than parsing them from the Proxy server field.

Support landed in commit 8d549296 and is present from v3.0.12 onward. In General Settings:

1. Select Use custom proxy.
2. Put only the proxy host in Proxy server (for example proxy.example.com).
3. Put 8080 in Port.
4. Fill the separate Username and Password fields.
5. Restart/reload the gateway if the running process has not picked up the saved configuration.

Do not rely on entering http://user:pass@host:port entirely in the server field. The current implementation's normalizeCustomProxyServer() extracts only parsed.hostname; authentication comes from upstream.custom.username and .password.

Internally CCR then builds the URL given to Undici's ProxyAgent as:

http://<percent-encoded-username>:<percent-encoded-password>@<host>:<port>

That detail matters when a username contains @ or a password contains :: enter the raw values in their dedicated fields and let CCR encode them. The repository has a unit test covering exactly those characters in proxy-upstream.test.mjs.

If you are on v3.0.11 or earlier, update first; the dedicated authenticated-upstream configuration is absent there. For a quick verification after updating, point it at a test proxy and confirm that a request no longer returns HTTP 407 Proxy Authentication Required.

If this solves it, please mark the comment as accepted so users on older versions know that the feature arrived in v3.0.12.

[bidzhao]

@MentalOfCrow , thank you for the response. I tried upgrading CCR to latest and setting up proxy with host 192.168.2.101, port 9999 and username, passowrd. But unfortunately the provider's check connectivity fails with error code 599, and Cluade Code's requests fail with "⏺ API Error: 502 All target providers failed. This is a server-side issue, usually temporary — try again in a moment. If it persists, check your inference
gateway (127.0.0.1:3456).". I have no idea what is wrong in my settings. BTW the same proxy settings work in CC-Switch, so I believe the proxy service is OK.

Best Regards,