Three Levels of Proxy Configuration: System, Browser, App — Step-by-Step Guide
Table of contents
- Introduction: why you need to understand the three levels of proxy configuration
- Preliminary preparation: what you'll need before configuring
- Basic concepts: three levels and their priorities
- Step 1: test your proxy before any configuration
- Step 2: configure the proxy at the system level
- Step 3: configure the proxy at the browser level
- Step 4: configure the proxy at the application level
- Step 5: test priorities in practice
- Step 6: regain control and set up a rollback
- Verifying the result: a checklist for successful configuration
- Common mistakes and their solutions
- Additional capabilities and advanced settings
- Faq: common questions about configuring proxies at three levels
- Conclusion
Introduction: Why You Need to Understand the Three Levels of Proxy Configuration
Picture this. You've entered a proxy in your Windows settings, opened your browser, visited an IP-check website, and saw your regular address. Or the opposite: you turned off the system proxy long ago, but your messenger keeps routing through an old server and throws a connection error. Sound familiar? The cause is almost always the same: proxy settings on a computer aren't configured in one place but at three different levels, and each level follows its own rules.
In this guide, we'll break everything down. You'll learn what system, browser, and application-level proxy settings are, which one takes precedence, and why an app can completely ignore what you've entered in your operating system settings. We're deliberately not diving into auto-configuration via PAC files and the WPAD protocol: that's a big topic on its own, and here we're focused on manual settings and their priorities.
What you'll get out of this. After completing all the steps, you'll have a working proxy at the level you need. You'll be able to consciously choose: route your entire computer through a proxy, just one browser, or one specific program. And most importantly, you'll learn to quickly diagnose why traffic went somewhere you didn't expect.
Who this guide is for. For those who have already purchased or received access to a proxy server and want to connect it correctly. For marketers, social media specialists, testers, and developers who work with multiple accounts or check how a service looks from another region. For small business sysadmins who need to figure out why an employee's corporate proxy isn't working. The difficulty level is intermediate: the basic steps are beginner-friendly, and the sections on environment variables and priorities will be useful for advanced users.
What you need to know beforehand. It's enough to know how to open your operating system settings, install programs, and copy text. If you've ever changed Wi-Fi settings or installed a browser, you'll manage fine.
How much time it'll take. Full completion takes 40 to 60 minutes. If you only need one level, say the browser level, you'll be done in 15 minutes. I still recommend reading the priorities section in full — it'll save you hours of troubleshooting down the road.
Preliminary Preparation: What You'll Need Before Configuring
Before changing anything, let's gather everything you need. Good preparation takes five minutes and eliminates half of the typical mistakes.
Your Proxy Server Details
Every proxy has four key parameters. Find them in your proxy provider's dashboard or in the access email, and write them down in a text file:
- Server address (host). This is either an IP address like 185.10.20.30 or a domain name like proxy.example.net.
- Port. A number from 1 to 65535, such as 8080, 3128, or 1080. Often a single server has separate ports for HTTP and SOCKS5.
- Protocol type. HTTP, HTTPS, or SOCKS5. This determines which field you'll enter the data into.
- Username and password, if the proxy requires authentication. Some providers bind your IP address instead of using a password, in which case you don't need a username and password.
Tip: Immediately check that the port is specified for the protocol you're planning to use. The most common beginner mistake: entering a SOCKS5 port in the HTTP proxy field. The connection simply won't establish, and the error message will be vague.
Tools and Programs
- A computer with Windows 10 or 11, macOS 13 or newer, or Linux with a graphical shell. For the mobile part, you'll need a phone running Android 12+ or iOS 16+.
- Two browsers: one on the Chromium engine (Chrome, Edge, Yandex Browser) and Firefox. They handle proxies differently, and we'll use that difference to illustrate our points.
- Any website for checking your IP address. There are plenty of such services — search for "what's my IP" and pick one that also shows your country and ISP.
- A terminal or command prompt. On Windows, that's PowerShell; on macOS and Linux, the Terminal app.
- Optional: a messenger that supports proxies in its settings, like Telegram Desktop, to practice the application level.
Backing Up Your Current Settings
Proxy changes are reversible, but it's still worth capturing the original state. Especially if you're working on a corporate computer where the network has already been configured by an administrator.
- Open your current system proxy settings (we'll cover how in Step 2) and write down or photograph with your phone all the values, including the state of the toggles.
- If you've already configured a proxy in Firefox, open its connection settings and note the values there too.
- On Windows, additionally run the command
netsh winhttp show proxyin PowerShell and save the output. These are settings for system services — many people forget about them. - Save the file with your notes somewhere you'll find it a month from now.
Warning: If you're using a work laptop, check with your administrator whether you're allowed to change network settings. In some companies, proxy settings are managed by group policies, and your changes will either be automatically reverted or will block access to internal resources.
Basic Concepts: Three Levels and Their Priorities
Now for the most important part of understanding this whole topic. Let's figure out what proxy configuration levels are and how they interact. Without this section, all the following steps would just be mechanical button-pressing.
What a Proxy Is in Plain Terms
A proxy server is an intermediary between your program and a website. The program sends a request not directly to the site but to the proxy, which then contacts the site itself and returns the response to you. As a result, the site sees the proxy's IP address, not yours. This is used for working with multiple accounts, testing regional versions of services, scraping publicly available data with load distribution, and in corporate networks for monitoring and caching traffic.
There are several types of proxies. An HTTP proxy only understands web traffic. An HTTPS proxy can pass encrypted connections through a tunneling mechanism. SOCKS5 is a universal protocol that transmits any traffic, including email, games, and messengers. That's why in many program settings you'll see separate fields for each type.
Level 1: System Proxy
These are the operating system settings. On Windows, they're stored in Internet Options; on macOS, in each network connection's properties; on Linux, in environment variables and desktop settings. The idea is simple: the system announces to all programs, "here's the proxy address, route through it." But the key word here is announces. The system doesn't force programs to use the proxy — it merely provides them with the information. The program itself decides whether to read that information or not.
Level 2: Browser Proxy
A browser is also an application, but a special one: most user traffic goes through it, so it gets its own level. There's a fundamental division here. Chromium-based browsers (Chrome, Edge, Opera, Yandex Browser) by default don't have their own proxy settings and rely entirely on the system. The "Open your computer's proxy settings" button in Chrome just takes you to Windows or macOS settings. Firefox, on the other hand, has a completely independent mechanism and can use one proxy while the system uses another or none at all. Additionally, you can install a proxy management extension in any browser that intercepts settings at the browser level and overrides the system.
Level 3: Application Proxy
Many programs have their own connection settings section: messengers, torrent clients, development environments, package managers, command-line utilities. If a proxy is explicitly configured in the app, it will use that one regardless of the system and browser. If the app explicitly selects "no proxy," it will connect directly, even if the system is configured for a proxy. And only if the app has "use system settings" selected or no settings at all will it possibly refer to Level 1.
The Priority Rule: Who Overrides Whom
Remember the main principle: the closer a setting is to the application itself, the higher its priority. It looks like this:
- A setting inside the app overrides everything else.
- A browser extension overrides the browser's built-in settings and the system.
- The browser's built-in settings (in Firefox) override the system.
- System settings only work for programs that have agreed to read them.
Why can an app ignore the system proxy? There are several reasons. First, the program may use its own network library that simply can't read system parameters. Many utilities written in Go, Python, or Java behave this way: they expect environment variables or explicit flags. Second, Windows has two independent sets of system settings: WinINET for user programs and WinHTTP for services, and they don't sync automatically. Third, some apps deliberately ignore proxies for speed or security, like game clients or update programs. Finally, apps running under a different user or in a container see a completely different environment and different settings.
There's a flip side too. The system proxy in Windows and macOS is by default considered a setting for HTTP and HTTPS. If an app uses a different protocol — say, a direct TCP connection to a server — it physically can't route it through an HTTP proxy even if it wants to. It needs SOCKS5 and explicit support in the code.
The Difference from Auto-Configuration
You may have heard of PAC files and WPAD. These are methods where the browser downloads a script with rules and decides which request goes where. In this guide, we deliberately leave them out. Here we're talking about manually specifying a specific proxy and about which manual setting wins when there are several. Understanding priorities will also help you with auto-configuration, since a PAC script is subject to the same rule: an app with an explicitly configured proxy will ignore it too.
Step 1: Test Your Proxy Before Any Configuration
Goal of this stage: Make sure the proxy server is alive and the access credentials are correct. Otherwise, you'll be looking for a problem in system settings when the real culprit is a dead server.
Testing via Command Line
- Open the terminal. On Windows, press Win and X, then choose "Terminal" or "Windows PowerShell." On macOS, press Command and Space, type "Terminal," and press Enter. On Linux, Ctrl, Alt, and T usually works.
- First, find out your current IP without a proxy. Type the command
curl https://api.ipify.organd press Enter. The curl utility is pre-installed on Windows 10 version 1803 and later, on macOS, and on most Linux distributions. You'll see a line with your current address, like 91.200.10.5. Write it down — that's your baseline. - Now test the HTTP proxy. Type the command with your data substituted in:
curl -x http://username:password@address:port https://api.ipify.org. For example:curl -x http://user123:Pa55word@185.10.20.30:8080 https://api.ipify.org. - If the proxy doesn't require authentication, remove the part with the username, password, and @ symbol:
curl -x http://185.10.20.30:8080 https://api.ipify.org. - For SOCKS5, replace http with socks5h:
curl -x socks5h://user123:Pa55word@185.10.20.30:1080 https://api.ipify.org. The trailing h means the proxy itself will resolve domain names, not your computer. This is important for correct operation. - Press Enter and wait for a response. It usually takes one to three seconds.
Tip: If your password contains special characters like @, :, or #, the command will break. Replace them with percent-encoding: @ becomes %40, : becomes %3A, # becomes %23. Or ask your provider for a password made of letters and numbers.
Verification: In response to the command with the -x flag, you should see an IP address different from your baseline. That's the proxy server's address. If the address matches the baseline, the proxy wasn't applied. If you get an error like "407 Proxy Authentication Required," the username or password is wrong. If you get "Connection refused" or "Failed to connect," the address, port, or server is incorrect or unavailable.
Possible Issues at This Step
- The curl command isn't found. Older Windows builds don't have it. Install the utility via the winget package manager with the command
winget install curl.curl, or skip the test and move on to Step 2, testing through the browser instead. - The response takes very long, then times out. The port is closed or blocked by a firewall. Check whether you're confusing the HTTP and SOCKS5 ports, and try from a different connection, like mobile internet.
- The proxy responds but the IP doesn't change. Your proxy provider may have IP binding enabled, and your address isn't on the whitelist. Log into your dashboard and add your baseline IP.
Step 2: Configure the Proxy at the System Level
Goal of this stage: Set the proxy in your operating system so that all programs capable of reading system settings pick it up. This is the broadest level: one action affects most browsers, app stores, and many utilities.
Windows 11 and Windows 10
- Press the Win key or click the Start button and open "Settings" (the gear icon). Faster: press Win and I simultaneously.
- In the left menu, choose "Network & Internet."
- Scroll down and click "Proxy." A page opens with two sections: "Automatic proxy setup" and "Manual proxy setup."
- In the automatic setup section, make sure the "Automatically detect settings" toggle is off and "Use setup script" is also off. This disables auto-configuration so it doesn't interfere with manual settings.
- In the manual setup section, find the "Use a proxy server" line and click the "Set up" button to its right. The "Edit proxy server" window opens.
- Turn the "Use a proxy server" toggle to "On."
- In the "Proxy IP address" field, enter the server address, like 185.10.20.30. Enter only the address, without http:// and without the port.
- In the "Port" field, enter the port number, like 8080.
- The large text field below lists addresses for which the proxy is not used. By default, it may already contain local addresses. Add the sites that should open directly, separated by semicolons — for example, your proxy provider's dashboard URL.
- Check the "Don't use the proxy server for local addresses" box. Without it, printers, your router, and other devices on your home network may stop working.
- Click "Save." The window closes, and changes apply immediately — no reboot required.
Warning: The standard Windows window has no fields for username and password. If your proxy requires authentication, the browser will show a pop-up asking for credentials on the first attempt to reach a site. Enter them and check "Remember." Some programs that lack an interface for such a prompt will simply get a 407 error. For those, you'll need app-level configuration from Step 4.
There's an important nuance we mentioned in the concepts section. What you just configured are called WinINET settings, and they're read by user programs. System services, including Windows Update and some background tasks, use a separate set called WinHTTP. To sync them, open PowerShell as administrator (right-click Start, then "Terminal (Admin)") and run the command netsh winhttp import proxy source=ie. In response, the system will display the current proxy server and the exception list.
macOS
- Click the Apple logo in the top-left corner of the screen and choose "System Settings."
- In the sidebar, choose "Network."
- Click the active connection — usually "Wi-Fi" with a green dot. Then click the "Details" button next to your network name.
- In the window that opens, select the "Proxies" tab in the left list.
- You'll see a list of protocols with toggles: "Web proxy (HTTP)," "Secure web proxy (HTTPS)," "SOCKS proxy," and others.
- Turn on the "Web proxy (HTTP)" toggle. Fields for "Server" and "Port" appear on the right. Enter the address and port.
- If the proxy requires authentication, check the "Proxy server requires password" box and fill in the "Username" and "Password" fields. This is one of macOS's convenient differences from Windows: credentials can be saved right here.
- Repeat the same steps for "Secure web proxy (HTTPS)." Without this, encrypted sites — and that's almost all sites in 2026 — will go directly.
- If you have SOCKS5, instead of the previous two points, turn on "SOCKS proxy" and enter its details.
- In the "Bypass proxy settings for these hosts and domains" field, add exceptions separated by commas if needed.
- Click "OK," then make sure the changes took effect: the connection indicator should stay green.
Tip: On macOS, proxy settings are tied to a specific network interface. If you switch from Wi-Fi to Ethernet or another network, you'll need to re-enable the proxy. For convenience, create a separate network configuration via the "Locations" menu: that way you can switch between a profile with a proxy and one without in two clicks.
Linux, Using Ubuntu with GNOME as an Example
- Open "Settings" via the app menu or by clicking the indicators in the top-right corner and choosing the gear icon.
- In the left menu, choose "Network."
- Find "Network Proxy" and click the gear icon next to it.
- In the window that opens, choose "Manual" mode.
- Fill in the "HTTP proxy," "HTTPS proxy," and, if needed, "Socks host" fields. Each has a separate port field.
- In "Ignore hosts," leave localhost and 127.0.0.0/8, and add your own if needed.
- Close the window — settings apply immediately.
These settings are read by Firefox in "Use system proxy settings" mode, by Chromium browsers, and by some GNOME apps. However, command-line utilities like curl, wget, apt, and git won't see them. For those, Linux uses environment variables, which we'll cover in Step 4. This is a classic example of how even a correctly configured system level doesn't cover everything.
Android
- Open "Settings," then "Network & Internet" or "Connections," depending on the manufacturer.
- Choose "Wi-Fi" and find the network you're connected to. Tap the gear icon next to it, or long-press the network name and choose "Modify network."
- Expand "Advanced options."
- In the "Proxy" section, choose "Manual."
- Enter the "Proxy hostname" and "Proxy port." You can leave "Bypass proxy for" empty.
- Tap "Save."
Warning: The system proxy on Android only works for Wi-Fi and only for apps that use standard network libraries. For mobile data, there are no proxy settings in the interface at all. Many apps, including most messengers and games, ignore this parameter entirely. If you need a specific app to work through a proxy, look for the setting inside the app itself.
iOS and iPadOS
- Open "Settings," then "Wi-Fi."
- Tap the "i" icon next to the active network.
- Scroll down to the "HTTP Proxy" section and tap "Configure Proxy."
- Choose "Manual," enter the "Server" and "Port."
- If authentication is needed, turn on the "Authentication" toggle and enter the username and password.
- Tap "Save" in the top-right corner.
Verification: After configuring on any of the systems, open Chrome, Edge, or Safari, visit an IP-check site, and confirm it shows the proxy address, not your baseline from Step 1. Then close the browser, reopen it, and check again: the setting should persist. If Windows pops up a prompt for username and password, enter the data and check the remember box.
Possible Issues at This Step
- The proxy toggle is grayed out and won't move. Settings are locked by an organizational policy. Contact your administrator or configure the proxy at the browser and application levels instead.
- No sites open at all. Most likely, there's an error in the address or port. Go back to settings and double-check every character. For a quick rollback, just turn the proxy toggle off.
- On Windows, the password prompt keeps appearing. Credentials aren't being saved due to Credential Manager settings. Open Control Panel, go to "Credential Manager," click the "Windows Credentials" tab, and manually add an entry for the proxy address.
Step 3: Configure the Proxy at the Browser Level
Goal of this stage: Learn to route only the browser through a proxy while leaving the rest of the system on a direct connection, and clearly see how browser settings override system ones.
Firefox: Independent Settings
Firefox is the only popular browser with a full-fledged, built-in proxy configuration mechanism. It's the perfect tool for understanding priorities.
- Open Firefox and click the menu button (three horizontal lines in the top-right corner). Choose "Settings."
- Stay on the "General" tab and scroll to the very bottom, to the "Network Settings" section. Click the "Settings" button.
- The "Connection Settings" window opens with several options: "No proxy," "Auto-detect proxy settings for this network," "Use system proxy settings," "Manual proxy configuration," and "Automatic proxy configuration URL."
- Note that the default is "Use system proxy settings." In this mode, Firefox reads what you configured in Step 2. As soon as you pick something else, the link to the system level is broken.
- Select "Manual proxy configuration."
- In the "HTTP Proxy" field, enter the address; in the "Port" field to the right, the port.
- Check the "Also use this proxy for HTTPS" box. The HTTPS Proxy field will fill in automatically.
- If you have SOCKS5, leave the HTTP fields empty, enter the address and port in the "SOCKS Host" field, and select the "SOCKS v5" radio button below.
- Check the "Proxy DNS when using SOCKS v5" box. This is important: without it, site names will be resolved through your ISP, and some data about your activity will leak past the proxy.
- In the "No proxy for" field, list exceptions separated by commas if needed.
- Click "OK."
- Open a new tab and visit any site. If the proxy requires authentication, Firefox will show a prompt for username and password. Enter them and check "Use Password Manager to remember this."
Tip: Firefox lets you have multiple profiles with different proxy settings. Type about:profiles in the address bar, create a new profile, and configure a different proxy in it. That way you get two independent browsers on one computer without installing extra software.
Chrome, Edge, and Other Chromium Browsers
Here it's different. Open Chrome settings, type "proxy" in the settings search, and you'll see a single item: "Open your computer's proxy settings." Clicking it just opens the Windows or macOS window from Step 2. There are no native settings.
Still, you can route only Chrome through a separate proxy in two ways.
Method 1: Launch Parameter
- Close all Chrome windows completely. Check the notification area to make sure the browser isn't running in the background.
- Find the Chrome shortcut on your desktop or in the Start menu. Right-click it and choose "Properties." If the shortcut is in the Start menu, first choose "More," then "Open file location," and open properties there.
- On the "Shortcut" tab, find the "Target" field. It contains the path to the executable in quotes.
- Place the cursor at the very end of the line, after the closing quote, add a space, and append:
--proxy-server="http://185.10.20.30:8080". For SOCKS5:--proxy-server="socks5://185.10.20.30:1080". - Click "OK." If the system asks for administrator permission, confirm.
- Launch Chrome using this specific shortcut.
You can't specify a username and password in the launch parameter — the browser will prompt for them on the first connection. Note: the launch parameter overrides system settings. Even if Windows has a different proxy configured or the proxy is off, this Chrome instance will route through the server you specified. This also works on macOS if you launch the browser from the terminal: open -a "Google Chrome" --args --proxy-server="http://185.10.20.30:8080".
Method 2: Proxy Management Extension
- Open your browser's extension store and search for a proxy management extension. Choose ones with many installs and recent updates.
- Install the extension and click its icon in the toolbar.
- Create a new proxy profile: specify the type (HTTP or SOCKS5), address, port, username, and password.
- Save the profile and activate it by selecting it from the list.
- The extension's icon usually changes color to indicate that the proxy is active.
The extension uses a special browser API that has higher priority than system settings. While the extension is active, Chrome will ignore Windows settings. If you choose "System proxy" or "Direct connection" mode in the extension, priority returns to the system or is disabled entirely.
Warning: Extensions get access to all browser traffic. Only install trusted ones — open-source or from well-known developers. Don't enter proxy passwords into a suspicious extension if you use them elsewhere.
Verification: Turn off the system proxy from Step 2. Open Firefox with manual settings and Chrome without launch parameters. Visit an IP-check site in both. Firefox should show the proxy address, while Chrome should show your baseline. Now turn the system proxy back on: Chrome will show the system proxy, and Firefox will keep using its own. You just saw with your own eyes how the browser level overrides the system.
Possible Issues at This Step
- In Firefox, sites open but the IP doesn't change. Check that you selected "Manual proxy configuration" and not "Use system proxy settings." Also make sure the "Also use this proxy for HTTPS" box is checked.
- Chrome ignores the launch parameter. The browser was running in the background before you clicked the shortcut, and the new instance joined the existing process. Fully terminate Chrome via Task Manager and launch again.
- The extension shows the proxy is active, but sites don't open. Check the protocol type in the extension settings. The "ERR_TUNNEL_CONNECTION_FAILED" error often means you specified HTTP instead of SOCKS5 or vice versa.
Step 4: Configure the Proxy at the Application Level
Goal of this stage: Connect a specific program to the proxy and figure out why some apps don't see system settings, as well as how to make them work through a proxy.
Example 1: A Messenger with a GUI Setting
Let's take Telegram Desktop as a typical example of an app with its own proxy section. You'll find a similar interface in many other programs.
- Open Telegram Desktop and click the menu button (three lines) in the top-left corner. Choose "Settings."
- Go to "Advanced Settings."
- Find "Connection Type." By default it says "Default." Click it.
- A window opens with three options: "No proxy," "Use system proxy settings," and "Use custom proxy." These match exactly the three priority levels we discussed.
- Choose "Use custom proxy" and click "Add proxy."
- Select SOCKS5 (messengers almost always use it). Enter the address, port, username, and password.
- Click "Save." Your proxy appears in the list with a latency indicator in milliseconds. Green means the connection is established.
Now run an experiment. Turn off the system proxy in your operating system settings. The messenger will keep working through its proxy, because the app's setting has the highest priority. Then switch the messenger to "No proxy" and turn the system proxy on: the program will connect directly, completely ignoring the system. Only the "Use system proxy settings" option ties it to Level 1.
Example 2: Command-Line Utilities and Environment Variables
Here begins the zone where the question "why does my app ignore the system proxy" comes up most often. Utilities like curl, wget, git, pip, npm, and hundreds of others don't read Windows or macOS settings. They look at environment variables: special text values that the operating system passes to the launched program.
The standard variable names are: HTTP_PROXY for unencrypted requests, HTTPS_PROXY for encrypted ones, and NO_PROXY for an exception list. Many programs also accept these names in lowercase, and some understand only lowercase. So it's safer to set both variants.
Windows, Temporarily for One PowerShell Window
- Open PowerShell.
- Type the command
$env:HTTP_PROXY = "http://user123:Pa55word@185.10.20.30:8080"and press Enter. - Type
$env:HTTPS_PROXY = "http://user123:Pa55word@185.10.20.30:8080". Note: even for the HTTPS variable, the proxy address starts with http://, because that's the protocol for talking to the proxy itself, not to the site. - Type
$env:NO_PROXY = "localhost,127.0.0.1". - Verify:
curl https://api.ipify.orgwithout the -x flag. Now curl will take the proxy from the variable and show the proxy server's address.
These variables disappear when the window is closed. To make them permanent, run [Environment]::SetEnvironmentVariable("HTTPS_PROXY", "http://user123:Pa55word@185.10.20.30:8080", "User") and similarly for HTTP_PROXY. New terminal windows and newly launched programs will see them. Already-open programs will need to be restarted.
macOS and Linux
- Open Terminal.
- For the current session, run:
export HTTP_PROXY=http://user123:Pa55word@185.10.20.30:8080, thenexport HTTPS_PROXY=$HTTP_PROXY, thenexport http_proxy=$HTTP_PROXYandexport https_proxy=$HTTP_PROXY. - To make the setting permanent, add the same lines to the end of your shell config file. On macOS it's usually .zshrc in your home folder; on Linux, .bashrc. Open it with
nano ~/.zshrc, paste the lines, press Ctrl and O to save, then Ctrl and X to exit. - Apply the changes with
source ~/.zshrcor open a new terminal window.
Tip: Storing a password in a config file is insecure if multiple people use the computer. Alternative: ask your proxy provider for IP-based authentication without a password, or use a local proxy client that adds authentication itself and gives programs an address of 127.0.0.1 without a password.
Example 3: Apps with Their Own Config File
Some tools read neither the system nor environment variables but expect the setting in their own file. Git, for example, stores it in the global config: run git config --global http.proxy http://user123:Pa55word@185.10.20.30:8080. The npm package manager is configured with npm config set proxy http://185.10.20.30:8080 and a similar one for https-proxy. The pip client reads environment variables but also accepts a --proxy flag when invoked. For each such program, look for the answer to "why doesn't it see my proxy" in its documentation under the word proxy.
Why an App Might Still Connect Directly
Even after configuring at the application level, surprises are possible. An app running as administrator works in a different user's environment and doesn't see your user variables. A program in a Docker container has its own isolated environment, and variables must be passed inside explicitly. Some apps read variables only at launch and don't notice changes until restarted. And some programs, especially those related to games and voice chat, use the UDP protocol, which an HTTP proxy won't pass at all, and SOCKS5 will only pass with explicit support in the app.
Verification: Run curl https://api.ipify.org in the terminal with your configured variables and make sure the proxy address is shown. Then open a new terminal window: if the variables are set permanently, the result will repeat. In the messenger, look at the latency indicator next to the proxy: it should be green.
Step 5: Test Priorities in Practice
Goal of this stage: Reinforce your understanding of who overrides whom with a series of controlled experiments. After this, you'll be able to determine in a minute at which level the problem arose.
For the experiment, you need two different proxy addresses or at least one proxy and a direct connection. If you only have one proxy, the second option will be your baseline IP from Step 1.
- Initial state. Turn off the system proxy. In Firefox, choose "Use system proxy settings." Remove the launch parameter from Chrome and disable the extension. Clear the environment variables with the command
Remove-Item Env:HTTPS_PROXYin PowerShell orunset HTTPS_PROXYin macOS and Linux. In the messenger, choose "Use system settings." Check the IP in all three places: everything should show the baseline address. - Enable only the system. Turn on the system proxy. Check again. Chrome, Firefox, and the messenger will show the proxy address. Curl without variables on Windows and macOS will show the baseline: it doesn't read system settings. Write this result down — it's key to understanding.
- Override with the browser. Without turning off the system, switch Firefox to manual configuration with a different proxy or the "No proxy" option. Firefox will show a different result, while Chrome stays on the system proxy. The browser level overrode the system for just one browser.
- Override with the app. In the messenger, choose "No proxy." The indicator will change, and the connection will go directly despite the active system proxy. Then choose "Custom proxy": the app will again route to the specified server regardless of the system.
- Test variables. Set the HTTPS_PROXY variable to the second proxy. Curl will show the second proxy. Chrome and Firefox won't react to it: browsers on Windows and macOS don't read environment variables. On Linux, however, Chromium may take them into account if launched from a terminal with those variables set, which once again shows: the rules depend on the platform.
- Restore everything. Bring settings back to the state you need for work, and turn everything else off so you don't get confused later.
Tip: Create a simple table in your notes: rows are programs, columns are configuration levels. Mark which level each program reads. After a week, you'll have a personal map of your computer, and any proxy problem will be solved in a minute.
Verification: You can explain without hints why curl showed the baseline in step 2 and why browsers didn't react to the variable in step 5. If so, you've mastered priorities.
Step 6: Regain Control and Set Up a Rollback
Goal of this stage: Make sure you can return the system to its original state at any moment and record your final configuration.
How to Fully Disable the Proxy at All Levels
- Windows system: open Settings, Network & Internet, Proxy, click Set up, and move the toggle to Off. Then in PowerShell as administrator, run
netsh winhttp reset proxy. - macOS system: in network settings, turn off all toggles on the Proxies tab.
- Linux system: in network proxy settings, choose "Disabled."
- Firefox: in connection settings, choose "No proxy" or "Use system proxy settings."
- Chrome: remove the --proxy-server parameter from the shortcut, and in the extension, choose direct connection or remove the extension.
- Environment variables: on Windows, run
[Environment]::SetEnvironmentVariable("HTTPS_PROXY", $null, "User")and the same for HTTP_PROXY. On macOS and Linux, remove the export lines from your shell config file. - Git and npm: run
git config --global --unset http.proxyandnpm config delete proxy. - Apps: in each one where you configured a proxy, choose "No proxy" or "System settings."
Warning: If sites still open through a proxy after turning everything off, check your router settings. Some models allow you to set a proxy at the network level, which applies to all devices. That's essentially a zero level, sitting even below the system one.
Verification: After a full shutdown, all three verification points — browsers, terminal, and messenger — show the baseline IP address from Step 1.
Verifying the Result: A Checklist for Successful Configuration
Go through the list and check off each item. If something doesn't add up, go back to the corresponding step.
- You know your proxy's address, port, protocol type, and credentials, and you've verified them with curl using the -x flag.
- You know your baseline IP address without a proxy.
- The system proxy turns on and off, and Chromium browsers respond to this change.
- On Windows, WinINET and WinHTTP settings are synced with the netsh command if needed.
- Firefox works through its own proxy independently of system settings, or is explicitly switched to system settings.
- You can route Chrome through a separate proxy using a launch parameter or an extension.
- Environment variables are set, and curl without extra flags shows the proxy address.
- At least one app is configured with its own proxy and works through it while the system proxy is off.
- You've performed the experiment from Step 5 and understand the result of each of its points.
- You know how to roll back each setting.
How to Test Everything End-to-End
- Open an IP-check site simultaneously in Chrome and Firefox.
- Run
curl https://api.ipify.orgin the terminal. - Look at the proxy indicator in the messenger.
- Compare all results with what you expected based on the current level configuration. If reality matched expectations at all four points, the configuration is correct.
An additional success indicator: page load speed. Normal latency through a quality proxy adds 50 to 300 milliseconds. If pages take 10 seconds to open, the problem is either an overloaded proxy server or the wrong protocol type, causing the browser to take a long time trying to establish a connection before failing.
Common Mistakes and Their Solutions
The Proxy Is On in the System, but the Site Shows My Real IP
Cause: You're testing in Firefox with manual settings or "No proxy" mode, or Chrome has an extension active with a direct connection. The browser level overrides the system. Solution: In Firefox, choose "Use system proxy settings"; in the Chrome extension, choose system proxy mode.
407 Proxy Authentication Required Error
Cause: The proxy requires a username and password, but the app didn't provide them. This often happens with the system proxy on Windows, where there are no credential fields, and with programs lacking a password prompt interface. Solution: Put the credentials into environment variables in the format http://username:password@address:port, add an entry to Windows Credential Manager, or ask your provider to enable IP-based authentication.
Sites Don't Open at All, ERR_PROXY_CONNECTION_FAILED Error
Cause: Wrong address or port, or the proxy server is down. Solution: Verify the proxy with curl using the -x flag from Step 1. If it errors there too, the problem is on the server side or with your credentials. Temporarily disable the proxy to restore internet access and contact your provider.
ERR_TUNNEL_CONNECTION_FAILED Error or Empty Response
Cause: Mixed-up protocol type. You entered a SOCKS5 port in the HTTP field or vice versa. Solution: Check in your provider's dashboard which port corresponds to which protocol and correct the field.
A Command-Line Utility Ignores the System Proxy
Cause: This is normal behavior. Curl, wget, git, pip, and similar programs don't read Windows or macOS settings. Solution: Set the HTTP_PROXY and HTTPS_PROXY environment variables from Step 4, or use the program's own flags and config files.
Environment Variables Are Set but the Program Doesn't See Them
Cause: The program was launched before you set the variables, or it's running as a different user, or it reads only lowercase variable names. Solution: Restart the program, set the variables in both uppercase and lowercase, and for programs with administrator rights, set system variables instead of user ones.
Windows Updates Stopped Downloading After Proxy Configuration
Cause: Services use WinHTTP, but you only configured WinINET. The service either can't see the proxy and hits a closed network, or sees a proxy with authentication and can't authenticate. Solution: Run netsh winhttp import proxy source=ie to sync, or netsh winhttp reset proxy to make services go directly.
The Messenger Works Through a Proxy Even Though I Turned It Off Everywhere
Cause: The messenger itself has a custom proxy selected, which is the highest priority. Solution: Open the connection settings in the app and choose "No proxy" or "System settings."
Local Devices and Corporate Sites Stopped Opening
Cause: Requests to the local network are going to an external proxy that knows nothing about it. Solution: Add local addresses and internal domains to the exception list at each level: system, Firefox, and the NO_PROXY variable.
Additional Capabilities and Advanced Settings
A Local Proxy Client as a Single Entry Point
If you have several proxies with passwords and a dozen programs, managing them individually is tedious. Solution: install a local proxy client on your computer that listens on 127.0.0.1 at some port and forwards traffic to the real proxy with authentication. Then you point all programs to the single address 127.0.0.1 without a password, and change the external proxy in one place. This is especially handy for programs that can't pass a username and password.
Different Proxies for Different Tasks
Using your knowledge of priorities, you can build a scheme: the system connects directly, your work browser with an extension goes through one proxy, a separate Firefox profile through another, and build scripts in the terminal through a third using environment variables. Each level lives its own life and doesn't interfere with the others. This is a legitimate and common way to organize work with multiple work accounts or to test regional versions of services.
Mobile Proxies and Rotation
If you're using mobile proxies whose IP address changes on a schedule or on demand, remember: rotation happens on the server side, and your level settings don't change. However, some apps cache the connection and keep using the old address until they reconnect. To verify after rotation, restart the app or open a new tab in incognito mode.
Checking for DNS Leaks
When using SOCKS5, make sure site names are resolved through the proxy. Firefox has a dedicated checkbox for this, in curl use socks5h instead of socks5, and in environment variables specify socks5h:// as well. Find a DNS leak test service and confirm that the name servers shown belong to the proxy's region, not your home ISP.
Automating Switching
On Windows, you can create two .ps1 files: one enables the system proxy by modifying the registry key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings (parameters ProxyEnable and ProxyServer), and the other disables it. Put shortcuts on your desktop and switch with one click. On macOS, the same task is handled by the networksetup command with the -setwebproxy and -setwebproxystate flags.
FAQ: Common Questions About Configuring Proxies at Three Levels
Do I need to configure the proxy at all three levels at once?
No. Choose the level based on your task. The whole computer through a proxy — system level. Only web browsing — browser level. One specific program — application level. You only need to configure everything at once for the experiment in Step 5.
Why doesn't Chrome have its own proxy settings while Firefox does?
It's an architectural decision by the developers. Chromium relies on the operating system's network stack and doesn't duplicate its settings. Firefox historically uses its own network stack and provides an independent interface. Both approaches have merit; you just need to account for them.
How can I tell if a specific program reads the system proxy?
The most reliable way: turn on the system proxy, turn off all other levels, and check whether the address the program sees has changed. If the program has no built-in IP check, look at the documentation under the word proxy or ask the developers. General rule: programs with graphical interfaces on standard frameworks usually read the system, while console utilities almost never do.
Can I specify a username and password in Windows system settings?
The standard window has no fields for this. The browser will prompt for them on the first request. For programs without such a prompt, use environment variables with credentials in the address, Windows Credential Manager, or IP-based authentication on the provider's side.
What should I do if my printer or router stops working after I configure a proxy?
Add local addresses to the exceptions. On Windows, check "Don't use the proxy server for local addresses"; on macOS and Linux, add the 192.168.0.0/16 range to the bypass list; in the NO_PROXY variable, enter localhost, 127.0.0.1, and your router's address.
Why does the proxy work in the browser on my phone but not in apps?
The system proxy on Android and iOS applies only to Wi-Fi and only to apps that use standard network libraries. Many mobile apps use their own libraries or direct connections and ignore this parameter. Look for the proxy setting inside the app itself.
How can I check that DNS requests also go through the proxy?
Use SOCKS5 with remote name resolution: in Firefox, check the corresponding box; in curl and environment variables, use socks5h://. Then open a DNS leak test service and make sure the name servers match the proxy's region.
Environment variables are set, but Chrome doesn't see them. Is that a bug?
No, on Windows and macOS Chrome doesn't read HTTP_PROXY variables. It uses system settings, a launch parameter, or an extension. On Linux, Chromium may take variables into account if launched from an environment where they're set.
Can I configure different proxies for different tabs in the same browser?
Not with built-in tools: a browser's proxy applies to the entire process. Use separate browser profiles or an extension with per-domain rules that routes different sites through different proxies. That's closer to the auto-configuration topic, which is beyond the scope of this guide.
How do I quickly roll everything back if something breaks?
Turn off the system proxy in settings, choose "No proxy" in Firefox, disable extensions, remove environment variables, and select "No proxy" in apps. The order from Step 6 covers all levels. After that, check your IP: the baseline should be back.
Conclusion
Let's sum it up. You've tested your proxy server via the command line and recorded your baseline IP address. You've configured the proxy at the operating system level on Windows, macOS, Linux, Android, and iOS and learned about the two independent sets of settings on Windows. You've figured out why Chrome depends entirely on the system while Firefox lives its own life, and you've learned to route a Chromium browser through a separate proxy using a launch parameter or an extension. You've set up a proxy in the messenger and in command-line utilities via environment variables and seen why console programs ignore the system level. Most importantly, you've run an experiment that clearly demonstrated the priority rule: an app setting overrides the browser, the browser overrides the system, and the system only works for those who agree to listen to it.
Now any situation like "the proxy is on but the IP isn't changing" is no longer a mystery but a two-minute task: check which level has an overriding setting.
What's next? Create a map of your programs and the levels they read. Configure a working scheme for your tasks: maybe a single browser profile with an extension is enough, or maybe you need a local proxy client as a single entry point. If you work with rotating mobile proxies, check how your apps respond to address changes.
Where to develop further? A logical next step is to explore auto-configuration via PAC files: it lets a single browser use different proxies for different sites based on rules. It's also worth digging deeper into the differences between HTTP and SOCKS5, understanding how encrypted traffic tunneling through a proxy works, and mastering network diagnostic tools so you can see where packets actually go. But the foundation — understanding the three levels and their priorities — you already have. Good luck with your configuration!