# GeeLark Proxy Setup: Add, Check and Fix > GeeLark proxy setup step by step: Custom proxy on a cloud phone, HTTP or SOCKS5, Check proxy, one sticky IP per phone, bulk changes and a fix for each failure. [Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/GeeLark Proxy Setup: Add, Check and Fix # How to set up a proxy in GeeLark: cloud phones, bulk changes and fixes ProxiesOct 23, 2026·13 min read·By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData Setting up a proxy on a GeeLark cloud phone in four steps: generate a sticky line in the QuanticData endpoint generator, enter it under Proxy settings with Custom selected and HTTP on port 8080 or SOCKS5 on port 1080, click Check proxy for the exit IP, country and city, then create the phone with its location based on the IP; the card lists the three things to verify when the check fails. On this page [What you need before you start](/blog/geelark-proxy-setup/#what-you-need-before-you-start) [The proxy formats GeeLark accepts](/blog/geelark-proxy-setup/#the-proxy-formats-geelark-accepts) [Step by step: add a proxy to a GeeLark cloud phone](/blog/geelark-proxy-setup/#step-by-step-add-a-proxy-to-a-geelark-cloud-phone) [One sticky session per cloud phone](/blog/geelark-proxy-setup/#one-sticky-session-per-cloud-phone) [Residential Premium, ISP and mobile proxies in GeeLark](/blog/geelark-proxy-setup/#residential-premium-isp-and-mobile-proxies-in-geelark) [Adding and changing proxies for many cloud phones](/blog/geelark-proxy-setup/#adding-and-changing-proxies-for-many-cloud-phones) [A new IP without touching anything else](/blog/geelark-proxy-setup/#a-new-ip-without-touching-anything-else) [GeeLark proxy connection failed: errors and fixes](/blog/geelark-proxy-setup/#geelark-proxy-connection-failed-errors-and-fixes) [HTTP or SOCKS5 in GeeLark](/blog/geelark-proxy-setup/#http-or-socks5-in-geelark) [Before you run accounts](/blog/geelark-proxy-setup/#before-you-run-accounts) To add a proxy in GeeLark, open New profile, choose Custom under Proxy settings, pick HTTP or Socks5 to match the port, enter host, port, username and password, click Check proxy and create the cloud phone. Give every phone its own sticky session. Below: each step, Residential Premium, ISP and mobile lines, bulk changes and a fix for each failed check. GeeLark runs Android phones in the cloud, and each cloud phone profile keeps its own apps, its own device identity and, once you add one, its own proxy. The proxy decides which IP address, which country and which network the apps on that phone show to TikTok, Instagram or any other platform. With Location and Language set to Based on IP, the phone also takes its location and its language from the proxy. The field names below are the ones in GeeLark's own help center and app; the values come from the QuanticData endpoint generator. ## What you need before you start - **A GeeLark account** with the desktop app or the web console open on Profiles. The same New profile page also creates browser profiles (the laptop icon at the top); this guide follows the cloud phone. - **A proxy plan.** Residential Premium, ISP or mobile: all of them work in GeeLark. The table further down says which one fits which phone. - **The four values:** host, port, username and password. In the QuanticData dashboard they are under My proxies, on the plan's page, in the Endpoint generator, and Connection details lists them one by one. - **Username and password authentication.** A cloud phone runs on GeeLark's servers, so the proxy sees GeeLark's address, not your own. An IP whitelist made for your office or home IP would not match; the login travels with the phone wherever it runs. **Try it on your own targets.** Every QuanticData account gets $2 of free API usage per month. [Start free — $2/month included](https://quanticdata.io/signup/?utm_source=blog&utm_medium=website&utm_campaign=blog-inline&utm_content=geelark-proxy-setup)[Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/) ## The proxy formats GeeLark accepts GeeLark takes three proxy types, HTTP, HTTPS and Socks5, and nothing else. How you enter the proxy depends on where: - **New profile, Custom:** separate fields. Host and port on one line next to the Check proxy button, then Username and Password below. - **Proxies, Add proxy:** one line, `host:port:username:password`; with Socks5 the full form starts with the type, `socks5://host:port:username:password`. - **Proxies, Bulk add:** one proxy per line, up to 100 at once, as `type://host:port:username:password` or `type://username:password@host:port`. A change-IP link and a remark can follow in brackets and braces. The same QuanticData proxy in each layout: ``` # New profile, Custom: four fields Host residentialpremium.quantumproxies.io Port 8080 Username USER-country-mx-sid-p01-ttl-60m Password PASS # Add proxy or Bulk add, HTTP on port 8080 residentialpremium.quantumproxies.io:8080:USER-country-mx-sid-p01-ttl-60m:PASS # Bulk add, Socks5 on its own port socks5://residentialpremium.quantumproxies.io:1080:USER-country-mx-sid-p01-ttl-60m:PASS ``` The username is the whole string, with everything after the first dash: `-country-mx` picks the exit country, `-sid-p01` names the session and `-ttl-60m` keeps it for 60 minutes. Copy it whole. A username cut at the first dash still logs in, but the phone then leaves from a random country on a new IP at every request. ## Step by step: add a proxy to a GeeLark cloud phone Step 1 in the QuanticData dashboard: country, sticky session and protocol give the values to enter in GeeLark. 1. **Generate the values.** In the QuanticData dashboard open My proxies, then your plan. In the Endpoint generator choose the Country (and a Region or City if the phone needs one), set Session to Sticky, set Session TTL (minutes) to at least the time the phone stays on, and choose the Protocol. Open Connection details: host, port, username and password, each with a copy button. 2. **Open New profile in GeeLark.** In Profiles click New Profile, keep the phone icon and Single selected, and give the profile a name, a group or tags if you use them. 3. **Choose Custom under Proxy settings.** Saved, the other choice for your own proxies, picks one you stored before on the Proxies page. 4. **Pick the Type that matches the port.** HTTP for port 8080, Socks5 for port 1080. Leave IP query channel on IP2Location: it only chooses the database that places the IP on the map. 5. **Enter host and port, then username and password.** Host `residentialpremium.quantumproxies.io`, port 8080, the whole username with `-country-mx-sid-p01-ttl-60m` and the password. 6. **Click Check proxy.** Under the field GeeLark shows Proxy info: country or region, state or province, city, the exit IP and the ISP. The country has to match the `-country-` in the username. 7. **Leave Change IP URL empty and Auto refresh off.** With QuanticData a new IP comes from a new session ID in the username, explained further down. 8. **Finish the phone and create it.** Choose the Android version and the charging method; under Advanced settings keep Location on Based on IP and set Language to Based on IP, so both follow the proxy's country. Click Create. Steps 3 to 8 in GeeLark, redrawn with our values: the result under the field is a real check of a QuanticData Mexico line on 23 October 2026, Santiago de Querétaro, Querétaro, time zone America/Mexico_City. GeeLark's own advice for long-term accounts is to set the proxy, the location and the language before the first login, and to avoid changing the network setup once the account is active. Do the check before you install or sign in to anything. ## One sticky session per cloud phone A cloud phone is meant to look like one handset on one connection. A rotating proxy changes IP on every request, which suits public data collection and breaks an account that stays logged in. A sticky session keeps one IP for as long as the session lives, and the session lives in the username, so the proxy never has to be edited once the phone is created. ``` # phone 1: Mexico, one session for a working day residentialpremium.quantumproxies.io:8080:USER-country-mx-sid-p01-ttl-480m:PASS # phone 2: same plan, its own session (never reuse p01) residentialpremium.quantumproxies.io:8080:USER-country-mx-sid-p02-ttl-480m:PASS # phone 3: Mexico, on all day residentialpremium.quantumproxies.io:8080:USER-country-mx-sid-p03-ttl-1440m:PASS ``` Three rules cover almost every case: - **A different session ID on every phone.** Two phones on the same line leave from one IP, which is exactly what separate cloud phones are there to avoid. The Number of cloud phones column on the Proxies page shows when one proxy is used by more than one phone. - **A lifetime longer than the work.** The generator accepts up to 1440 minutes, a full day. When the session ends, the next request gets a new IP, and a platform can see that as a new login location. - **The country in the username.** Without `-country-` the exit can be anywhere, and a phone set to Based on IP takes whatever location it lands on. With Session set to Sticky, the generator makes as many lines as the Quantity field says, ten by default, each with its own session ID, and Copy all or Download takes them out in the same format. One line per phone. One line per cloud phone: every generated line has its own session ID. ## Residential Premium, ISP and mobile proxies in GeeLark | Proxy type | In GeeLark | Good for | | --- | --- | --- | | Residential Premium | Custom or Bulk add; one sticky line per phone; country, region, city or ISP in the username; username and password only | Most cloud phones: home IPs in the country you choose | | ISP | Fixed IPs listed under Assigned IPs as IP:Port:Username:Password; Bulk add takes the list as it is; one IP per phone | Long-lived accounts that should keep the same address for months | | Mobile | One sticky line per phone with -type-mobile in the username; Global, USA, EU or Asia gateway; HTTP 8080 or SOCKS5 1080 | Phone-first platforms and accounts tied to carrier networks | ### Residential Premium The line from the steps above. Targeting goes in the username: Country, then Region and City, or Country and ISP, all chosen in the generator. For a market like Mexico, start from the country and add a region only when the account really belongs there; the plan pages for [Mexico residential proxies](https://quanticdata.io/proxies/mexico/) and [QuanticData residential proxies](https://quanticdata.io/residential-proxies/) list what each network covers. ### ISP proxies An ISP plan gives fixed addresses instead of sessions. Open the plan's Assigned IPs, choose the format IP:Port:Username:Password and paste the list into Bulk add with the matching Type; every IP becomes one saved proxy, ready to be picked with Saved when you create a phone. ISP IPs are static by design, so there is no session ID and no TTL: one IP per phone, for as long as the plan runs. More on the product: [ISP proxies](https://quanticdata.io/isp-proxies/). ### Mobile proxies Mobile lines work like Residential Premium, with `-type-mobile` in the username and a gateway to choose: Global, USA, EU or Asia. On a cloud phone that runs TikTok or Instagram they are the closest match to a real handset on a carrier network; see [mobile proxies for TikTok](https://quanticdata.io/mobile-proxies/for/tiktok/) and for [Instagram](https://quanticdata.io/mobile-proxies/for/instagram/), or [Mexico mobile proxies](https://quanticdata.io/mobile-proxies/mexico/) for the market in this guide. ``` # mobile, Mexico, sticky for an hour mobile.quantumproxies.io:8080:USER-country-mx-type-mobile-sid-m01-ttl-60m:PASS ``` Mobile: gateway, sticky session, HTTP 8080 or SOCKS5 1080. Keep username and password on cloud phones. Mobile plans also offer an IP whitelist, but on GeeLark keep username and password: the phone connects from GeeLark's servers, not from the IP you would whitelist. ## Adding and changing proxies for many cloud phones 1. **Make the lines.** In the generator set Session to Sticky and the quantity you need, generate, then Copy all or Download. 2. **Bulk add them in GeeLark.** Open Proxies, click Add proxy and choose Bulk add. Set the Type (HTTP for 8080, Socks5 for 1080), a Proxy group such as Mexico, keep IP query channel on IP2Location and paste the lines, one per line, up to 100 at a time. GeeLark splits each line into host, port, username and password in the table below; Import from spreadsheet takes them from a file instead. 3. **Check them before saving.** Click Check proxy: the Export IP column shows the exit IP, the country or region, the city and the time of the check. Click OK to save. GeeLark skips duplicates, so every line needs its own session ID. 4. **Assign them.** New phones: Proxy settings, Saved, then the proxy group and the proxy. Phones you already have: select them in Profiles, open the three-dot menu in the toolbar and choose Change proxy. Change proxy opens the Edit proxy window. Same proxy gives one proxy to every selected phone, which only makes sense for internal tests. Different proxies gives each phone its own: with Custom you enter one line per phone, with Random from saved GeeLark takes a different saved proxy from the group you choose for each phone. Three cloud phones moved to their own mobile session in one window. Redrawn screen with our values. ## A new IP without touching anything else GeeLark's Change IP URL field and its Auto refresh switch are meant for providers that change the IP through a link. With QuanticData Residential Premium and mobile leave both empty: the IP is tied to the session ID in the username, so a new session ID, for example `-sid-p02` instead of `-sid-p01`, is a new IP, and the old line keeps working until its lifetime ends. To move one phone, stop it (GeeLark edits a profile while it is closed), open its three-dot menu, choose Change proxy, enter the new line, run Check proxy and save. Keep the new IP in the same country, ideally the same city, as the old one. ISP proxies are static addresses: one IP per phone, for months. ## GeeLark proxy connection failed: errors and fixes When Check proxy does not get through, there is no Proxy info to read: no exit IP, no country, no city. GeeLark's API documentation names this result "Proxy detection failed". These are the cases behind it, in the order to check. A failed check and the order of the fixes. Redrawn screen; the message follows the wording of GeeLark's API documentation. | What you see | Usual cause | Fix | | --- | --- | --- | | Check proxy fails, no Proxy info | The type does not match the port: Socks5 on 8080 or HTTP on 1080 | HTTP with 8080, Socks5 with 1080 | | The same failure, with the right type | The username was cut, the whole line was pasted into Host, or a space came with the paste | Copy the four values again from Connection details, one per field | | The check worked yesterday, fails today | The plan expired or its traffic is used up | Check the plan in My proxies: status, remaining traffic, expiry date | | Proxy info shows the wrong country or city | No `-country-` in the username, or Worldwide chosen in the generator | Generate the line with a country; if only the city looks off, try the other IP query channel, IP-API, which uses a different database | | The IP changes while the phone is running | The session lifetime ended, or two phones share one session ID | A longer `-ttl-` and a different `-sid-` on every phone | | Bulk add saves fewer proxies than you pasted | GeeLark drops duplicates | Give every line its own session ID | | Proxy is not supported | GeeLark does not accept proxies whose server or exit IP is in mainland China | Choose another country in the generator | One test outside GeeLark settles most cases in a minute. If this returns an address in Mexico, the proxy works and the problem is in the profile's fields: ``` curl -x http://residentialpremium.quantumproxies.io:8080 \ -U "USER-country-mx-sid-test-ttl-10m:PASS" https://ipinfo.io/json ``` Our own run of this test on 23 October 2026 came back from Santiago de Querétaro, in the state of Querétaro, with the time zone America/Mexico_City; that is the result drawn in the New profile screen above. ## HTTP or SOCKS5 in GeeLark Both work on a cloud phone, and every QuanticData network offers both. HTTP on port 8080 is the simpler choice and the one to start with; it already carries HTTPS sites through the CONNECT method, so the HTTPS type in GeeLark's list is not needed. Socks5 on port 1080 passes any kind of connection, not only web traffic, which matters for apps on the phone that do not speak HTTP; the details are on the page for [SOCKS5 proxies](https://quanticdata.io/socks5-proxies/). What breaks a phone is never the choice itself, only a type that does not match its port. Why every profile needs its own address, in a cloud phone or in a browser, is explained in [residential proxies for antidetect browsers](https://quanticdata.io/residential-proxies/for/antidetect-browsers/); the mobile plans are on the page for [QuanticData mobile proxies](https://quanticdata.io/mobile-proxies/). ## Before you run accounts A proxy changes where a phone's traffic comes from, not what the account is allowed to do. Keep to each platform's terms and to the law where you work, and use one phone, one session and one identity per account. ### Sources & further reading - [GeeLark help center: Profiles (create a cloud phone profile, proxy settings, Check Proxy)](https://help.geelark.com/profiles-create) - [GeeLark help center: Proxies (Add Proxy, proxy details, IP query channel, check and save)](https://help.geelark.com/proxies-en) - [GeeLark blog: How to Use Proxies with Cloud Phones for Social Media (Bulk add, Change proxy)](https://www.geelark.com/blog/cloud-phone-proxy/) - [GeeLark: proxy management (bulk import, supported protocols)](https://www.geelark.com/features/proxy-management/) - [GeeLark OpenAPI documentation: proxy management and error codes](https://github.com/GeeLark/geelark-openapi) - [RFC 1928: SOCKS Protocol Version 5](https://www.rfc-editor.org/rfc/rfc1928) - [RFC 9110: HTTP Semantics, the CONNECT method](https://www.rfc-editor.org/rfc/rfc9110#name-connect) ## FAQ Quick answers on geelark proxy. [Something else? Ask us](mailto:hello@quanticdata.io) ### How do I add a proxy in GeeLark? Open Profiles, click New Profile and, under Proxy settings, choose Custom. Pick the Type that matches the port (HTTP for 8080, Socks5 for 1080 on QuanticData), enter host and port, then username and password, click Check proxy and create the phone. To store proxies first, open Proxies and use Add proxy or Bulk add, then pick them with Saved. ### What proxy format does GeeLark use? In a new profile the proxy goes into separate fields: host, port, username, password. On the Proxies page one line per proxy works: host:port:username:password, or with the type first, such as socks5://host:port:username:password. Bulk add also accepts type://username:password@host:port and takes up to 100 lines at once. GeeLark supports HTTP, HTTPS and Socks5 only. ### Why does the GeeLark proxy check fail? The check could not get through the proxy. The usual causes are a type that does not match the port, a username cut or pasted with a space, the whole line pasted into the Host field, or a plan that expired or ran out of traffic. Test the same values with curl outside GeeLark: if curl answers from the right country, fix the profile's fields; if it fails, check the plan. ### Can I use mobile proxies on GeeLark cloud phones? Yes. A mobile line goes in like any other: host mobile.quantumproxies.io, HTTP on 8080 or Socks5 on 1080, and a username with -type-mobile and a sticky session ID. Use username and password rather than an IP whitelist, because the cloud phone connects from GeeLark's servers, not from your own IP. ### Can several GeeLark cloud phones share one proxy? They can, but they should not: phones on the same sticky line leave from the same IP, which links their accounts. Give every phone its own session ID. The QuanticData generator makes many sticky lines at once, ten by default, and GeeLark's Change proxy with Different proxies assigns one per phone in a single step. ### How do I change the proxy of an existing GeeLark profile? Stop the cloud phone, open its three-dot menu in Profiles and choose Change proxy. Enter a new Custom proxy or pick a Saved one, click Check proxy and save. For several phones, select them, open the three-dot menu in the toolbar, choose Change proxy and use Different proxies so each phone gets its own. ## One sticky IP for every GeeLark cloud phone Residential Premium, ISP and mobile proxies with country targeting and sticky sessions up to 1440 minutes, HTTP and SOCKS5, copied straight from the endpoint generator into GeeLark. [Start free — $2/month included](https://quanticdata.io/signup/?utm_source=blog&utm_medium=website&utm_campaign=blog-end&utm_content=geelark-proxy-setup)[Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/) ## Related reading [Proxies Octo Browser Proxy Setup: Add, Check and Fix Open the profile, click Proxy / VPN, choose Add a new proxy / VPN, paste the whole line into the host field, match HTTP or SOCKS5 to the port, run Connection check and confirm. Below: every step with the exact field names, one sticky session per profile, Residential Premium, ISP and mobile lines, Bulk Add and a fix for each error Octo Browser shows. Read more](https://quanticdata.io/blog/octo-browser-proxy-setup/) [Proxies Kameleo Proxy Setup: Add, Test and Fix Open the profile, set Proxy to With Proxy, pick HTTP for port 8080 or SOCKS5 for port 1080, paste the line as user:pass@host:port, click Test Proxy, then Save & Start. Below: every step with the exact field names, one sticky session per profile, Residential Premium, ISP and mobile lines, the local API and a fix for each error Kameleo shows. Read more](https://quanticdata.io/blog/kameleo-proxy-setup/) [Proxies VMLogin Proxy Setup: Add, Test and Fix Click Setting proxy server in the profile, turn on Enable proxy server, pick HTTP Proxy for 8080 or Socks 5 Proxy for 1080, Paste proxy info, Test Proxy and save. Below: every field, the Test Proxy result, one sticky session per profile, Residential Premium, ISP and mobile lines, the batch TXT format and a fix for each VMLogin message. Read more](https://quanticdata.io/blog/vmlogin-proxy-setup/) --- Source: https://quanticdata.io/blog/geelark-proxy-setup/ · Site index for AI: https://quanticdata.io/llms.txt