Skip to content

Cloud Phone Proxy: SOCKS5 or HTTP, Which One to Enter

Follow the app's list first, then make the type match the protocol the IP was issued with.

What each app accepts

What each app accepts
ItemAccepted typesWhat to enter on Proxy302
DuoPlusSocks5 onlyA SOCKS5 IP, port 3333
GeeLarkHTTP, HTTPS and SOCKS5The type shown for the IP: SOCKS5 on port 3333 or HTTP on 2222
Desktop Chrome and Edge, for a testHTTP and HTTPS proxies; no login for SOCKS5An HTTP IP, port 2222

Sources: DuoPlus help center, GeeLark proxy management page, Chromium network docs and Proxy302 product facts, all read on 16 November 2026.

What the two types are

An HTTP proxy receives requests from the app, and for HTTPS sites it is asked to open a tunnel with the CONNECT method and then forwards the bytes both ways. SOCKS5, defined in RFC 1928, is a lower-level relay: it supports CONNECT for TCP, BIND, and UDP ASSOCIATE for UDP, with optional username and password under RFC 1929.

For a cloud phone the practical difference is what the app lets you type: some accept only one type, and the value must match what the proxy listens for. Chrome's own notes add that its SOCKS5 carries only TCP and has no login, which matters when you test an IP in a desktop browser.

Matching the IP on Proxy302

In My assets, each per-IP lease carries one protocol and shows it as a tag; rotating residential and newly bought per-GB static residential list an HTTP line and a SOCKS5 line on the same username and password. A per-IP static or datacenter lease also answered on the other protocol's port in our tests of 4 November 2026, but a per-GB datacenter token connects only over the protocol it was bought with.

So the safe rule for cloud phones: with rotating residential use the line on port 3333 and enter SOCKS5 in the app; with a per-IP lease buy SOCKS5 and enter SOCKS5. Rotating residential needs no new credential, only a matching type and port.

Test both protocols from a terminal

# HTTP, port 2222
curl -x http://LOGIN:PASSWORD@HOST:2222 https://ipinfo.io/json

# SOCKS5, port 3333 (socks5h also resolves names through the proxy)
curl -x socks5h://LOGIN:PASSWORD@HOST:3333 https://ipinfo.io/json

Example only: replace LOGIN, PASSWORD and HOST with the values from My assets. A per-GB token answers only over its own protocol.

Choose and enter the type

  1. Step 1: Find what the app accepts

    DuoPlus: Socks5 only. GeeLark: HTTP, HTTPS or SOCKS5.

  2. Step 2: Pick the protocol when you buy

    For a per-IP lease, choose SOCKS5 in the Proxy302 order form. Rotating residential needs no choice: use the line on port 3333.

  3. Step 3: Copy the line

    In My assets click host:port:user:pass for the IP. Note the tag and the port: 3333 for SOCKS5.

  4. Step 4: Enter the same type

    In the app set Type or protocol to Socks5 (GeeLark) or paste the line under Add (DuoPlus), then run its check.

    Expected result The check shows the exit IP and country.

When the type is wrong

Check fails and the port in My assets is 2222

Check The IP is an HTTP asset, and the app wants SOCKS5.

Fix For rotating residential, switch to the line on port 3333; for a per-IP lease, buy a SOCKS5 IP; or, in GeeLark, set Type to HTTP.

Stop when DuoPlus accepts only Socks5; do not keep retrying an HTTP line there.

A rotating credential resets the connection on 3333

Check The type is set to HTTP, or the username and password differ from the ones in My assets.

Fix Set the type to SOCKS5, the port to 3333, and copy the username and password from that row in My assets.

Stop when Keep type and port paired; do not mix HTTP with port 3333.

SOCKS5 with a login fails in desktop Chrome

Check Chrome does not support SOCKS5 authentication.

Fix For a browser test use an HTTP IP, port 2222, or a tool that supports SOCKS5 login such as curl.

Stop when Keep SOCKS5 for the cloud phone app.

curl works over one protocol only

Check It is an asset with only one protocol; the console marks these HTTP only or SOCKS5 only.

Fix Use the protocol it works over, or buy another.

Stop when Open a Support ticket with the order number if a per-IP lease fails on both.

Cloud phone proxy protocol FAQ

Should I enter SOCKS5 or HTTP in DuoPlus?

SOCKS5: its help center lists Socks5 as the only supported type.

Should I enter SOCKS5 or HTTP in GeeLark?

Either works, because GeeLark accepts HTTP, HTTPS and SOCKS5; enter the one the IP was issued with.

Is SOCKS5 faster than HTTP?

We make no speed claim; the difference is which protocol the app accepts and which one the IP listens on.

Can I change an IP from HTTP to SOCKS5 in My assets?

No: there is no protocol switch there. Rotating residential needs no change, since both ports take the same username and password. A per-IP lease also connects over the other protocol's port, but for a clean setup buy SOCKS5 next time.

Does choosing SOCKS5 change what a platform allows?

No. The protocol only decides how the app talks to the proxy; the platform rules stay the same, so follow the platform's terms and complete any verification it asks for.

View all partners →

Reference links

6
  1. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site (checked 10 November 2026, read 16 November 2026): each per-IP asset is issued with one protocol, HTTP on port 2222 or SOCKS5 on port 3333; rotating residential and newly bought per-GB static residential work on both ports with the same username and password; tests of 4 November 2026: a per-IP static or datacenter lease also connects over the other protocol on its port, and a per-GB datacenter token connects only over the protocol it was bought with.

  2. DuoPlus help center: Standard proxy configuration

    Official documentation · Confirmed on:

    Read on 16 November 2026 (DuoPlus help center): only Socks5 proxies are supported; you buy Socks5 proxy IPs yourself.

  3. GeeLark: Proxy management

    Official documentation · Confirmed on:

    Read on 16 November 2026 (GeeLark proxy management page): HTTP, HTTPS and SOCKS5 are supported.

  4. Chromium: Proxy support in net

    Official documentation · Confirmed on:

    Read on 16 November 2026 (Chromium network docs): no authentication methods are supported for SOCKSv5 in Chrome; in Chrome SOCKSv5 only proxies TCP-based URL requests, not UDP.

  5. RFC 1928: SOCKS Protocol Version 5

    Official documentation · Confirmed on:

    Read on 16 November 2026 (RFC 1928): SOCKS5 defines the commands CONNECT, BIND and UDP ASSOCIATE and the authentication methods none, GSSAPI and username/password; RFC 1929 defines the username/password step.

  6. MDN: HTTP CONNECT method

    Official documentation · Confirmed on:

    Read on 16 November 2026 (MDN, HTTP CONNECT): CONNECT asks a proxy to open a tunnel to a destination server and forward data both ways, which is how HTTPS goes through an HTTP proxy.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.