SOCKS5 Proxies With Login and Password, From US$1.50/GB
Every Proxy302 line speaks SOCKS5: rotating residential, static ISP and datacenter. Choose SOCKS5 on the order page, then connect to port 3333 with your username and password.
SOCKS5 relays any TCP connection after a short handshake defined in RFC 1928, so antidetect browsers, Telegram, curl, Python scripts and other apps can send their traffic through it — not only web browsers. With a socks5h:// address the proxy also looks up domain names, so DNS requests leave from the proxy's location instead of your own network. If you picked a state, city or ISP on the Premium line and need the state and city to be exact, use remote resolution (socks5h) or an HTTP proxy.
Choose SOCKS5 when your tool supports it, when names should resolve at the proxy, or when the traffic is not plain web requests. Choose HTTP on port 2222 for Chrome's own proxy settings and for tools that only have an HTTP proxy field. Both run on the same gateway with the same username and password.
One rule decides most setups: Proxy302's SOCKS5 port always asks for a username and password (RFC 1929). In our test it turned away clients that offered no login, so a tool that cannot send a SOCKS5 login cannot connect.
Scroll horizontally with the arrow keys to read all content.
Recommended SOCKS5 setup
Item
Choose
Why
Protocol
SOCKS5, set under Protocol on the order page
A static ISP or datacenter IP keeps the protocol it was bought with
Port
3333 (HTTP uses 2222)
Each port answers only its own protocol
Login
Username and password from My assets
The gateway asks for them on every connection
Address
socks5h://USERNAME:PASSWORD@HOST:PORT
With socks5h the proxy resolves domain names
Tool
One that can send a SOCKS5 login
Chrome's built-in proxy settings cannot: use HTTP there
The button below opens rotating residential proxies. Static ISP and datacenter IPs are bought on their own product pages: choose Protocol, Region, Term and Quantity (up to 100 IPs at a time) before you pay.
Scroll horizontally with the arrow keys to read all content.
Which Proxy302 line to buy for SOCKS5
Item
Rotating residential
Static ISP
Datacenter
SOCKS5
Yes — pick SOCKS5 when you generate a proxy
Yes — pick SOCKS5 when you buy; the IP keeps it
Yes, since 17 October 2026 — pick it when you buy
Connect to
proxy.proxy302.com:3333 (HTTP uses port 2222)
The host and port on the asset; SOCKS5 uses port 3333
The host and port shown on the asset
Price
Per GB: Budget US$1.50/GB from 1 GB, down to US$1.124/GB at 500 GB; Premium US$5.00/GB, down to US$4.25/GB at 300 GB
Per IP and lease term: US$0.50 for one day, US$7.99 for 30 days
Per IP and lease term: US$0.25 for one day, US$3.99 for 30 days
How many
One proxy per generation, drawing on the GB you bought
Quantity 1 to 100 per order; each IP is charged separately
Quantity 1 to 100 per order; each IP is charged separately
The IP
Rotates per request, or stays for a sticky session
Fixed for the lease
Fixed for the lease
Locations
195+ countries and regions, with state and major-city targeting
Countries listed on the order page; stock changes daily
Countries listed on the order page; stock changes daily
Good for
Scraping, price and search-result checks, ad verification
Accounts, shops and antidetect browser profiles
APIs, testing and bulk jobs without logins
Prices in US dollars from the price list, checked on 21 October 2026; checkout shows the binding total. Auto-renew is optional and set per IP: switch it on in My assets (new purchases start with it off), or renew a static ISP or datacenter IP by hand there before its lease ends.
Open the product and set Protocol to SOCKS5 under Connection settings. Rotating residential: buy GB for a line, then generate the proxy. Static ISP and datacenter: choose Region and Term, and set Quantity to the number of IPs you need (up to 100 at a time, each charged separately).
Copy the four fields
In My assets open the proxy and click View credentials or Copy all: host, port, username and password. A rotating residential SOCKS5 proxy connects to proxy.proxy302.com on port 3333.
Enter them as SOCKS5
In your tool choose SOCKS5 (some tools say SOCKS v5) and fill in host, port, username and password. curl and Python requests take one URL instead: socks5h://USERNAME:PASSWORD@HOST:PORT — with socks5h the proxy, not your computer, looks up domain names.
Before continuing Do not send SOCKS5 to port 2222 or HTTP to port 3333: the table of errors below shows what happens.
Check the exit IP
Request ipinfo.io through the proxy with the commands below, or open it in the browser profile that uses the proxy.
Expected result The IP and country match the proxy you bought.
Save as proxy302-socks.conf and make it readable only by you (chmod 600). Then compare curl -q --noproxy "" --config proxy302-socks.conf https://ipinfo.io/json with the direct curl -q --proxy "" https://ipinfo.io/json — the first shows the proxy's IP and country. On Windows run both in Command Prompt (cmd.exe).
Requests needs its SOCKS extra. socks5h sends DNS lookups through the proxy; plain socks5 resolves them on your computer. Put the username and password from My assets in place of the placeholders.
Yes — choose SOCKS5 in the profile's proxy settings
Follow the setup page for your browser
Telegram (phone apps and Telegram Desktop)
Yes — SOCKS5 with server, port, username and password
Add it in the app's proxy settings
iPhone and Android apps
Depends on the app
See our Shadowrocket (iPhone) and v2rayNG (Android) guides
Chromium's proxy documentation: "No authentication methods are supported for SOCKSv5 in Chrome." In our test the gateway required a username and password, so plain Chrome cannot sign in to a Proxy302 SOCKS5 proxy.
On 18 October 2026 at 04:31 UTC we connected to proxy.proxy302.com from a network in Singapore with curl 8.7.1 and with raw SOCKS5 handshakes, using no credentials or deliberately wrong ones. A second run at 05:43 UTC repeated the curl checks on the entry hosts that static ISP and datacenter assets use and got the same answers. The table below lists what came back, so you can match the message your tool shows to its cause.
Two answers matter most. The SOCKS5 port asked for a username and password (method 0x02, the RFC 1929 username and password login) even when the client offered only "no authentication", so a client without a login cannot connect. And the HTTP port gave no answer at all to a SOCKS5 greeting, so a wrong port looks like a timeout, not an error.
Check The gateway rejected the login. It happens with no credentials and with wrong ones — both gave this message in our test.
Fix Copy the username and password again with Copy all in My assets and enter them in the tool's SOCKS5 settings.
The connection hangs, then "Connection timed out"
Check Is the tool sending SOCKS5 to port 2222? That is the HTTP port; it never answered our SOCKS5 greeting, so the tool waits until its own timeout. In our test curl waited until the 20-second limit we gave it.
Fix Use port 3333 for SOCKS5.
"Received HTTP/0.9 when not allowed" or "Connection reset by peer" with an HTTP proxy setting
Check Is an HTTP proxy pointed at port 3333? The SOCKS5 port refused our HTTP requests.
Fix Use port 2222 for HTTP, or switch the tool to SOCKS5.
SOCKS4 or SOCKS4a fails with "Connection reset by peer"
Check The gateway speaks SOCKS5 only; it refused our SOCKS4 request.
Fix Choose SOCKS5 (SOCKS v5) in the tool.
407 or "CONNECT tunnel failed, response 407" on port 2222
Check The HTTP port is asking for the login: 407 means Proxy Authentication Required.
Fix Enter the username and password from My assets, or move the tool to SOCKS5 on port 3333.
Chrome cannot use the SOCKS5 proxy at all
Check Chrome has no SOCKS5 authentication, and our SOCKS5 port requires a login.
Fix Use HTTP on port 2222 in Chrome, or an antidetect browser profile that handles the SOCKS5 login.
Domain names are looked up on your own network
Check With socks5:// curl and Python resolve names on your computer; with socks5h:// the proxy does.
Fix Switch to socks5h:// so lookups happen at the proxy's location, then check the IP again.
A static ISP or datacenter IP needs the other protocol
Check The protocol is set when you buy, and My assets has no protocol switch.
Fix Buy another IP with the protocol you need; on rotating residential, generate one proxy of each type.
SOCKS5 proxy FAQ
What is a SOCKS5 proxy?
A proxy that relays your app's TCP connections after a short handshake defined in RFC 1928, with an optional username and password login defined in RFC 1929. It forwards the bytes without interpreting web requests, so any app that supports SOCKS5 can use it — not only browsers.
Four values in any SOCKS5-capable tool: type SOCKS5, host proxy.proxy302.com, port 3333, and the username and password from My assets. In curl that is one line: curl -x socks5h://USERNAME:[email protected]:3333 https://ipinfo.io/json
SOCKS5 costs nothing extra; you pay for the line it runs on. Rotating residential is billed per GB: Budget US$1.50/GB from 1 GB, US$1.42/GB at 50 GB, US$1.35/GB at 100 GB, US$1.20/GB at 300 GB and US$1.124/GB at 500 GB; Premium US$5.00/GB, down to US$4.25/GB at 300 GB. Bought traffic does not expire. A static ISP IP costs US$0.50 for one day or US$7.99 for 30 days, a datacenter IP US$0.25 for one day or US$3.99 for 30 days. There is no free trial.
Choose what your tool can log in with. HTTP on port 2222 works in browsers and most tools; SOCKS5 on port 3333 suits apps and scripts that support it and lets the proxy look up domain names. For a static ISP or datacenter IP decide before you buy, because the IP keeps its protocol.
Rotating residential: generate one proxy of each type; both draw on the same traffic of that line. Static ISP and datacenter: no — each IP is issued with the protocol you chose at purchase, and My assets has no protocol switch.
No. SOCKS5 relays data as it is, and RFC 1929 notes that its username and password travel in cleartext. Use HTTPS sites and apps so the content stays encrypted between you and the site.
No. Chromium's documentation says no SOCKS5 authentication methods are supported. Use HTTP on port 2222 in Chrome, or an antidetect browser profile that handles the SOCKS5 login.
Yes. Telegram's apps accept a SOCKS5 proxy with server, port, username and password in their proxy settings. Use one static ISP IP per account, in a country where Telegram works.
Real household IPs in 195+ countries with state and major-city targeting. Rotate on every request or keep sticky sessions. From US$1.50/GB, US$1.35/GB at 100 GB. HTTP and SOCKS5.
Fast datacenter proxies with fixed IPs, low latency and high concurrency — the lowest cost per IP for APIs, testing and bulk jobs. Pick the country; pay per IP and term.
Set up a proxy in AdsPower, BitBrowser, GoLogin, Kameleo, Hidemium or GenLogin: one IP per profile, where each field goes, and what a failed proxy check really means.
Check the exit IP, country and ISP your proxy really gives you in 30 seconds — and why IP databases disagree on the city. With our own test of three lookup services.
Residential proxies from US$1.50/GB, static ISP IPs US$7.99 and datacenter IPs US$3.99 per month. Pay as you go, no subscription.
Reference links
10
Proxy302 console: order page and My assets
Product observation · Confirmed on:
Read from the console source on 21 October 2026: every product page has a Protocol switch (HTTP / SOCKS5) under Connection settings; the public endpoint is proxy.proxy302.com:3333 for SOCKS5 and :2222 for HTTP (src/lib/proxyEndpoint.ts); static ISP and datacenter purchases take Region, Term and a Quantity of 1 to 100 IPs, bought and charged one by one; My assets offers View credentials and Copy all.
Product facts file of the site (src/routes/site-v2/commercial/productFacts.json), read on 21 October 2026; its facts were checked against the console, the backend and read-only production queries on 18 and 19 October 2026: SOCKS5 on rotating residential, static ISP and datacenter (datacenter since 17 October 2026); one protocol per static ISP or datacenter IP; Quantity 1 to 100 IPs per order, each charged separately; residential prices per GB with package prices; no free trial. Since 24 October 2026 the console has an Auto-renew IP switch for static IPs (off for new purchases) on the purchase page and per IP in My assets.
18 October 2026, 04:31 UTC, from a network in Singapore: raw SOCKS5 greetings and curl 8.7.1 requests to proxy.proxy302.com without valid credentials. Port 3333 answered with method 0x02 (username/password) even to a client that offered only 0x00 (no authentication), returned status 1 for wrong credentials and refused SOCKS4 and HTTP requests. Port 2222 answered "407 Proxy Authorization Required" without credentials and gave no answer to a SOCKS5 greeting, so curl stopped at the 20-second limit we set. At 05:05 UTC the proxy302-socks.conf shown on this page, filled with wrong credentials, reached port 3333 and got the same rejection. At 05:43 UTC a second run from the same network repeated the curl checks, SOCKS4a included, on proxy.proxy302.com and on the entry hosts used for static ISP and datacenter assets: every host gave the same answers, and on port 2222 curl waited until its 25-second limit.
One network, two runs on one morning, without a valid account: it shows how the gateway answers mistakes, not speed or success rates.