GeeLark proxy setup
Copy one line from Proxy302, paste it into GeeLark's Bulk add, check it, and give each cloud phone its own IP.
When the proxy check fails in GeeLark, check the type, the line format and expiry first, then compare the exit IP and location the check shows.
On the Proxies page, or in the proxy settings when you create a profile, you click Check proxy (older versions call it 检查代理) and instead of an exit IP and a location the check does not pass.
Do not swap the proxy yet. The six checks below start with the most common; check again after each change and stop at the first one that fixes it. GeeLark's help pages do not say which network the check runs from, so this page does not guess and lists only the steps they state.
Where to look: click Proxies in the left menu, click Add proxy, go to Bulk add and look at the Type drop-down; or, when creating a profile, choose Custom in the proxy settings and look at Proxy type. GeeLark supports HTTP, HTTPS and SOCKS5.
What to change: the type must match the protocol the provider gave you. In Proxy302 My assets every IP has an HTTP or SOCKS5 tag; an IP has only the protocol chosen at purchase and there is no switch, so the wrong type will not connect.
Where to look: in Bulk add, each proxy takes one line, in GeeLark's format type://host:port:account:password, for example socks5://100.200.200.100:30000:AD000004:30000000002. After you paste, GeeLark parses host, port, username and password and shows them in the list below.
What to change: compare each parsed value with My assets before you click Check proxy. Typical slips are a missing digit in the port, account and password swapped, or a space at the end of the line. Up to 100 proxies go in at once and duplicates are filtered out; Change IP URL is optional, so leave it empty unless your provider gave you one.
When a check passes, the Export IP column shows the exit IP, country or region, city and check time. When it does not, GeeLark's guide says to verify that the details were entered correctly.
If you use GeeLark's OpenAPI, a response with detectStatus false carries the reason in its message field; the endpoint accepts only IP-API or IP2Location as the query channel and only socks5, http or https as the type.
A pass only says the proxy connects. Whether the location is right is check 5.
GeeLark advises checking proxies that have sat unused for a while before you assign them to new cloud phones: a bulk check catches expired proxies, incorrect login details and unexpected location changes.
Where to look: in the Proxies list select the entry and click Check proxy; at the same time log in to Proxy302 and open My assets for the IP's end date, or the traffic left on rotating residential.
What to change: renew or generate again if it has expired, then update the entry in GeeLark. If the IP is within its term but will not connect, open a Support ticket with the order number and we reissue it.
Where to look: after a pass, read the country or region and the city in the Export IP column; they should match the account's target market. GeeLark shows country and ISP using the IP2Location and ip-api databases.
What to change: compare this country with the country of the IP in My assets. If they differ, check once more; if they still differ, open a ticket with the order number and do not assign the proxy to a profile yet.
Where to look: when you create a profile, the proxy settings offer Custom and Saved; Saved picks one of the proxies you imported. In the Proxies list the Number of cloud phones column, and its view icon, show which profiles use a proxy.
What to change: to switch an existing profile, click the three-dot menu in the cloud phone list, choose Change proxy, enter the new proxy and save once the check passes; the apps, logins and files on the phone are kept, so there is no need to create a new profile. Keep the new proxy close to the old one, at least in the same country. GeeLark also advises setting proxy, location and language before the first login of a long-term account, and trying not to change the network setup once it is in use.
To tell whether the proxy itself is down or the details in GeeLark are wrong, test it from a terminal on your own computer. Replace the capitalised placeholders with the values from My assets.
curl -x http://USERNAME:PASSWORD@HOST:PORT https://ipinfo.io/json
# SOCKS5 (DNS is also resolved through the proxy)
curl -x socks5h://USERNAME:PASSWORD@HOST:PORT https://ipinfo.io/jsonExample only: replace the placeholders with your own. Use the first line for an HTTP IP and the second for a SOCKS5 IP.
A JSON answer with the exit IP, country and provider means the proxy works, so the problem is most likely the type or format in GeeLark (checks 1 and 2). A timeout or refusal sends you back to check 4; the proxy connection guide goes further. A 407 means the account or password is wrong. If the command works but GeeLark's check still fails, tell GeeLark support exactly that.
On GeeLark's Proxies page every proxy that passed has an Export IP column with the exit IP, country or region, city and check time. Select several proxies and click Check proxy to refresh them together.
Compare that IP with the Proxy302 IP; they should be the same. More ways to verify are in the guide on checking an IP's location.
GeeLark does not provide proxies. A Proxy302 IP goes into GeeLark at the level of host, port, account and password. The full illustrated steps are on the GeeLark proxy setup page.
Log in to Proxy302, open the IP in My assets, note its protocol tag and copy host, port, username and password, or click host:port:user:pass to copy the whole line.
In GeeLark click Proxies, then Add proxy, then Bulk add; set Type to the same protocol as in Proxy302, pick a proxy group and paste the line.
Check that the host, port, username and password parsed into the list are right, click Check proxy, and click OK to save once it passes.
When you create or edit a profile, choose Saved in the proxy settings and pick this proxy, or choose Custom and fill in type, host, port, username and password, and check it again.
Check that the type matches the IP's protocol, then that the host, port, username and password parsed after Bulk add match My assets. When a test fails, verifying the entered details is GeeLark's own advice.
GeeLark supports both; follow the IP's own protocol. Each Proxy302 IP has only the protocol chosen at purchase, and the tag is shown in My assets.
No. GeeLark's quick start guide says you choose your own proxy service; its partner page lists some providers.
GeeLark says accounts on different phones that connect through the same proxy share one network exit. In Change proxy for several profiles, the Same proxy option is mainly for internal testing and usually not a fit for long-term accounts; Different proxies gives each phone its own.
No. Use the three-dot menu in the cloud phone list and choose Change proxy; the apps, logins and files are kept. Keep the new proxy close to the old location.
GeeLark says a proxy is only part of an account's environment: account history, login changes, device changes or a sudden change of location can all trigger verification. A working proxy mainly gives a consistent network identity and makes connection problems easier to trace. An IP does not change any platform's rules, so use accounts the way the platform itself allows.
Official documentation · Confirmed on:
Read on 2 November 2026: bulk add up to 100 proxies, HTTP, HTTPS and SOCKS5, duplicates filtered on import; IP2Location and ip-api databases used to show the exit country and ISP.
Official documentation · Confirmed on:
Read on 2 November 2026 (English page, and the Chinese edition at /zh/blog-zh/cloud-phone-proxy-zh/): import steps (Proxies, Add proxy, Bulk add, type, group, one proxy per line, Check proxy, OK); what a check shows; re-check saved proxies before assigning them; Custom or Saved in a profile's proxy settings; Change proxy on a profile; a shared proxy means a shared network exit; a working proxy does not prevent every verification prompt.
Official documentation · Confirmed on:
Read on 2 November 2026: GeeLark does not provide proxies; bulk line format type://host:port:account:password; the check button; if the test fails, verify the details entered. The page is dated 2024, so button names may differ slightly in newer versions (this page calls it 检测代理 / 检查代理).
Official documentation · Confirmed on:
Read on 2 November 2026: the proxy check endpoint takes proxyQueryChannel (IP-API or IP2Location), proxyType (socks5, http, https), server, port and optional username and password, and returns detectStatus, a failure message, the exit IP, country, subdivision, city, time zone and ISP. The page does not say which network the check runs from.
Product observation · Confirmed on:
Product facts file of the site (checked 18 October 2026): HTTP or SOCKS5 is chosen at purchase and each IP asset carries one protocol; HTTP on port 2222, SOCKS5 on port 3333; a failed asset is reissued after a Support ticket with the order number.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.