Setting Up Proxy in VS Code and JetBrains IDE

Configuring Proxies in VS Code and JetBrains IDEs

Introduction

IDEs are a developer's primary tool. When working behind a corporate proxy, VS Code and JetBrains IDEs require special configuration to download extensions, updates, and work with Git repositories through the proxy.

Basic Configuration

VS Code

1. Open Settings (Ctrl+,)
2. Search for "proxy"
3. Set "Http: Proxy" to http://proxy_ip:port
4. Or edit settings.json and add http.proxy
5. For authentication: http://user:pass@proxy_ip:port
6. "Http: Proxy Strict SSL" — disable for corporate proxies with self-signed certificates

JetBrains IDEs (IntelliJ, PyCharm, WebStorm)

1. File → Settings → Appearance & Behavior → System Settings → HTTP Proxy
2. Select "Manual proxy configuration"
3. Enter Host name and Port number
4. For authentication — enter Login and Password
5. Click "Check connection" to verify
6. No proxy for: localhost, *.local

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 exclusions (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 Operation

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

Troubleshooting

Proxy Not Connecting

• 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 the credentials format is correct
• Try URL encoding special characters in the password

Best Practices

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

Conclusion

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