Skip to main content
Zeus Desktop allows you to assign a dedicated proxy server to each browser profile, enabling different IP addresses and geographic locations for each browsing session.

​
Overview

Proxy support is a key component for creating truly isolated browser environments. By assigning different proxies to different profiles, each profile appears to originate from a different location, IP address, and network — essential for multi-account management, regional testing, and privacy.

​
Supported Proxy Types

TypeProtocolUse Case
HTTPhttp://General web browsing, most common proxy type
HTTPShttps://Encrypted proxy tunnel for secure browsing
SOCKS5socks5://Low-level proxy supporting all protocols, best for advanced use

​
Configuration

​
Setting Up a Proxy

In the profile creation (or editing) dialog, navigate to the Proxy Settings tab:
  1. Enable Proxy — Toggle the switch to activate proxy settings
  2. Proxy Type — Select HTTP, HTTPS, or SOCKS5
  3. Host — Enter the proxy server hostname or IP (e.g., 192.168.1.100)
  4. Port — Enter the proxy server port (e.g., 1080)
  5. Username (optional) — For authenticated proxies
  6. Password (optional) — For authenticated proxies

​
Configuration Example

Type:     SOCKS5
Host:     proxy.example.com
Port:     1080
Username: user123
Password: ********

​
How It Works

​
Command-line Proxy

When a profile with proxy enabled is launched, Zeus passes the --proxy-server flag to Chrome: 
chrome --proxy-server=socks5://proxy.example.com:1080
This routes all browser traffic through the specified proxy server.

​
Proxy Authentication (CDP)

If the proxy requires username/password authentication, Zeus handles this automatically through Chrome DevTools Protocol: This is achieved using:
  • Fetch.enable({ handleAuthRequests: true }) — Enables auth interception
  • Fetch.authRequired event listener — Automatically responds with stored credentials
The user never sees a proxy authentication popup — it’s handled entirely in the background.

​
Proxy Testing

Before saving a proxy configuration, you can test the connection directly from the UI.

​
How Testing Works

  1. Click the “Test Proxy” button
  2. Zeus sends a test request through the configured proxy to httpbin.org/ip
  3. Results show:
    • Success/Failure status
    • Exit IP — The public IP address as seen by the target server
    • Latency — Round-trip time in milliseconds

​
What’s Being Tested

CheckDescription
ConnectivityCan we reach the proxy server?
AuthenticationAre the credentials (if any) accepted?
Exit IPWhat IP does the external world see?
LatencyHow fast is the proxy connection?

​
Best Practices

​
Proxy Selection

  • Residential proxies — Best for anti-detection; appear as regular home users
  • Datacenter proxies — Faster but easier to detect; good for testing
  • Mobile proxies — Highest trust level; best for sensitive accounts

​
Performance Tips

  • Choose proxy servers geographically close to your target websites for lower latency
  • Use SOCKS5 for best compatibility — it supports UDP and all protocols
  • Match the proxy’s geographic location with the profile’s timezone and language settings for consistency

​
Security Considerations

  • Proxy credentials are stored in the local profile configuration file
  • Always use trusted proxy providers — the proxy can see unencrypted HTTP traffic
  • For maximum security, combine proxy with HTTPS-only browsing

​
Troubleshooting

​
Proxy Connection Failed

  1. Verify the proxy host and port are correct
  2. Check if the proxy server is online and accepting connections
  3. Ensure your local firewall isn’t blocking outbound connections to the proxy port
  4. Try a different proxy type (HTTP vs SOCKS5)

​
Authentication Errors

  1. Double-check username and password
  2. Some proxies may whitelist IPs — ensure your current IP is allowed
  3. Check if the proxy provider has usage limits or has expired

​
Slow Browsing with Proxy

  1. Test proxy latency using the built-in test feature
  2. Try a proxy server closer to your geographic location
  3. Consider upgrading to a faster proxy plan
  4. Check if the proxy provider throttles bandwidth