Skip to main content
Cromite includes a built-in proxy configuration page for managing network proxy settings.

​
Accessing Proxy Settings

Cromite provides a dedicated configuration page at: 
chrome://proxy
1

Open Address Bar

Tap or click on the address bar in Cromite.
2

Enter URL

Type chrome://proxy and press Enter.
3

Configure Settings

Use the proxy configuration interface to set up your proxy.
The proxy configuration page provides a user-friendly interface for Chromium’s built-in proxy support.

​
Proxy Configuration Options

Cromite supports various proxy configuration methods:

​
Direct Connection

No proxy is used; all connections go directly to the destination. 
Mode: Direct
Description: No proxy server
Use case: Default configuration

​
Manual Proxy Configuration

Specify proxy servers manually for different protocols: 
Proxy Type: HTTP
Address: proxy.example.com
Port: 8080

​
Proxy Auto-Configuration (PAC)

Use a PAC script URL for automatic proxy configuration: 
PAC URL: http://proxy.example.com/proxy.pac
PAC scripts allow dynamic proxy selection based on URL, hostname, or other criteria.

​
System Proxy Settings

Use the operating system’s proxy configuration:
Cromite uses Windows Internet Options proxy settings.Access via: Control Panel → Internet Options → Connections → LAN settings

​
Command-Line Proxy Configuration

Alternatively, configure proxies via command-line switches: 
--proxy-server="http://proxy.example.com:8080"

​
Windows Configuration Example

In your chrlauncher.ini: 
[chrlauncher]
ChromiumCommandLine=--proxy-server="http://proxy.example.com:8080" --proxy-bypass-list="localhost;*.local" --user-data-dir="%LOCALAPPDATA%\Cromite\User Data"

​
Linux Configuration Example

./chrome --proxy-server="socks5://localhost:1080" --proxy-bypass-list="localhost;127.0.0.1"

​
Proxy Authentication

If your proxy requires authentication:
1

Configure Proxy

Set up the proxy server address and port via chrome://proxy or command line.
2

Trigger Authentication

When you first access a website, Cromite will prompt for credentials.
3

Enter Credentials

Provide your username and password in the authentication dialog.
4

Save Credentials (Optional)

Choose whether to save credentials for future sessions.
Saved proxy credentials are stored in your browser profile. Use with caution on shared devices.

​
Proxy Bypass Rules

Specify domains or IP addresses that should bypass the proxy:

​
Bypass Syntax

localhost              # Bypass localhost
127.0.0.1             # Bypass loopback address
*.local               # Bypass .local domains
internal.company.com  # Bypass specific domain
192.168.*             # Bypass IP range
<local>               # Bypass all local addresses

​
Common Bypass Patterns

localhost;127.0.0.1;*.local;*.test;*.localhost

*.internal;*.corp;10.*;192.168.*;172.16.*

mail.company.com;vpn.company.com;git.company.com

​
Testing Proxy Configuration

Verify your proxy setup:
1

Check IP Address

Visit a site like https://ifconfig.me or https://ipinfo.io to verify your public IP changes through the proxy.
2

Check DNS Resolution

Ensure DNS queries are handled correctly by the proxy.
3

Test Bypass Rules

Access a bypassed domain to confirm direct connections.
4

Verify Protocols

Test HTTP, HTTPS, and WebSocket connections.
Use chrome://net-internals/#proxy to view detailed proxy resolution information.

​
SOCKS Proxy Configuration

​
SOCKS4 vs SOCKS5

SOCKS4

  • Basic proxy protocol
  • No authentication
  • IPv4 only
  • No UDP support

SOCKS5

  • Advanced proxy protocol
  • Authentication support
  • IPv6 support
  • UDP support

​
SOCKS5 Example

--proxy-server="socks5://user:[email protected]:1080"
SOCKS5 is recommended for better security and functionality.

​
PAC Script Examples

Proxy Auto-Configuration scripts allow dynamic proxy selection: 
function FindProxyForURL(url, host) {
  // Direct connection for local addresses
  if (isPlainHostName(host) || isInNet(host, "192.168.0.0", "255.255.0.0")) {
    return "DIRECT";
  }
  
  // Use proxy for everything else
  return "PROXY proxy.example.com:8080";
}

​
Troubleshooting

​
Common Issues

Symptoms: Unable to load any websitesSolutions:
  1. Verify proxy server address and port
  2. Check proxy server is running and accessible
  3. Confirm network connectivity to proxy
  4. Check firewall settings
  5. Test with chrome://net-internals/#proxy
Symptoms: Repeated credential requestsSolutions:
  1. Verify username and password are correct
  2. Check proxy server authentication method
  3. Clear saved credentials and re-enter
  4. Check proxy server logs for auth errors
Symptoms: Partial connectivity through proxySolutions:
  1. Check proxy bypass list
  2. Verify DNS resolution through proxy
  3. Test with different proxy protocols
  4. Check for SSL/TLS certificate issues
Symptoms: PAC URL doesn’t applySolutions:
  1. Verify PAC URL is accessible
  2. Check PAC script syntax
  3. Test PAC script locally
  4. Ensure PAC server returns correct MIME type (application/x-ns-proxy-autoconfig)

​
Security Considerations

Proxies can see and modify all your unencrypted traffic.

​
Best Practices

  1. Use HTTPS: Always prefer HTTPS for end-to-end encryption
  2. Trust: Only use proxies you trust completely
  3. Authentication: Use authenticated proxies when available
  4. Credentials: Don’t save credentials on shared devices
  5. Bypass Lists: Keep bypass lists minimal and specific
  6. PAC Security: Ensure PAC scripts come from trusted sources

​
Corporate Proxies

Corporate proxies may inspect SSL/TLS traffic using certificates.
If your organization uses SSL inspection:
  1. You may need to install corporate root certificates
  2. Enable user certificates in Cromite (see Settings Guide)
  3. Be aware that your traffic can be monitored
Cromite disables user certificates by default to prevent man-in-the-middle attacks.

​
Advanced Configuration

​
Network Internals

Access detailed proxy information: 
chrome://net-internals/#proxy
View:
  • Current proxy configuration
  • Effective proxy settings
  • PAC script execution results
  • Proxy resolution logs

​
Environment Variables (Linux)

Set system-wide proxy via environment: 
export http_proxy="http://proxy.example.com:8080"
export https_proxy="http://proxy.example.com:8080"
export ftp_proxy="http://proxy.example.com:8080"
export no_proxy="localhost,127.0.0.1,.local"
Make permanent by adding to ~/.bashrc or ~/.profile.

​
Additional Resources

Chromium Proxy Documentation

Official Chromium proxy configuration documentation

PAC File Specification

PAC script format and function reference

Build docs developers (and LLMs) love

Get started for freeTalk to us