FoxyProxy proxy setup
FoxyProxy stores proxies with their login inside the browser. It is the easy way to use SOCKS5 with a login in Firefox, and it can keep WebRTC behind the proxy in Chrome too.
- Protocols
- HTTP with a login in Firefox, Chrome and Edge; SOCKS5 with a login in Firefox only
- UDP
- No
- Where the setting is
- FoxyProxy Options → Proxies → Add
- Works with
- Residential and mobile proxies
Before you start
- FoxyProxy Standard from Firefox Add-ons, the Chrome Web Store or Edge Add-ons. The Basic edition hides some options used below.
- Firefox: allow FoxyProxy to Run in Private Windows in
about:addons. Firefox requires it for extensions that change proxy settings. - 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- Port (SOCKS5)
7001- 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
- Click the FoxyProxy icon → Options, open the Proxies tab and click Add.
- Fill in Title (for example
AeonProxy US) and Hostnamegate.aeonproxy.com. Set Type to HTTP with Port7000, or in Firefox SOCKS5 with Port7001. - Enter your login with its keys in Username and your password in Password. For SOCKS5 in Firefox keep Proxy DNS on, so host names are resolved at the exit.
- Click Save. Nothing changes until you save.
- In the FoxyProxy popup, click the proxy's title to send all traffic through it. Disable turns the proxy off; Proxy by Patterns sends only the sites that match your patterns.
Pick HTTP, not HTTPS: in FoxyProxy, HTTPS means a TLS connection to the proxy, which port 7000 does not offer. In Chrome and Edge, a SOCKS5 entry cannot carry the username and password because Chromium has no SOCKS authentication, so use HTTP there.
Keep WebRTC behind the proxy
Open Options and set Limit WebRTC to Disable Non-Proxied (Chrome, Edge and Firefox) or Proxy Only (Firefox). FoxyProxy asks for the privacy permission once, and the change applies without Save. In Firefox, Toggle WebRTC turns WebRTC off completely, which also stops browser calls. See WebRTC leaks.
Check the proxy
With the proxy on, open the IP checker: the address and country should be the proxy's, and the WebRTC result should not show your own address. To test the line outside the browser, paste it into the proxy tester.
Rotating or sticky
Each entry carries one login. For browsing, make it sticky: one IP for up to 60 minutes, then a new IP from the same place on the same line.
LOGIN-cc-us-city-losangeles-sid-fox01-ttl-60Firefox can give each tab or container its own entry: Tab Proxy and Container Proxy in the popup are Firefox only. To keep several Firefox entries with the same host and port but different logins, add a letter to the port (7001a, 7001b); FoxyProxy strips it before connecting. In Chrome and Edge the letters do not work and FoxyProxy keeps one login per host and port, so use one browser profile per login.
If it does not work
| What you see | What to check |
|---|---|
| The browser shows its own login window | The entry has no username and password, or they were not saved. Fill them in and click Save. |
| SOCKS5 fails in Chrome or Edge | Chromium cannot send a SOCKS5 login. Change Type to HTTP and Port to 7000. |
| "Settings are controlled by other extensions" | Another proxy extension is active. Disable it and select the proxy again. |
| Firefox ignores FoxyProxy | Run in Private Windows is not allowed for the extension. |
| Pages fail right after you pick the entry | The gateway rejected the login (407): a wrong password, or a key in the username that is not in the lists. FoxyProxy sends the login once, then cancels the request instead of asking again. |
Questions
Firefox lets extensions pass a username and password with a SOCKS5 proxy. Chrome has no SOCKS authentication at all, so in Chrome and Edge use HTTP on port 7000, which carries HTTPS sites too.
Yes, except the default container. Make one entry per container with its own -sid- key, add port letters if the host and port repeat, and pick the entry under Container Proxy in the popup while a tab of that container is open.