chrome://version does not show --proxy-server
Check Was every window and background process closed before the launch?
Fix Quit with chrome://quit and start again from the command line or the edited shortcut.
Chromium Proxy Command Line: --proxy-server Examples
The exact flags, one launch command per system, and the five reasons the flag seems to do nothing.
Launch Chromium with a proxy: steps
Step 1: quit every running window
The Chromium page tells you to close the browser first by opening chrome://quit. If an old process is still running, a new start may not take your flag.
Before continuing Skipping this is the most common reason the flag looks ignored.
Step 2: start it with the flag
On Windows add the flag to the end of the shortcut's Target line. On macOS run the program file in Terminal. On Linux start chromium-browser or google-chrome from a terminal. The commands are in the next block.
Step 3: confirm the flag was applied
Open chrome://version: it lists the full command line in use. For the proxy itself, chrome://net-internals/#proxy shows where the settings come from.
Expected result --proxy-server=... appears in the command line.
Step 4: check the exit IP
Open https://ipinfo.io/json in that window and compare the IP and country with your own.
Expected result The IP and country of the proxy, not yours.
Launch commands for Windows, macOS and Linux
# Windows: fully quit the browser first (chrome://quit), then put this at the end of the shortcut's Target
chrome.exe --proxy-server="http://HOST:PORT"
# macOS (Terminal; escape the spaces for Google Chrome)
/Applications/Chromium.app/Contents/MacOS/Chromium --proxy-server="http://HOST:PORT"
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --proxy-server="http://HOST:PORT"
# Linux
chromium-browser --proxy-server="http://HOST:PORT"
google-chrome --proxy-server="http://HOST:PORT"Example only: replace HOST and PORT with the values from My assets. Not launched on the writing machine; the syntax follows the Chromium documentation.
What the --proxy-server value means
| Item | What Chromium does | Good to know |
|---|---|---|
| http://HOST:PORT | Sends all requests to that proxy | Without a scheme, HOST:PORT is read as an HTTP proxy |
| http://HOST:PORT,direct:// | Tries the proxy, then connects directly if it is unreachable | Without the fallback, an unreachable proxy gives ERR_PROXY_CONNECTION_FAILED; with it you may leak your own IP |
| http=http://HOST:PORT;socks=socks5://H2:P2 | One proxy for http:// URLs, another for everything else | "socks=" means "other proxies"; a scheme-less address there is read as SOCKS4, not HTTP |
| socks5://HOST:PORT | Sends traffic through a SOCKS5 proxy | No login method works in Chrome; names are always resolved by the proxy |
| https://HOST:PORT | Talks to the proxy over TLS | Supports the same logins as HTTP, plus client certificates |
Source: Chromium documentation "Proxy support in Chrome", read on 14 November 2026.
Different proxy per scheme, fallback and skip rules
# one proxy for everything
--proxy-server="http://HOST:PORT"
# fall back to a direct connection if the proxy is unreachable (comma = ordered list)
--proxy-server="http://HOST:PORT,direct://"
# a different proxy per scheme (WinInet map format; "socks=" means "other proxies")
--proxy-server="http=http://HOST:PORT;socks=socks5://HOST2:PORT2"
# addresses that should skip the proxy are listed as rules like these
# (semicolon- or comma-separated; the flag that takes them is named in the Chromium page under Sources)
<local>;*.example.com;192.168.0.0/16Flag fragments, not a script: combine only the ones you need. The rule formats come from the Chromium documentation.
Skipping the proxy for some addresses
A second flag, named in the Chromium page linked under Sources, takes semicolon- or comma-separated rules. The documentation lists host names (foobar.com, *foobar.com), subdomains (.example.com matches sub.example.com but not example.com), IP literals, IPv4 ranges such as 192.168.1.1/16, and <local> for names without a dot. localhost and similar loopback addresses are skipped implicitly; <-loopback> removes that rule and is meant for test setups.
For mainland China domestic sites, skip rules like these, or a PAC file, are the right tool: it keeps domestic sites off the overseas exit, which is what the page is about. It does not help anyone reach blocked sites.
The login: what the flag cannot do
Chrome does not use a username and password written in the proxy settings, so http://LOGIN:PASSWORD@HOST:PORT in the flag does not sign in. An HTTP proxy then asks through the ordinary sign-in flow; Chrome supports Basic, Digest, Negotiate and NTLM for HTTP proxies. For SOCKS5 Chrome supports no login method at all.
If you need a logged-in proxy in a window nobody watches, point Chromium at a local forwarder that adds the login, or use Playwright or Puppeteer, which take the login in their own settings.
The flag seems to do nothing
The page opens but the IP is still yours
Check Is another source overriding it: a managed policy (chrome://policy) or an extension?
Fix Check chrome://net-internals/#proxy and chrome://policy; the Chromium notes list policy, command line, extensions and system settings as the sources.
ERR_PROXY_CONNECTION_FAILED
Check Are host, port and scheme right, and does the proxy answer outside the browser?
Fix Test with curl, press "Clear bad proxies" on chrome://net-internals/#proxy, then follow the connection-failed guide.
A sign-in box appears, or the proxy refuses
Check Is the proxy SOCKS5 with a login, or HTTP without the login being answered?
Fix Use the HTTP port and type the login once, or use a local forwarder.
Stop when If curl with the same login fails too, the problem is the account details, not the flag.
Which Proxy302 product to use with Chromium
For one profile that stays signed in to the same account, a static ISP IP does not rotate during the lease: US$0.50 for 1 day, US$7.99 for 30 days (about US$0.27 a day). Choose HTTP when you buy; the HTTP port is 2222 and the SOCKS5 port is 3333 on proxy.proxy302.com.
There is no free trial; the smallest purchase is one IP for one day.
FAQ
How do I set a proxy for Chromium from the command line?
Quit the browser, then start it with --proxy-server="http://HOST:PORT" and check chrome://version.
Can I put the username and password in --proxy-server?
You can write them, but Chrome does not use credentials embedded in proxy settings.
Does the flag work for SOCKS5?
Use socks5://HOST:PORT. Chrome supports no authentication for SOCKS5, so it only suits a SOCKS5 proxy without a login.
How do I skip the proxy for local addresses?
localhost is skipped implicitly. For other addresses add skip rules such as "<local>;*.example.com"; the flag name is in the Chromium page under Sources.
Is the flag the same in Google Chrome and Edge?
Chrome and Chromium share the proxy code described in the Chromium notes. For Edge see the Edge guide.
Read next
Chrome proxy setup
Set a proxy in Google Chrome: system settings, the --proxy-server flag, why SOCKS5 with a login does not work, extensions and a check.
Edge proxy setup
Set a proxy in Microsoft Edge: system settings, the --proxy-server flag, why SOCKS5 with a login does not work, managed computers, extensions and a check.
Linux proxy setup
Set a proxy on Linux: http_proxy, https_proxy and no_proxy variables, making them permanent, the GNOME Network proxy panel, and proxy settings for apt and dnf.
Fix ERR_PROXY_CONNECTION_FAILED
The ERR_PROXY_CONNECTION_FAILED error appears in Chrome and Edge when the browser cannot establish a connection with a proxy server.
ISP proxies (static residential)
Fixed static ISP proxies: a residential-grade IP that stays the same for the whole term. For social accounts, stores and AI tools. HTTP and SOCKS5.
View options and pricingReference links
4
- Chromium docs: Proxy support in Chrome (net/docs/proxy.md)
Official documentation · Confirmed on:
Read on 14 November 2026: --proxy-server syntax (single proxy, comma-separated fallback with direct://, per-scheme map such as http=...;socks=...); a bare host:port means an HTTP proxy; a bypass-list flag (--proxy-bypass-list) with semicolon- or comma-separated rules (hostname, .subdomain, IP literal, IPv4 range, <local>, <-loopback>); implicit bypass of localhost; credentials in proxy settings are not used; no authentication method for SOCKS5; SOCKS5 names are always resolved by the proxy; chrome://net-internals/#proxy and chrome://net-export for debugging.
- Chromium: Run Chromium with flags
Official documentation · Confirmed on:
Read on 14 November 2026: close Chrome first (chrome://quit), then add the switch to the Windows shortcut target, run the binary with the switch in Terminal on macOS, or start chromium-browser or google-chrome with the switch on Linux; chrome://version lists the command line in use.
- Proxy302 test notes
Local example · Confirmed on:
No browser binary was available on the writing machine, so the examples were not launched; the flag syntax and platform steps come from the two Chromium pages above.
The commands are examples; test them on your own system.
- Proxy302 product facts and price list
Product observation · Confirmed on:
Product facts file of the site (values checked on 10 November 2026): protocols and ports, prices in US$ (1 PTC = US$1), lease terms, quantity limits, no free trial.
Ready to try it?
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.