macOS Apps Ignore the System Proxy: Causes and Per-App Fixes
Why some Mac apps skip the system proxy, how to check what macOS has set, and the fix for each kind of app.
The 3 most common causes
The proxy is set on a different network service. Apple's page says you choose your network service first; a proxy saved under Wi-Fi does nothing while the Mac is on Ethernet, and the reverse.
The program does not read the system settings. Chromium-based browsers use the system network settings according to Chromium's documentation, but terminal tools such as curl read environment variables instead, and many apps have their own proxy setting.
The wrong rows or the exceptions list. The rows for web proxy (HTTP), secure web proxy (HTTPS) and SOCKS proxy are separate, and hosts listed in the exceptions box (hosts and domains that skip the proxy) go direct.
Check the network service and rows; or use a browser-only setting
curl and other terminal tools
No, they read environment variables
Set http_proxy, HTTPS_PROXY or ALL_PROXY in the terminal
Apps with their own proxy setting
Depends on the app
Open the app's settings and enter the proxy there
Apps with no proxy setting at all
No way to tell from outside
Use a network-level tool or leave that app on your own connection
Chromium and curl rows follow their documentation read on 17 November 2026; the other two rows describe what you will find per app and are not a list of named apps.
Run the commands in the top code block. scutil --proxy shows the active proxy settings; networksetup shows each service. If HTTPEnable, HTTPSEnable and SOCKSEnable are all 0, the system proxy is not on at all.
Step 2: Set it on the service you really use
Open Apple menu, System Settings, Network, select your network service (Wi-Fi or Ethernet), click Details, then Proxies. For a Proxy302 HTTP IP fill web proxy (HTTP) and secure web proxy (HTTPS) with the address and port 2222; for SOCKS5 fill SOCKS proxy with port 3333. Turn on Proxy server requires password and enter the username and password. Save, then repeat for the other service if you switch between them.
Step 3: Test with a browser that follows it
Open https://ipinfo.io/json in Chrome. If the ip is the proxy exit, the system proxy works and only the stubborn app is the problem. If it is your own address, go back to Step 2 and check for typos and the exceptions list.
Look in the app's own settings for a proxy section and enter the same address, port and login there. For terminal tools, set the variables in the middle code block; curl reads them, but other tools may not, so check each tool's documentation. Use the same protocol and port pair as in My assets.
Step 5: If nothing else works, narrow it or go network-level
To proxy only one browser, use an add-on such as FoxyProxy or a launch switch like the bottom code block; the add-on route also takes a username and password. To send an app that has no setting through a proxy you need a tool that works at the network level, such as Clash, and its side effects on other traffic come with it.
scutil --proxy
# Per network service (replace Wi-Fi with the service you use)
networksetup -getwebproxy Wi-Fi
networksetup -getsocksfirewallproxy Wi-Fi
Example output differs per Mac. HTTPEnable 1 means the web proxy row is on; 0 means it is off. Nothing here contains your password.
Terminal tools: example
export http_proxy="http://USERNAME:PASSWORD@HOST:PORT"
export HTTPS_PROXY="http://USERNAME:PASSWORD@HOST:PORT"
export NO_PROXY="localhost,127.0.0.1"
# or one SOCKS5 setting for everything curl does
export ALL_PROXY="socks5h://USERNAME:PASSWORD@HOST:PORT"
curl https://ipinfo.io/json
Example only: replace the capitalised placeholders with the values from My assets. These variables apply to this terminal window only; curl reads them, other tools may not.
One Chrome window with a proxy: example
open -na "Google Chrome" --args --proxy-server="http://HOST:PORT"
Example only. The switch takes host:port, with no field for a username and password, so use it for a proxy that does not ask for a login, or use the system settings or a browser extension for one that does.
When one thing keeps failing
Browser works through the proxy, another app shows your own IP
Check Whether that app has its own proxy setting
Fix Enter the proxy in the app, or use the network-level option in Step 5.
Stop when If the app offers no proxy setting, do not expect the system proxy to reach it.
Terminal tools ignore the proxy
Check env | grep -i proxy in that window
Fix Export the variables in the same window where you run the tool; they do not reach other windows.
Stop when If curl works with the variables but another tool does not, that tool has its own setting.
Nothing loads after you set the system proxy
Check Port and row pairing, then the command-line test
Fix HTTP rows with 2222, SOCKS row with 3333, no extra characters. See the connection failed guide if pages still do not open.
Stop when If the same IP fails in curl, open a ticket with the order number.
FAQ
Why do only some Mac apps use the system proxy?
The system proxy is a setting programs choose to read. Chromium-based browsers read it by default, terminal tools read environment variables, and many apps have their own proxy setting.
Did macOS Sequoia change how the system proxy works?
Apple's Proxies page describes the same path in System Settings and I found no statement on changed behavior. If a program stopped following the proxy after an update, run Step 1 to see what is actually set before blaming the update.
HTTP IPs use port 2222 in the web proxy (HTTP) row, and in the secure web proxy (HTTPS) row too if https:// sites should also go through it; SOCKS5 uses port 3333 in the SOCKS proxy row.
When a proxy won't connect or is slow, check six things first: address, port and type, login and password, one proxy app only, the antidetect browser port, the exit IP.
Read on 17 November 2026: open System Settings, choose Network, choose your network service, open its details and select Proxies; the options are auto proxy discovery, automatic proxy configuration, web proxy (HTTP), secure web proxy (HTTPS) and SOCKS proxy; the exception boxes are Exclude simple hostnames and a box for hosts and domains that skip the proxy; Proxy server requires password for user name and password.
Read on 17 November 2026 from the manual of curl 8.7.1 on macOS (curl --manual): proxy variables can be written in lower or upper case, the lower case wins, http_proxy exists only in lower case; HTTPS_PROXY, ALL_PROXY and NO_PROXY are listed; using a variable has the same effect as the --proxy option; socks5:// and socks5h:// select a SOCKS version.
Read on 17 November 2026: Chromium uses the system network settings; the --proxy-server switch takes scheme-to-host:port mappings, one host:port for all traffic, or direct://.
Proxy302 local check on macOS (17 November 2026)
Local example · Confirmed on:
On a Mac with no proxy set, scutil --proxy listed HTTPEnable, HTTPSEnable and SOCKSEnable as 0 plus an exceptions list, and networksetup -getwebproxy Wi-Fi printed Enabled: No; commands and output format were read from that run.
Proxy302 product facts
Product observation · Confirmed on:
Product facts file of the site (checked 17 November 2026): HTTP on port 2222, SOCKS5 on port 3333; a static ISP IP leased per IP is issued with one protocol and also connects over the other protocol on its port; prices from US$0.50 for 1 day and US$7.99 for 30 days; a failed asset is reissued after a Support ticket with the order number.
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.