Configure Cline to work behind firewalls and proxies
If you’re working behind a corporate proxy or firewall, you’ll need to configure
proxy settings for Cline to connect to AI providers. The configuration varies
depending on which version of Cline you’re using.
To avoid setting these variables every time, add them to your shell profile or system environment variables.macOS/Linux (add to ~/.bashrc, ~/.zshrc, or ~/.profile):
Search for “Environment Variables” in Windows Settings
Add the variables under “User variables” or “System variables”
Restart your terminal or IDE
Known Limitations
Cline CLI only supports HTTP proxies. It does not support SOCKS proxies,
proxy autoconfiguration (PAC) scripts, or HTTP proxies which require
authentication beyond a basic username and password.
JetBrains IDEs
The JetBrains plugin uses the IDE’s HTTP proxy settings.
Configure JetBrains Proxy
Open Settings/Preferences:
Windows/Linux: File > Settings
macOS: IntelliJ IDEA > Preferences
Or press Ctrl+Alt+S (Windows/Linux) or Cmd+, (macOS)
Navigate to:
Appearance & Behavior > System Settings > HTTP Proxy
Select “Manual proxy configuration”
Configure your proxy:
Host name: proxy.company.com
Port number: 8080
No proxy for: localhost,127.0.0.1
Check “Proxy authentication” if required
Enter your username and password
Click “Check connection” to verify the settings
Click “OK” to apply
Restart the IDE
Test Connection
After configuring the proxy, test that Cline can connect to your AI provider:
Open the Cline panel
Try sending a simple message
If connection fails, check the IDE’s Event Log for error messages
Custom Certificate Authority
If your proxy uses a custom CA:
Add the certificate to your system’s trust store, or
Import it into the JetBrains IDE:
Settings > Tools > Server Certificates
Click ”+” to add your certificate
Known Limitations
Cline in JetBrains only supports HTTP proxies. It does not support SOCKS
proxies, proxy autoconfiguration (PAC) scripts, or HTTP proxies which require
authentication beyond a basic username and password.Cline does not pick up changed proxy settings dynamically. After changing proxy
settings, restart the IDE for Cline to use the new settings.
Troubleshooting
Connection Timeouts
If you’re experiencing connection timeouts:
Verify your proxy address and port are correct
Check if the proxy requires authentication
Ensure the AI provider’s API endpoints aren’t blocked by your firewall
SSL/TLS Certificate Errors
If you see certificate-related errors:
Check that NODE_EXTRA_CA_CERTS points to the correct certificate file
Ensure the certificate file is in PEM format
Use curl to verify the certificate works, for example, curl -x proxy.corp.example:8080 --cacert /path/to/ca-cert.pem -o - -vv https://api.cline.bot/
Consider disabling http.proxyStrictSSL in VSCode (not recommended for production)
Testing Proxy Configuration
If you encounter problems with Cline networking, first verify your proxy
configuration works using curl:
# Linux/macOSexport https_proxy=http://proxy.company.com:8080curl -vv https://api.anthropic.com# Windows PowerShell$env:https_proxy="http://proxy.company.com:8080"curl.exe -vv https://api.anthropic.com
Use --cacert $NODE_EXTRA_CA_CERTS to specify a certificate if necessary.Next, check the logs for messages confirming your proxy configuration and any
network-related errors:
CLI: ~/.cline/data/logs/cline.log, or the file CLINE_LOG_PATH names.
cline doctor log opens it. If the hub is involved, also check
~/.cline/data/logs/hub-daemon.log.
JetBrains IDEs: ~/.cline/cline-core-service.log. Cline’s process for
every open project writes to this one file.