Windows proxy setup

Windows has one manual HTTP proxy setting for your user account. Browsers follow it and ask for your login; many other apps ignore it.

Protocols
HTTP proxy (HTTPS sites go through it). No SOCKS5 in Settings
Login and password
No fields in Windows: the browser asks in a sign-in window
UDP
No: the setting carries web traffic over TCP only
Where the setting is
Settings → Network & internet → Proxy
Works with
Residential and mobile proxies

Before you start

  • Windows 11 or 10. The setting covers Wi-Fi and Ethernet; a VPN connection has its own proxy settings.
  • Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product.
  • Optional: test gate.aeonproxy.com:7000:LOGIN:PASSWORD in the proxy tester first.
Connection details
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

  1. Open Settings (Windows key + I) and go to Network & internet → Proxy.
  2. Under Manual proxy setup, next to Use a proxy server, select Set up.
  3. In Edit proxy server, turn on Use a proxy server.
  4. In Proxy IP address type gate.aeonproxy.com (a host name is fine) and in Port type 7000.
  5. Tick Don't use the proxy server for local (intranet) addresses, so your router and printers stay direct, and select Save.
  6. Open Edge or Chrome and load any page. When the browser asks for the proxy's username and password, enter your login (with keys, see below) and password.

If your Windows 10 shows no Set up button, the switch and the address and port boxes are on the Proxy page itself. Fill them in the same way and select Save.

Port 7001 (SOCKS5) cannot be used here: the Socks box in the older Internet Options dialog takes no login.

Which apps use it

  • Edge, Chrome and other Chromium browsers follow it and ask for the login in their own sign-in window.
  • Firefox follows it at its default, Use system proxy settings, and asks for the login. For a Firefox-only proxy, see Firefox.
  • Other desktop apps differ: some follow the setting but cannot send a login and show a connection error, many ignore it.
  • curl and git read the HTTPS_PROXY and HTTP_PROXY variables instead, with the login in the URL. In PowerShell, $env:HTTPS_PROXY = "http://LOGIN:[email protected]:7000" sets one for that window (cURL and wget). Python and pip read the variables too; without them they take the Windows setting, which has no login, and fail with 407.
  • UDP traffic (games, voice and video calls) never goes through this setting.
  • Telegram has its own proxy setting: Telegram.

Check the proxy

In the browser that asked for the login, open the IP checker. It should show the exit IP and the targeted country, not your own. A WebRTC leak there means sites can see your real address over UDP: see WebRTC leaks.

Rotating or sticky

Use a sticky login here. A browser opens many connections for one page, and with a rotating login each leaves from a different IP, so sites you are signed in to may log you out. Type a login like this in the sign-in window:

LOGIN-cc-us-sid-pc01-ttl-60

The exit stays the same for up to 60 minutes, then the same login gets a new IP in the same country. Edge and Chrome keep the login you typed until they close: for a new IP sooner, quit the browser completely and sign in with another key, such as -sid-pc02.

If it does not work

What you seeWhat to check
The sign-in window keeps coming backThe login, the password or a key in the login is wrong (407). Copy them again from the dashboard.
ERR_PROXY_CONNECTION_FAILEDThe host or port is mistyped, or a firewall blocks outgoing port 7000.
ERR_TUNNEL_CONNECTION_FAILEDThe gateway refused the tunnel: no traffic left (402), a site blocked by default (403) or a failed exit (502). Check the dashboard, then retry.
One app shows a network error, the browser worksThat app follows the setting but cannot send a login. Route it with Proxifier.
The IP checker shows your own IPA VPN is on, or the browser has a proxy setting of its own (Firefox can). Turn the VPN off and check again.

Questions

No. Windows has no login field for a manual proxy, so each browser asks for it. For apps that cannot ask, use a proxy client such as Proxifier, which keeps the login in its own settings.

Not in Windows Settings. Use port 7001 in an app that logs in to SOCKS5, such as Proxifier or ProxyCap.

Proxy questions? Ask support in the live chat.