How to Set Up a Proxy in Google Chrome (Windows, Mac & Extension)

Google Chrome does not have its own built-in proxy settings — it uses the operating system's proxy configuration by default. This guide covers three ways to route Chrome through a proxy: via Windows system settings, via macOS system settings, and via a Chrome extension for more flexibility.

What You Will Need

Before you start, get your proxy credentials from LTEasy. After purchasing a plan, your dashboard will show:

• Proxy host/IP — e.g. proxy.lteasy.shop
• Port — e.g. 10500
• Username — your chosen auth username
• Password — your chosen auth password
• Protocol — SOCKS5 or HTTP (choose based on your plan)

Method 1: Windows System Proxy (Affects All Apps Including Chrome)

This method routes all internet traffic from your PC through the proxy, not just Chrome.

1. Press Windows + I to open Settings.
2. Go to Network & Internet → Proxy.
3. Under Manual proxy setup, toggle Use a proxy server to On.
4. Enter your proxy host in the Address field and your port in the Port field.
5. Click Save.

Note: Windows system proxy only supports HTTP/HTTPS proxies natively. For SOCKS5, use the Chrome extension method below.

When Chrome prompts for credentials (a login dialog will appear on the first proxied request), enter your LTEasy username and password.

Method 2: macOS System Proxy (Affects All Apps Including Chrome)

1. Open System Settings (or System Preferences on older macOS).
2. Go to Network, select your active connection (Wi-Fi or Ethernet), then click Details (or Advanced).
3. Click the Proxies tab.
4. For HTTP proxy: check Web Proxy (HTTP), enter your host and port.
5. For SOCKS5: check SOCKS Proxy, enter your host and port.
6. Enter your username and password if prompted.
7. Click OK and then Apply.

Method 3: Chrome Extension — Proxy SwitchyOmega (Recommended)

This is the most flexible method. It lets you switch proxies on the fly, create rules, and keep other apps off the proxy — all without changing system settings.

1. Open Chrome and go to the Chrome Web Store.
2. Search for Proxy SwitchyOmega and install it.
3. Click the SwitchyOmega icon in your toolbar, then click Options.
4. In the left sidebar, click New Profile, name it (e.g. "LTEasy"), and select Proxy Profile.
5. Set the protocol to SOCKS5 (or HTTP).
6. Enter your proxy Server (host) and Port.
7. Click Apply changes.
8. Back in the toolbar, click the SwitchyOmega icon and select your new profile to activate it.

When the proxy requires authentication, Chrome will show a credential dialog — enter your LTEasy username and password. SwitchyOmega will remember it for the session.

Method 4: Chrome Command-Line Flag (Advanced)

You can launch Chrome with a proxy flag directly from the terminal. This is useful for automation scripts:

# Windows (Command Prompt)
"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="socks5://proxy.lteasy.shop:10500"

# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --proxy-server="socks5://proxy.lteasy.shop:10500"

Replace the host and port with your actual LTEasy connection details. Note that credential prompts will still appear for authenticated proxies.

Verifying Your Proxy Is Working

After setting up your proxy, visit whatismyipaddress.com or ipinfo.io in Chrome. The IP shown should match your proxy's exit IP, and the location should match the country/region you selected in LTEasy.

You can also check your fraud score at IPQualityScore — a real LTE proxy from LTEasy will score 0–2.

Troubleshooting

• ERR_PROXY_CONNECTION_FAILED — double-check your host and port. Make sure the port matches your LTEasy dashboard exactly.
• Credential prompt keeps appearing — Chrome may not cache SOCKS5 credentials reliably via system settings. Use SwitchyOmega for SOCKS5 proxies with authentication.
• Proxy works but site is still blocked — the site may be doing browser fingerprint checks beyond IP. Consider pairing with an anti-detect browser.
• IP not changing after proxy switch — clear Chrome's DNS cache at chrome://net-internals/#dns and flush the socket pool at chrome://net-internals/#sockets.