Use a Proxy with uv

Set uv's proxy environment variables and use the current system-certs option when an approved proxy CA is already in the operating-system trust store.

For one uv command in a POSIX shell, set the proxy variables on that invocation:

HTTP_PROXY=http://203.0.113.10:8080 \
HTTPS_PROXY=http://203.0.113.10:8080 \
uv add requests

Replace the example endpoint with a service address or a candidate from the HTTP proxy list. The assignments apply to the command and its children rather than shell startup files; PowerShell uses different syntax. HTTPS destinations can use an http:// proxy listener. ALL_PROXY supplies a general proxy setting and NO_PROXY specifies bypasses.

If the route works but an approved organization CA is missing from uv's bundled Mozilla roots, use system trust when that CA is already installed there:

HTTPS_PROXY=http://203.0.113.10:8080 \
uv --system-certs add requests

The flag is --system-certs. Its corresponding UV_SYSTEM_CERTS=true variable was added in uv 0.11.0; check installed help for an older release. A separately provided PEM bundle instead uses the documented SSL_CERT_FILE or SSL_CERT_DIR trust interface. None of these trust settings chooses the proxy address.

Read the command output before calling this a successful route test. uv can reuse cached packages without downloading them. A real operation can also contact files, redirects, managed Python downloads or Git dependencies beyond the index. Keep the failed stage with its error. If the wrong route persists, inspect inherited proxy/bypass values; changing the package index chooses a source rather than a forward proxy.

Artihkkalat mat laktásit