Windows 10/11 Proxy Setup

Windows 10 and 11 proxy setup is managed through the "Proxy" section within the "Network & Internet" settings, enabling either manual configuration of a proxy server address and port or automatic configuration via a PAC (Proxy Auto-Configuration) script.

Accessing Proxy Settings

To configure proxy settings on Windows 10 or 11:

1. Open the Settings application. This can be done by pressing Win + I or by clicking the Start button and selecting "Settings".
2. Navigate to Network & Internet.
3. In the left-hand menu, select Proxy.

Within the Proxy settings, two primary configuration methods are available: Automatic proxy setup and Manual proxy setup.

Automatic Proxy Setup

This method utilizes a Proxy Auto-Configuration (PAC) script, which is a JavaScript file that defines rules for how web browsers and other user agents automatically choose the appropriate proxy server for fetching a given URL.

Configure Automatic Proxy Setup

1. In the Proxy settings, locate the Automatic proxy setup section.
2. Toggle Automatically detect settings to Off unless you rely on Web Proxy Auto-Discovery Protocol (WPAD) in your network environment. For specific PAC file usage, this should typically be off.
3. Toggle Use setup script to On.
4. In the Script address field, enter the full URL to your PAC file (e.g., http://proxy.example.com/proxy.pac).
5. Click Save.

PAC File Considerations

• Dynamic Configuration: PAC files allow for dynamic proxy selection based on destination IP, hostname, or protocol, offering more granular control than manual setup.
• Centralized Management: Updates to proxy rules can be deployed by modifying a single PAC file on a web server, simplifying management across multiple clients.
• Availability: The PAC file server must be continuously accessible for the proxy configuration to function correctly. If the server is down, clients may lose internet access or fail to use the proxy.
• Debugging: PAC file issues can be complex to diagnose. Ensure the script is syntactically correct and the server hosting it is reachable.

Manual Proxy Setup

This method involves specifying a single proxy server address and port for all internet traffic.

Configure Manual Proxy Setup

1. In the Proxy settings, locate the Manual proxy setup section.
2. Toggle Use a proxy server to On.
3. In the Proxy IP address field, enter the IP address or hostname of your proxy server.
4. In the Port field, enter the port number your proxy server uses (e.g., 8080, 3128).
5. (Optional) Check Don't use the proxy server for local addresses (intranet). This bypasses the proxy for requests to local network resources, which is generally recommended to avoid unnecessary proxying of internal traffic.
6. (Optional) In the Bypass proxy server for these addresses text box, enter specific addresses or domains that should not use the proxy, separated by semicolons (e.g., *.local; 192.168.1.0/24; example.com).
7. Click Save.

Manual Setup Considerations

• Simplicity: Straightforward to configure for a single, consistent proxy server.
• Limited Flexibility: Less dynamic than PAC files. All traffic (unless bypassed) is routed through the specified proxy.
• Proxy Authentication: If the proxy server requires authentication, Windows will typically present a pop-up dialog requesting credentials upon the first connection attempt. These credentials are often cached for the session.

System-Wide vs. Application-Specific Proxy Settings

Windows proxy settings are generally system-wide, meaning they apply to most Universal Windows Platform (UWP) applications and many traditional Win32 applications that respect the system's proxy configuration. However, some applications may override or ignore these settings.

Applications That May Ignore System Proxy Settings

• Web Browsers:
  • Google Chrome, Microsoft Edge, Internet Explorer: These browsers typically respect the system proxy settings by default.
  • Mozilla Firefox: Firefox maintains its own independent proxy settings, configurable via Options > Network Settings > Settings.... It can be configured to use system proxy settings, or custom settings.
  • Opera, Vivaldi: Often based on Chromium, they usually follow system settings but may offer specific overrides.
• VPN Clients: VPN software typically establishes its own network interface and routing, bypassing or coexisting with system proxy settings.
• Download Managers: Some download managers have built-in proxy configuration options that can override system settings.
• Command-Line Tools: Tools like curl or wget often require explicit proxy configuration via command-line arguments or environment variables.

Setting Proxy for Command-Line Tools

For tools like curl or applications that rely on standard environment variables, you can set HTTP_PROXY and HTTPS_PROXY (and NO_PROXY for exclusions).

SET HTTP_PROXY=http://proxy.example.com:8080
SET HTTPS_PROXY=http://proxy.example.com:8080
SET NO_PROXY=localhost,127.0.0.1,.local

For persistent environment variables, use the System Properties dialog or PowerShell:

[System.Environment]::SetEnvironmentVariable('HTTP_PROXY', 'http://proxy.example.com:8080', 'User')
[System.Environment]::SetEnvironmentVariable('HTTPS_PROXY', 'http://proxy.example.com:8080', 'User')
[System.Environment]::SetEnvironmentVariable('NO_PROXY', 'localhost,127.0.0.1,.local', 'User')

Replace 'User' with 'Machine' for system-wide variables requiring administrator privileges.

Proxy Server Types and Windows Support

Windows system proxy settings primarily support HTTP and HTTPS proxies. SOCKS proxies (SOCKS4, SOCKS5) are generally not directly configurable through the native Windows proxy settings and typically require application-specific configuration or third-party client software.

Feature / Type	Manual Proxy Setup (Windows Settings)	Automatic Proxy Setup (PAC File)	Application-Specific Settings
HTTP Proxy	Supported	Supported (via PAC script logic)	Supported
HTTPS Proxy	Supported	Supported (via PAC script logic)	Supported
SOCKS4 Proxy	Not directly supported	Limited (PAC script can direct, but client might not support)	Often supported
SOCKS5 Proxy	Not directly supported	Limited (PAC script can direct, but client might not support)	Often supported
Authentication	OS prompt for basic auth	Handled by proxy server	Application specific
Dynamic Routing	No	Yes	Application specific
Centralized Mgmt	No	Yes	No

Troubleshooting Common Proxy Setup Issues

• Incorrect Proxy Address/Port: Double-check the IP address or hostname and port number. A common error.
• Proxy Server Unreachable: Ping the proxy server IP address to confirm network connectivity. Verify the proxy service is running on the server.
• Firewall Blocking: Ensure no local or network firewalls are blocking connections to the proxy server's IP and port.
• Authentication Failure: If the proxy requires authentication, ensure correct credentials are provided. If credentials are not prompted, verify the proxy configuration.
• PAC File Errors: Check the PAC file URL for typos. Verify the web server hosting the PAC file is accessible. Examine the PAC file for syntax errors using a JavaScript linter or browser developer tools.
• DNS Resolution Issues: If DNS resolution fails when using the proxy, the proxy server itself might have DNS issues, or it might not be configured to forward DNS requests correctly.
• Application-Specific Conflict: If internet access works for some applications but not others, investigate the proxy settings within the non-working application.
• Caching Issues: Sometimes, old proxy settings are cached. Restarting the browser or the system can resolve this. Clearing browser cache might also be necessary.
• SSL/TLS Certificate Issues: If HTTPS sites fail, the proxy might be intercepting SSL/TLS traffic. Ensure any required root certificates from the proxy provider are installed in the Windows certificate store.

Testing Proxy Connectivity

After configuring the proxy, verify its functionality:

1. Browser Test: Open a web browser and navigate to a website like whatismyip.com. The displayed IP address should be that of the proxy server, not your local machine.
2. curl Test (Command Prompt/PowerShell):
   cmd curl -x http://proxy.example.com:8080 https://api.ipify.org?format=json
   Replace http://proxy.example.com:8080 with your proxy details. This command should return the public IP address of the proxy.
3. Network Diagnostics: Use tracert to trace the route to an external IP address (e.g., tracert 8.8.8.8). This can help identify if traffic is being routed through the proxy's network.