ZeroOmega proxy setup

Protocols

HTTP with a login in every browser; SOCKS5 with a login in Firefox only

UDP

No

Where the setting is

ZeroOmega Options → New profile… → Proxy Profile

Works with

Residential and mobile proxies

Before you start

• ZeroOmega from the Chrome Web Store, Edge Add-ons or Firefox Add-ons. Brave installs the Chrome Web Store version directly, Opera through its Install Chrome extensions add-on.
• Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product.
• Chrome, Edge, Brave, Opera: protocol HTTP, port 7000. Firefox: HTTP on 7000 or SOCKS5 on 7001.

Add the proxy

1. Click the ZeroOmega icon and choose Options.
2. Under Profiles, click New profile…, type a Profile name such as aeon-us, choose Proxy Profile and click Create.
3. In Proxy servers, on the (default) row, set Protocol to HTTP, Server to gate.aeonproxy.com and Port to 7000.
4. Click the lock button at the end of the row (Authentication). Enter your login with its keys as Username, then your password, and click Save changes.
5. Click Apply changes under Actions in the left column.
6. Open the ZeroOmega icon and pick aeon-us. [Direct] turns the proxy off; [System Proxy] hands control back to the computer's settings.

Do not choose HTTPS as the protocol. In ZeroOmega it means a TLS connection to the proxy, which port 7000 does not offer, so pages fail to load.

SOCKS5

In Chrome, Edge, Brave and Opera, the lock button on a SOCKS5 row shows a warning that your browser does not support SOCKS5 proxy authentication. That is a limit of the Chromium engine, and ZeroOmega cannot change it: stay on HTTP there. In Firefox the same row works. Choose SOCKS5, port 7001, enter the login under Authentication, and keep Proxy DNS requests via SOCKS proxy ticked so host names are resolved at the exit. ZeroOmega notes this box should be off if Firefox uses DNS over HTTPS.

Check the proxy

With the profile on, open the IP checker. The address and country should be the proxy's. ZeroOmega does not touch WebRTC, so check that card too and use the browser's own fix: the WebRTC setting in Brave, the about:config setting on the Firefox page, or the options on the Chrome and Edge pages. See WebRTC leaks.

Rotating or sticky

One profile carries one login. For browsing, make it sticky: one IP for up to 60 minutes, then a new IP from the same country.

LOGIN-cc-us-sid-zo01-ttl-60

A browser can keep sending the first login it used for gate.aeonproxy.com:7000, even after you switch to a profile with a different login. If the IP checker still shows the old country after a switch, restart the browser. For several IPs at once, use separate browser profiles, each with ZeroOmega and its own -sid- key. A Switch Profile can send chosen sites through a proxy profile and the rest direct.

If it does not work