Microsoft Edge proxy setup
Edge takes its proxy from the Windows or macOS settings, a launch flag or an add-on. Use our HTTP port: Edge runs on Chromium and cannot log in to a SOCKS5 proxy.
- Protocols
- HTTP with a login. SOCKS5 only without a login, so not with our gateway
- UDP
- No. WebRTC can send UDP around the proxy unless a policy or add-on stops it
- Where the setting is
- Settings → System and performance → your computer's proxy settings, the
--proxy-serverflag, or an add-on - Works with
- Residential and mobile proxies
Before you start
- Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product.
- On Windows the system proxy is shared by Edge, Chrome and many other apps. For Edge alone, use the flag below or an add-on: ZeroOmega and FoxyProxy are both on Edge Add-ons.
- On a work computer, the organization may set Edge's proxy by policy (
ProxySettings). Edge then ignores the flag's proxy options, and add-ons cannot change the proxy.
- 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 in Windows
- In Edge, open Settings and more (…) → Settings → System and performance and follow the link to your computer's proxy settings (Windows Settings → Network & internet → Proxy).
- Under Manual proxy setup, click Set up next to Use a proxy server.
- Turn on Use a proxy server, enter
gate.aeonproxy.comin Proxy IP address and7000in Port, and click Save. - Open a site in Edge. When it asks for the proxy's username and password, enter your login with its keys and your password.
On a Mac, enter the same host and port under Web proxy (HTTP) and Secure web proxy (HTTPS) in System Settings → Network → your connection → Details → Proxies, then click OK. Edge still asks for the login. More: Windows, macOS.
Or start Edge with a launch flag
This leaves the Windows setting alone and runs a separate Edge with its own profile folder.
# Windows (Command Prompt)
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --proxy-server="http://gate.aeonproxy.com:7000" --user-data-dir="%LOCALAPPDATA%\EdgeProxy"
# macOS (Terminal)
/Applications/Microsoft\ Edge.app/Contents/MacOS/Microsoft\ Edge --proxy-server="http://gate.aeonproxy.com:7000" --user-data-dir="$HOME/edge-proxy"
# Edge then asks for LOGIN and PASSWORDEdge reads the flag only when a new instance starts. Startup boost keeps Edge running in the background after you close its windows, so a command with your usual profile folder goes to that copy and the flag is lost; the separate --user-data-dir avoids this.
Check the proxy
Open the IP checker in Edge: the address and country should match what you asked for. Check the WebRTC card too: by default WebRTC sends UDP outside the proxy, and a page can see your real address. On a computer you manage, set the Edge policy WebRtcLocalhostIpHandling to disable_non_proxied_udp and restart Edge. Otherwise FoxyProxy's Limit WebRTC → Disable Non-Proxied does the same for one profile. See WebRTC leaks.
Rotating or sticky
Use a sticky login, so every tab leaves from one IP. This line keeps its IP for 45 minutes, then gets a new one in the UK.
LOGIN-cc-gb-sid-edge01-ttl-45Edge keeps the typed login while it runs, and closing its windows may not stop it. Before you sign in with a new line, turn startup boost off at edge://settings/system/manageSystem, or end Microsoft Edge in Task Manager.
If it does not work
| What you see | What to check |
|---|---|
| Pages load from your own IP | Use a proxy server is off, a setup script or automatic detection is used instead, or an add-on or policy controls Edge's proxy. |
| The login prompt keeps coming back | The gateway rejected the login (407). Check the password and each key in the login against the dashboard. |
| An add-on set to SOCKS5 on port 7001 fails | Edge cannot send a SOCKS5 login. Set the add-on to HTTP on port 7000. |
| Windows apps stopped connecting | They use the same system proxy and cannot ask for a login. Turn the proxy off when you finish, or use the flag or an add-on. |
| The flag has no effect | Edge was still running with that profile folder, or a policy sets the proxy (see edge://policy). |
An error page with an ERR_ code | Edge's engine is Chromium, so the codes mean the same as in Chrome: see the Chrome table. |
Questions
Not through the Windows setting or the flag, which give one login to all of Edge. Install an add-on from Edge Add-ons in each profile and give each one its own -sid- key.
The Windows setting and the flag do. An add-on works in InPrivate windows only after you allow it there on its details page in edge://extensions.