Proxy setup on a computer
How to set a system proxy in Windows 11 and macOS, check the IP and turn the proxy off.
How to set a proxy in Microsoft Edge, step by step: where Edge takes its proxy from, the start-up flag for one session, what to do about a username and password, what a managed computer changes, how to check the result and how to switch it off.
A proxy is another computer that sends your requests to the internet for you; websites then see the proxy's address instead of yours.
HOST and PORT are the address of that computer and the number of its door. USERNAME and PASSWORD prove that you may use it.
A start-up flag is a word such as --proxy-server that you add to the command that launches Edge. It works for that launch only.
Microsoft's page on Edge command-line proxy options says the Edge network stack uses the system network settings by default, including the proxy settings. In plain words: Edge reads the proxy that Windows or macOS holds, and the same setting also affects other programs that follow the system.
Microsoft's proxy-support page adds that an HTTPS proxy cannot be specified through system settings; for that you need a PAC file or an Edge setting such as the command line. It also says that with system settings you should use the platform's own rule format for the list of hosts that skip the proxy.
On Windows, Microsoft Support gives the path: open the Settings app, choose Network & internet, then Proxy. On a Mac, Apple Support gives: Apple menu, System Settings, Network in the sidebar, your network service, Details, then Proxies. The Microsoft pages I read do not describe a link inside Edge's own Settings that opens this window, so use the system path.
Windows: under Manual proxy setup, next to Use a proxy server choose Set up, turn on Use a proxy server and fill in the Proxy IP address and Port boxes. Mac: enter HOST and PORT under Web proxy (HTTP) and under Secure web proxy (HTTPS). Microsoft's proxy-support page says that in the Windows proxy settings every field except SOCKS, including "Secure", names an ordinary HTTP proxy server; it does not say this about the Mac fields, and Apple's page does not either, so enter the same HTTP address in both. The system proxy guide has the full steps.
Close Edge completely, open it again and go to https://ipinfo.io/json. If the IP is not yours, the proxy works.
Microsoft's Edge proxy notes say that most platforms allow a username and password in manual proxy settings, but Edge "doesn't implement this, and won't use any credentials embedded in the proxy settings". Authentication goes through the ordinary flow instead. The notes list Basic, Digest, Negotiate and NTLM for HTTP proxies. Microsoft's troubleshooting page for repeated proxy prompts says Edge prompts for credentials when the authentication exchange is not completed, so when the sign-in box appears, enter the USERNAME and PASSWORD from My assets. Do not rely on the password box that macOS offers in its own proxy settings: Edge does not use credentials embedded in the proxy settings.
For SOCKS5 the same notes say "No authentication methods are supported for SOCKSv5 in Edge". A SOCKS5 proxy without a login can work; a SOCKS5 proxy with a login cannot be used by Edge itself. Buy HTTP if you need a login.
Microsoft's command-line page lists three forms of the flag: a semicolon-separated list of scheme=address pairs, a single address used for all URLs, and "direct://", which makes all connections skip the proxy. The proxy-support page lists the schemes Edge knows: direct, http, https, socks4 and socks5. Write the scheme in front of the address so there is no doubt. Its example for an HTTP proxy is --proxy-server="http://foo:8080".
--no-proxy-server tells Edge not to use a proxy even if the system has one, and overrides other proxy settings. --proxy-auto-detect asks Edge to find the setting itself and is ignored if --proxy-server is also given. --proxy-pac-url points Edge to a PAC file, a small script that decides which address goes through which proxy.
One warning: Microsoft's Dev Proxy page says "Microsoft Edge doesn't support the --proxy-server command-line flag" and tells you to use the system proxy settings. Microsoft's own command-line page lists the flag, so the two pages disagree. If the flag has no effect on your copy of Edge, use Method 1.
msedge --proxy-server="http://HOST:PORT"
msedge --proxy-server="socks5://HOST:PORT"
msedge --no-proxy-serverReplace HOST and PORT with the values from My assets. "msedge" stands for the way you start Edge on your system; the flag goes after it. The second line is for SOCKS5 without a login.
If a work or school administrator sets the ProxySettings policy, Microsoft says Edge ignores all proxy options given on the command line. Open edge://policy to see which policies are active. The older ProxyMode and ProxyServer policies, and the policy for the list of hosts that skip the proxy, are marked deprecated and are applied only when ProxySettings is not set. On such a computer, ask the administrator before changing proxy settings.
Microsoft's proxy-support page says requests to localhost and link-local addresses are sent directly by default. A list of hosts that skip the proxy can be given with a separate flag, described on Microsoft's command-line page, which must be used together with --proxy-server; the list is separated by semicolons or commas, and a pattern such as *.contoso.com matches subdomains. On Windows the Settings window has an exception list for the same purpose, and a Mac has a field for hosts and domains that skip the proxy.
Microsoft's list of supported extension APIs includes proxy, which manages the proxy settings of Edge, on Windows, Linux and Mac, for both Manifest V2 and V3 extensions. An extension that uses it applies the proxy inside Edge without changing the computer's settings. The page I read does not describe how an extension handles a username and password, so follow the extension's own instructions.
The page shows the IP, country and network that websites see. Compare it with the same page opened without the proxy.
Run the curl command below. If it fails, the problem is the proxy details, not Edge.
If you used a flag, make sure Edge was started with it; if you used an extension, check that it is switched on. On a work computer, open edge://policy to see whether a policy is setting the proxy.
curl -x http://USERNAME:PASSWORD@HOST:PORT https://ipinfo.io/jsonReplace HOST, PORT, USERNAME and PASSWORD with the values from My assets.
• System proxy: open the same system window and turn the proxy off.
• Flag: close Edge and start it again without the flag, or with --no-proxy-server.
• Extension: switch the extension to direct mode or remove it from Edge's extensions page.
• Managed computer: only the administrator can change a proxy that a policy sets.
• A sign-in box keeps coming back, or the page says 407. The proxy did not accept the username or password. Copy them again from My assets. Microsoft's troubleshooting page lists, among the causes, a proxy that offers no authentication scheme Edge accepts, and a proxy that refuses the account.
• SOCKS5 with a login does not work. This is expected in Edge itself; use HTTP.
• The page does not open and Edge says ERR_PROXY_CONNECTION_FAILED. Microsoft's notes use this message for an unreachable proxy server; check HOST and PORT, and test with curl.
• The IP did not change. Edge was not restarted, the flag was not on the command that started it, or an extension or a policy is setting the proxy.
A static ISP proxy fits when you want one permanent address for your browser: the IP stays the same for the whole lease and you choose the protocol at purchase. Choose HTTP: Microsoft's Edge notes say no authentication methods are supported for SOCKS5 in Edge, and a Proxy302 IP has a username and password. The product itself is described on the static residential proxies page.
Open the static ISP page, choose the country, set Protocol to HTTP, choose the term and the quantity, then review the cost and generate.
Open My assets and copy HOST, PORT, USERNAME and PASSWORD. The Connect page shows a ready example with your own details. HTTP uses port 2222 on proxy.proxy302.com.
Put the values into the computer's proxy settings (Method 1) or into the --proxy-server flag (Method 2), then restart Edge completely.
Check the exit with the curl command above and read the country and org fields, as the proxy location guide explains.
A static ISP IP costs US$0.50 for one day and US$7.99 for 30 days, about US$0.27 per day, the same in every country. Availability by country changes daily and is shown on the order page. There is no free trial, and the smallest purchase is one IP for one day.
By default Edge uses the system network settings, so you set the proxy in Windows or macOS.
Not by itself: Microsoft's Edge notes say no authentication methods are supported for SOCKS5. Use an HTTP proxy.
Microsoft's command-line page lists it, but a Dev Proxy page from Microsoft says Edge does not support it. Try it; if it has no effect, use the system settings.
Undo the method you used: clear the system setting, start Edge without the flag or with --no-proxy-server, or switch the extension to direct.
An earlier help page for this browser is still available.
Official documentation · Confirmed on:
Read on 2 November 2026: schemes DIRECT, HTTP, HTTPS, SOCKSv4, SOCKSv5; HTTP proxies support Basic, Digest, Negotiate, NTLM; no authentication methods supported for SOCKSv5 in Edge; an HTTPS proxy cannot be specified through system settings; Edge does not implement credentials in manual proxy settings and will not use credentials embedded in them (authentication goes through the ordinary flow); --proxy-server example "http://foo:8080"; ERR_PROXY_CONNECTION_FAILED when the proxy is unreachable; the flag for the list of hosts that skip the proxy, <local> and *.domain patterns; localhost and link-local addresses are sent directly by default; with system proxy settings use the platform's rule format; Windows and macOS proxy fields are plain HTTP proxy identifiers except SOCKS.
It does not describe the sign-in box or any menu inside Edge. It says part of the page is based on Chromium.org material.
Official documentation · Confirmed on:
Read on 2 November 2026: the Edge network stack uses the system network settings by default, including proxy settings; --no-proxy-server (overrides any other proxy settings, even if the system has a proxy), --proxy-auto-detect (ignored if --proxy-server is configured), --proxy-server in three forms (scheme=address list, one address, direct://), the flag for a list of hosts that skip the proxy (must be used with --proxy-server), --proxy-pac-url.
It does not name the executable used to start Edge and does not discuss credentials.
Official documentation · Confirmed on:
Read on 2 November 2026: when ProxySettings is enabled Edge ignores all proxy-related options from the command line; it overrides the individual ProxyMode, ProxyPacUrl, ProxyServer and the list-of-hosts-that-skip-the-proxy policies. The pages for ProxyMode (https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies/proxymode), ProxyServer and the list-of-hosts policy mark them deprecated, applied only if ProxySettings is not specified.
It is an administrator reference.
Official documentation · Confirmed on:
Read on 2 November 2026: Edge prompts for credentials when the authentication exchange with the proxy does not complete; causes include a proxy that offers no scheme enabled by the AuthSchemes policy and a proxy that refuses the credentials or whose authorization rule denies the account; edge://policy shows the effective ProxySettings.
Aimed at administrators with single sign-on; it does not describe a plain username-and-password proxy step by step.
Official documentation · Confirmed on:
Read on 2 November 2026: the proxy API manages the proxy settings of Edge, on Windows, Linux and Mac, MV2 and MV3.
It does not describe credentials or modes.
Official documentation · Confirmed on:
Read on 2 November 2026: the page states that Microsoft Edge does not support the --proxy-server command-line flag and recommends the system proxy settings. This contradicts the command-line page above.
It is about a developer tool and gives no reason for the statement.
Official documentation · Confirmed on:
Read on 2 November 2026: Settings app, Network & internet, Proxy; under Manual proxy setup, Use a proxy server, Set up; the Proxy IP address and Port boxes; the exception list; the check box for local (intranet) addresses.
It has no username or password field.
Official documentation · Confirmed on:
Read on 2 November 2026: Apple menu, System Settings, Network, a network service, Details, Proxies; options Web proxy (HTTP), Secure web proxy (HTTPS), SOCKS proxy; "Proxy server requires password"; a field for hosts & domains that skip the proxy.
It describes the macOS settings, not Edge.
Product observation · Confirmed on:
Product facts file of the site (checked against the console, the backend and the price table on 18-19 October 2026): prices in US$ (1 PTC = US$1), lease terms, protocols and ports, no free trial.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.