Firefox proxy setup
Firefox has its own proxy settings, separate from the computer's. Use them for our HTTP port with a saved login, or an extension when you want SOCKS5 with a login.
- Protocols
- HTTP with a login in the built-in settings; SOCKS5 with a login only through an extension
- UDP
- No. WebRTC can send UDP around the proxy
- Where the setting is
- Settings → General → Proxy settings → Configure proxy (older versions: Network Settings → Settings…)
- 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.
- The setting belongs to the current Firefox profile, not to the computer. To keep your usual browsing direct, create a second profile in
about:profilesand set the proxy there. - The SOCKS Host field has no place for a login, and our gateway needs one. Use HTTP on port 7000 in the built-in settings, or FoxyProxy for SOCKS5 on port 7001.
- 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
- Open Settings, stay on General, scroll to Proxy settings at the bottom and click Configure proxy. Typing "proxy" into the settings search finds it too. The Connection Settings window opens.
- Under Configure Proxy Access to the Internet, choose Manual proxy configuration.
- Enter
gate.aeonproxy.comin HTTP Proxy and7000in Port, and tick Also use this proxy for HTTPS. Leave SOCKS Host empty. - Tick Do not prompt for authentication if password is saved and click OK.
- Open any site. Firefox says the proxy is requesting a username and password: enter your login with its keys and your password, and let Firefox save them when it offers.
The tick in step 3 copies the host and port 7000 into HTTPS Proxy. In Firefox that field is the proxy for HTTPS sites, not a TLS connection to the proxy, so it stays on port 7000. Once the login is saved and the box in step 4 is ticked, Firefox signs in to the proxy without asking.
Check the proxy
Open the IP checker. It should show the country you asked for and an address that is not yours. If the WebRTC card shows your real address, open about:config and set media.peerconnection.ice.proxy_only_if_behind_proxy to true: WebRTC then connects only through the proxy when the page itself came through one. This is an advanced setting that Mozilla does not document, and it can stop WebRTC calls from connecting, so run the IP checker again to confirm the result. Setting media.peerconnection.enabled to false turns WebRTC off entirely, which also ends video calls in the browser. More in WebRTC leaks.
Rotating or sticky
For browsing, use a sticky login: all connections keep one IP for up to 60 minutes, then the same line moves to a new IP in Germany. A rotating login changes the IP with every new connection, and sites often sign you out when that happens.
LOGIN-cc-de-sid-firefox01-ttl-60To switch to another login, Firefox has to forget the saved one: remove the saved login for gate.aeonproxy.com in about:logins, restart Firefox and enter the new login when it asks.
If it does not work
| What you see | What to check |
|---|---|
| Your own IP on the IP checker | No proxy or Use system proxy settings is still selected, or you opened another Firefox profile. |
| The login window keeps coming back | The gateway rejected the login (407): a wrong password or an unknown key. Firefox sends an old saved login again and again until you delete it in about:logins. |
| Nothing loads after you chose SOCKS v5 | Firefox sends no login with its built-in SOCKS setting, and the gateway refuses connections without one. Clear SOCKS Host and use HTTP, or use FoxyProxy. |
| Settings say an extension controls how Firefox connects | A proxy extension (FoxyProxy, ZeroOmega) has taken over. Change the proxy in the extension, or disable it. |
| Some pages fail while others load | An exit failed (the gateway answers 502). Reload; if a sticky login keeps failing, change its -sid- key. See gateway errors. |
Questions
Yes, the built-in setting covers private windows of the same profile. An extension needs permission to Run in Private Windows, which Firefox requires for extensions that change proxy settings.