Basic proxy setup
Configure a proxy server without authentication:Proxy with authentication
If your proxy requires authentication, include credentials:Configuration options
The proxy server URL. Must start with
http:// or https://.Example: http://proxy.example.com:8080Username for proxy authentication (optional)
Password for proxy authentication (optional)
Comma-separated domains to bypass the proxy (optional)Example:
"*.example.com,localhost,127.0.0.1"Using environment variables
SOCKS proxy
Nova Act supports SOCKS proxies:http://- HTTP proxyhttps://- HTTPS proxysocks5://- SOCKS5 proxysocks4://- SOCKS4 proxy
Bypassing the proxy
Exclude specific domains from using the proxy:- Specific hostnames:
localhost,127.0.0.1 - Wildcard patterns:
*.internal.company.com - IP ranges:
192.168.0.0/16 - Multiple values: Comma-separated list
Workflow example
Complete workflow with proxy configuration:Corporate proxy setup
For corporate environments with automatic proxy configuration:Testing proxy configuration
Verify your proxy is working correctly:Important notes
If connecting to a CDP (Chrome DevTools Protocol) endpoint, the code that launches the browser is responsible for configuring the proxy. The
proxy parameter only applies when NovaAct is creating and launching the browser.When proxy configuration applies
✅ Applies when:- NovaAct creates and manages the browser
- Using default browser launch
starting_pageparameter is provided
- Connecting to existing browser via CDP
- Using
cdp_endpointparameter - Browser is launched externally
Troubleshooting
Connection timeout errors
Connection timeout errors
Check that:
- Proxy server URL is correct
- Proxy server is accessible from your network
- Proxy port is open and accepting connections
- Credentials are correct (if required)
- Test with curl:
curl -x http://proxy:8080 https://example.com
Authentication failures
Authentication failures
Verify:
- Username and password are correct
- Credentials don’t contain special characters that need encoding
- Proxy supports the authentication method
- Account hasn’t been locked due to failed attempts
Some sites not working through proxy
Some sites not working through proxy
This may be due to:
- SSL/TLS interception by the proxy
- Proxy blocking certain domains
- Certificate validation issues
- Try adding affected domains to the bypass list
Performance is slow
Performance is slow
Consider:
- Proxy server location and latency
- Proxy server load
- Network bandwidth between you and proxy
- Using a faster proxy or direct connection for time-sensitive tasks
Best practices
Security
- Use environment variables: Store credentials securely
- Rotate credentials: Change proxy passwords regularly
- Audit access: Log proxy usage for security audits
- Encrypt in transit: Use HTTPS proxies when possible
Reliability
Performance
Next steps
Headless mode
Run browsers in headless mode
Security
Security best practices
NovaAct API
Complete API reference
Error handling
Handle connection errors