Anti-detect browsers
Multilogin, GoLogin, Dolphin Anty and AdsPower all add a proxy to a browser profile through the same handful of fields, labelled differently in each app.
Fields to fill, per profile
| Field | Value |
|---|---|
| Proxy type | HTTP, or SOCKS5 |
| Host / IP | gate.avocadoproxies.com |
| Port | 8080 for HTTP, 1080 for SOCKS5 |
| Login / Username | USERNAME-cc-de-sid-<profile id> |
| Password | PASSWORD |
All four apps offer HTTP (some list it as “HTTP/HTTPS”) and SOCKS5. The gateway answers both, with the same login, password and targeting keys; the port is the only thing that changes. Use the one your profiles are already set up with, and do not mix the two inside one profile.
One profile, one session id
A profile’s whole point is a stable fingerprint. Give each one its own -sid-<id> so the exit address stays paired with that fingerprint instead of drifting to a new one on every launch. Mixing several profiles behind one session id, or behind none at all, undoes the separation the tool is built to give you.
A session id holds an address for a limited time (55 minutes on residential and mobile, 115 minutes on premium residential at most; see Sticky sessions), not for the life of the profile. A profile you keep open for days should expect its address to rotate periodically rather than stay fixed the whole time, so plan for that instead of treating the address as permanent.
The “check proxy” / “test proxy” button in these apps opens a real connection through your proxy user, the same as any other request: it counts against your GB balance, and if the profile carries a session id, it spends part of that session too. Test a new profile once, not on every launch.
- Test it. Open the profile and load any page. A normal page load means the connection worked. Open Dashboard → Usage → Live in a second tab and watch the destination land within a few seconds.
- For anything else, see the troubleshooting page.