macOS proxy setup
macOS keeps proxy settings for each network service, with a login and password. Safari and many Mac apps use them; Terminal tools and some apps need their own setup.
- Protocols
- Web proxy (HTTP) and Secure web proxy (HTTPS), both on port 7000. A SOCKS field exists too
- Login and password
- Yes: Proxy server requires password
- UDP
- No: the system proxies carry TCP only
- Where the setting is
- System Settings → Network → your network → Details → Proxies
- Works with
- Residential and mobile proxies
Before you start
- macOS Ventura or later. On older versions the same options are in System Preferences → Network → Advanced → Proxies (click OK, then Apply).
- The proxy belongs to one network service (Wi-Fi, Ethernet, a USB adapter): set it on each one you use.
- Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product.
- Host
gate.aeonproxy.com- Port (HTTP / HTTPS)
7000- Login
- your proxy login, with targeting keys if you need them:
LOGIN-cc-us-sid-abc123 - Password
- your proxy password
Copy the login and password from the Residential or Mobile page of the dashboard; the generator there also writes ready lines. Key syntax: targeting and sessions.
Add the proxy
- Choose Apple menu → System Settings → Network.
- Click Wi-Fi (or your Ethernet service), click Details next to the network you are connected to, then click Proxies.
- Turn on Web proxy (HTTP). Server
gate.aeonproxy.com, port7000. Turn on Proxy server requires password and enter your login (with keys, see below) and password. - Turn on Secure web proxy (HTTPS) and enter the same server, port
7000, login and password. It is the proxy for HTTPS sites and still talks plain HTTP to our gateway. - Leave SOCKS proxy off and the list of excluded hosts as it is. Click OK.
Why not SOCKS? macOS accepts a SOCKS proxy with a password, but Chrome, Edge and other Chromium browsers cannot log in to it. The two web proxies work in every browser.
Which apps use it
- Safari and many apps built on Apple's own networking follow it. If Safari asks for the login, enter the same values.
- Chrome, Edge and other Chromium browsers (Brave, Opera) follow it and ask for the login again in a Sign in window.
- Firefox follows it at its default setting, Use system proxy settings, and asks for the login itself.
- curl, git and Homebrew ignore System Settings and read
http_proxyandhttps_proxy(below). Python and pip read System Settings when those variables are unset, but not the password, so they get a 407: export the variables for them too. - Apps with their own connections, such as games, many messengers and video calls, and all UDP traffic go around it. Route them with Proxifier, or use the app's own setting (Telegram).
From the Terminal
networksetup changes the same settings from the Terminal. List the services, then set both proxies. macOS may ask for an administrator password; the commands stay in your shell history.
networksetup -listallnetworkservices
networksetup -setwebproxy "Wi-Fi" gate.aeonproxy.com 7000 on LOGIN-cc-us-sid-mac01-ttl-60 PASSWORD
networksetup -setsecurewebproxy "Wi-Fi" gate.aeonproxy.com 7000 on LOGIN-cc-us-sid-mac01-ttl-60 PASSWORD
# turn both off again
networksetup -setwebproxystate "Wi-Fi" off
networksetup -setsecurewebproxystate "Wi-Fi" offFor curl, git and other Terminal tools, export the variables in the window where you need them:
export http_proxy="http://LOGIN-cc-us-sid-mac01-ttl-60:[email protected]:7000"
export https_proxy="$http_proxy"
curl https://api.ipify.orgCheck the proxy
Open the IP checker in every browser you use. It should show the exit IP and the targeted country. A WebRTC warning means the browser shows your own address over UDP: see WebRTC leaks.
Rotating or sticky
Put a sticky login, such as LOGIN-cc-gb-sid-mac01-ttl-60, in both proxies: with a rotating login every connection gets a new IP, and sites you are signed in to see your address jump. The IP is kept for up to 60 minutes, then the same login gets a new one in the same country. For a new IP sooner, change the key (-sid-mac02) in both proxies and restart the browser.
If it does not work
| What you see | What to check |
|---|---|
| Safari keeps asking for the login | The login, the password or a key in the login is wrong (407). Enter them again in both proxies. |
Chrome: ERR_TUNNEL_CONNECTION_FAILED | The gateway refused the tunnel: no traffic left (402), a site blocked by default (403) or a failed exit (502, retry). |
Chrome: ERR_PROXY_CONNECTION_FAILED | The server or port is mistyped. Both proxies use port 7000. |
| Terminal shows your own IP | Terminal ignores System Settings. Export https_proxy as above. |
Questions
Chromium browsers do not use logins stored in system proxy settings; type the same login and password in their sign-in window.
Yes, in apps that log in to SOCKS5: Proxifier, or curl with all_proxy="socks5h://LOGIN:[email protected]:7001". Avoid the system SOCKS field for browsers.