How to Configure 922S5 Proxy: Client, SOCKS5, Antidetect & Integration Guide (2026)

922S5 (also written 922 S5 Proxy) is a residential proxy service with 200M+ IPs across 190+ countries, supporting both SOCKS5 and HTTP(S) protocols. In 2026 it operates through two parallel methods: a desktop client app that forwards local ports, and credential-based SOCKS5 endpoints that work directly in any compatible tool without software installation. This guide covers both methods end to end — client setup, Proxy Manager, credential format, antidetect browser integration, Python and curl examples, and a complete troubleshooting reference.

What Is 922S5 Proxy?

922S5 Proxy (922proxy.com) is a residential proxy service provider offering over 200 million real residential IPs from 190+ countries. It supports SOCKS5 and HTTP(S) protocols, provides both rotating and sticky session modes, and ships with its own desktop Proxy Manager application for Windows and macOS — plus direct credential-based access for users who prefer to skip client software entirely.^[3]

Common use cases include account management, ad verification, market research, price monitoring, web scraping, and social media automation — tasks that require clean, real ISP-assigned IPs at volume across many geographic locations.

The Old Desktop Client: What Happened

922S5's original product was a Windows desktop application — you opened it, browsed a proxy list, selected an IP, and it bound a local SOCKS5 port that other programs could point to. That original client is discontinued.

The replacement is strictly better: credential-based SOCKS5 access works on any device, any operating system, any tool that speaks SOCKS5 — without installation, without updates, and without anything that could carry malware in a tampered build.

Two Configuration Methods in 2026

Method 1: Desktop Client / Proxy Manager Setup

Method 2: Credential-Based SOCKS5 (No Client Required)

For scraping scripts, headless servers, and any workflow where you don't want a desktop app running, 922S5 provides direct credential-based access. Generate the credentials from the User & Password Auth section of your dashboard.^[1]

Credential Format

# Standard SOCKS5 credential format for 922S5
socks5h://username-country-US:password@gateway.922proxy.com:PORT

# Where:
#   username      → your 922S5 account username
#   -country-US   → embedded country code in username (US = United States)
#                   change US to GB, DE, JP, etc. for other countries
#   password      → your account password
#   gateway       → endpoint from your dashboard
#   PORT          → port number from your dashboard

# Rotating session (new IP per connection):
socks5h://username-country-US:password@gateway.922proxy.com:PORT

# Sticky session (same IP held for duration):
# Append a session ID to the username to pin one IP:
socks5h://username-country-US-session-abc123:password@gateway.922proxy.com:PORT

Using the 922S5 Proxy Manager for Third-Party Providers

The Proxy Manager isn't limited to 922S5's own IPs — it also supports importing proxy strings from other providers. To add an external proxy:

1. Inside the Proxy Manager, click Add Proxy.
2. Instead of selecting 922S5Proxy, paste your external provider's proxy command string directly into the input field.
3. Click Save. The Proxy Manager creates a local port for it, just as it does for 922S5's own proxies.

This makes the Proxy Manager useful as a general-purpose local proxy hub — you can manage 922S5 IPs and third-party IPs (like Nstproxy residential proxies) from the same interface, with all traffic forwarded through local ports in a consistent format.^[4]

Antidetect Browser Integration

922S5 has native integration with most major antidetect browsers. The two integration modes available are:

• Port forwarding via client — run the 922S5 Proxy Manager, forward an IP to a local port, then use 127.0.0.1:PORT as the SOCKS5 proxy in your browser profile.
• 922S5auto (rotating residential) — a special proxy type available natively in many antidetect browsers that connects directly to 922S5's rotating pool without manual IP selection or the Proxy Manager running.^[2]

The supported antidetect browsers with direct 922S5 integration include: AdsPower, BitBrowser, GoLogin, VMLogin, MULogin, Linken Sphere, Incogniton, ClonBrowser, SessionBox, Dolphin Anty, Kameleo, MoreLogin, DICloak, and many others listed in the 922S5 documentation.^[5]

AdsPower Integration Step-by-Step

Python and curl Configuration Examples

curl

# Basic request through 922S5 SOCKS5 credential
# socks5h:// ensures DNS resolves at proxy (no DNS leak)
curl --proxy socks5h://username-country-US:password@gateway.922proxy.com:PORT \
     https://ipinfo.io/json

# Verify the exit IP and country match your config
curl --proxy socks5h://username-country-JP:password@gateway.922proxy.com:PORT \
     -s https://ipinfo.io/json | python3 -m json.tool

Python — requests

import requests

proxy_url = "socks5h://username-country-US:password@gateway.922proxy.com:PORT"
proxies = {
    "http":  proxy_url,
    "https": proxy_url,
}

response = requests.get("https://ipinfo.io/json", proxies=proxies, timeout=15)
data = response.json()
print(f"Exit IP: {data['ip']} | Country: {data['country']} | City: {data.get('city')}")

Python — aiohttp (async)

import asyncio
import aiohttp

async def check_ip():
    proxy = "socks5://username-country-US:password@gateway.922proxy.com:PORT"
    async with aiohttp.ClientSession() as session:
        async with session.get("https://ipinfo.io/json", proxy=proxy) as resp:
            data = await resp.json()
            print(f"IP: {data['ip']} | Country: {data['country']}")

asyncio.run(check_ip())

Verifying Your Configuration Is Working

Always verify before routing real work through any proxy setup:^[1]

• IP check: visit ipinfo.io or run curl -s https://ipinfo.io/json through the proxy — confirm the returned IP and country match your configuration.
• DNS leak check: if you used socks5h://, your local resolver never saw the hostname — run a DNS leak test page through the proxied browser and confirm it shows the proxy's resolver, not your ISP's.
• WebRTC check: in an antidetect browser profile, open a WebRTC test page — it must show the proxy IP, not your real device IP. If it shows your real IP, WebRTC protection is disabled in the profile settings.

Troubleshooting Common Issues

FAQ

Further Reading