Setting up Proxy for pip and conda

Configuring Proxies for pip and conda

Python package managers pip and conda download packages from PyPI and Anaconda Cloud. Proxy configuration is essential for working behind a corporate firewall or for obscuring the source of downloads.

Basic Configuration

pip

Via environment variables:

export HTTP_PROXY=http://user:pass@proxy_ip:port
export HTTPS_PROXY=http://user:pass@proxy_ip:port
pip install package_name

Via flag:

pip install --proxy http://user:pass@proxy_ip:port package_name

Via pip.conf configuration (Linux: ~/.config/pip/pip.conf):

[global]
proxy = http://user:pass@proxy_ip:port

conda

In the .condarc file:

proxy_servers:
  http: http://user:pass@proxy_ip:port
  https: http://user:pass@proxy_ip:port

To disable SSL verification (corporate proxies):

ssl_verify: false

Advanced Configuration

Environment Variables

Most tools support standard environment variables for proxies:
- HTTP_PROXY / http_proxy — proxy for HTTP requests
- HTTPS_PROXY / https_proxy — proxy for HTTPS requests
- NO_PROXY / no_proxy — list of exceptions (addresses that bypass the proxy)
- ALL_PROXY / all_proxy — proxy for all protocols

SSL and Self-Signed Certificates

Corporate proxies often use their own SSL certificates. To work through them, you need to:
1. Obtain the proxy's CA certificate from the administrator
2. Add it to the system certificate store
3. Or disable SSL verification (for testing only)

Authentication

Two main authentication methods are supported:

By username and password — standard HTTP Basic authentication. Credentials are sent with each request. URL format: http://user:pass@proxy_ip:port

By IP address (whitelist) — your IP is added to a whitelist. No credentials need to be sent.

Verifying the Configuration

After configuration, verify:
1. Perform a test request through the proxy
2. Ensure the IP address has changed
3. Check connection speed
4. Ensure there are no DNS leaks

Troubleshooting

Proxy connection fails

• Check the address and port for correctness
• Ensure the firewall is not blocking the connection
• Check proxy accessibility from your network

SSL errors

• For corporate proxies, add the CA certificate
• For testing, temporarily disable SSL verification
• Update SSL libraries to the latest version

Authentication errors

• Check username and password
• Ensure credentials are in the correct format
• Try URL encoding special characters in the password

Best Practices

1. Use environment variables — for flexibility and security
2. Avoid hardcoding credentials — use environment variables or configuration files
3. Configure exceptions — do not proxy localhost and internal addresses
4. Document settings — in the project's README or team wiki
5. Test after changes — any configuration change requires verification

Conclusion

Proper proxy configuration ensures stable tool operation and secure connections. Follow the recommendations in this guide and always verify functionality after setup.