How to Set Up 922 SOCKS5 Proxy in AdsPower, Multilogin & Dolphin Anty (2026)

922 residential proxies are credential-based, which means they drop into any antidetect browser in under a minute — no client, no extension, no waiting. This is the copy-paste guide: the exact credential format, where the fields go in AdsPower, Multilogin, Dolphin Anty, GoLogin and Octo, how to choose sticky vs rotating, and how to confirm the IP before you launch a single profile.

The 922 credential format

When you generate a proxy in the 922proxy.app dashboard, you get four fields. Every antidetect browser asks for these same four:

Type:     SOCKS5
Host:     gate.922proxy.app
Port:     7000
Username: user-12345-countryUS-cityNewYork-sessABC123
Password: your-secret-key

The targeting lives inside the username. You don't type a different host for each country — you change the tokens in the username:

• countryUS — country code (US, GB, DE, JP…)
• cityNewYork — optional city
• ispComcast — optional ISP
• sessABC123 — optional sticky session token (omit it for rotating)

Generate the username in the dashboard rather than hand-editing it — the dashboard guarantees the token names match what the gateway expects.

Sticky vs rotating — which to pick

• Sticky (recommended for accounts): include a sess token. The same residential IP is held for up to 30 minutes. Use this for logging into and warming accounts, checkout flows, anything that must not change IP mid-session.
• Rotating (recommended for scraping): omit the sess token. Every new request can come from a fresh IP. Use this for crawling, price monitoring, and high-volume data collection.

If you're not sure: one profile = one sticky session. That's the safest default for antidetect work.

AdsPower

1. Open Profiles → New Profile (or edit an existing one).
2. Scroll to Proxy. Set Proxy Type to SOCKS5.
3. Paste gate.922proxy.app into Host, 7000 into Port.
4. Paste the generated Username and Password.
5. Click Check Proxy. AdsPower shows the detected IP and country — confirm it matches your target.
6. Save, then Open the profile.

Tip: AdsPower's "Check Proxy" uses its own IP API, so it's a reliable confirmation that the credentials and targeting are correct before you launch.

Multilogin

1. Create or edit a profile and open the Proxy tab.
2. Set Connection type to SOCKS5.
3. Enter host gate.922proxy.app, port 7000.
4. Fill Login and Password with the generated username/password.
5. Click Check proxy → it should return the residential IP and its geo.
6. Save the profile.

Multilogin (both X and the classic builds) treats SOCKS5 with auth natively, so there's nothing special to enable.

Dolphin Anty

1. Proxies → Create (you can save the proxy once and reuse it across profiles).
2. Set type to SOCKS5.
3. Paste the host:port:login:password — Dolphin also accepts pasting the full string and auto-splits it into fields.
4. Hit Check → confirm IP/country.
5. Attach the saved proxy to any browser profile.

Dolphin's "paste the whole line" box is handy: format your 922 credential as gate.922proxy.app:7000:USERNAME:PASSWORD and it fills everything at once.

GoLogin & Octo Browser

Both follow the same pattern:

1. Open the profile's proxy settings.
2. Choose SOCKS5.
3. Enter host, port, username, password.
4. Use the built-in Check / Test button to confirm the IP.

In GoLogin you can also store the proxy in the proxy manager and assign it to multiple profiles; in Octo the proxy is bound per-profile and tested on save.

Verify the IP correctly

Don't trust "connected" — verify. Inside the launched profile, open a checker that shows the full fingerprint, not just the IP:

• IP & geo: confirm the country/city matches your target tokens.
• Type: it should resolve as residential / ISP, not datacenter.
• DNS / WebRTC leak: make sure your real IP isn't leaking via WebRTC — every antidetect browser above has a WebRTC setting; set it to "Altered/Proxy" so it matches the proxy IP.
• Timezone & locale: set the profile timezone to match the proxy's geo (most of these tools can auto-match from the proxy).

An IP in the right country with a leaking WebRTC or mismatched timezone is worse than no proxy at all — it looks deliberately evasive. Match the whole fingerprint to the IP's location.

Troubleshooting

• "Proxy connected" but wrong country: the username tokens are malformed — re-copy from the dashboard.
• Auth fails: you pasted a trailing space, or used an old key after regenerating. Generate fresh credentials.
• IP changes mid-session: you used a rotating credential. Add a sess token for sticky.
• Slow first connection: normal for the first handshake on a fresh residential IP; subsequent requests are fast.
• City not available: 922 returns an explicit "not covered" instead of silently swapping — pick a nearby city or drop to country-level.

FAQ

What proxy type should I choose?

SOCKS5 — it's universal and works in every antidetect browser. HTTP(S) is supported too if a specific tool needs it.

How do I get a sticky IP?

Use the sticky session option when generating credentials. 922 encodes the session in the username and holds the same residential IP for up to 30 minutes.

Connected but the IP is wrong — why?

The targeting tokens in the username are misformatted and the gateway fell back to a default region. Re-copy the exact username from the dashboard.

Can I use one plan across many profiles?

Yes — generate one sticky session per profile. They share the balance but each holds its own IP.