GeeLark proxy setup
Save gateway lines under Proxies in GeeLark and give each cloud phone its own sticky line: mobile for a phone on a cellular network, residential for one on Wi-Fi.
- Protocols
- HTTP, HTTPS and Socks5, with username and password
- UDP
- Not mentioned in GeeLark's help or release notes
- Where the setting is
- Proxies → Add proxy, or Proxy settings in New profile
- Line format
host:port:username:password, one per line, up to 100 at once- Works with
- Mobile and residential proxies
Before you start
- The GeeLark client installed and signed in.
- A proxy login and password from the Mobile or Residential page of the dashboard, with traffic on that product (without it the gateway answers 402).
- A clear purpose for each phone profile: your own accounts, clients' accounts you manage with their access, or app QA and testing, within each platform's rules.
- Host
gate.aeonproxy.com- Port (HTTP / HTTPS)
7000- Port (SOCKS5)
7001- Login
- your proxy login, with targeting keys if you need them:
LOGIN-cc-us-sid-abc123 - Password
- your proxy password
Copy the login and password from the Residential or Mobile page of the dashboard; the generator there also writes ready lines. Key syntax: targeting and sessions.
Mobile or residential for a cloud phone
Under Advanced settings, a GeeLark phone has a Network setting: Wi-Fi or Cellular network. A phone on a cellular network gets its IP from a mobile carrier, so pair it with our mobile login; -car- picks the carrier (lists for the US, the UK and Germany so far). A phone on Wi-Fi sits behind a home connection, which a residential login matches, with -isp- for the provider. The login decides the pool; host and ports stay the same.
Add the proxy
- In GeeLark, open Proxies, click Add proxy, and pick the Type (HTTP for port 7000, Socks5 for port 7001) and a Proxy group.
- Paste the lines in
host:port:username:passwordorder, one per line, up to 100 at a time:gate.aeonproxy.com:7000:LOGIN:PASSWORD. For Socks5, GeeLark's help writes the full line asSOCKS5://gate.aeonproxy.com:7001:LOGIN:PASSWORD. - Click Check proxy: each line shows its exit IP and location under Export IP. Click OK to save.
- Open Profiles and click New profile. Under Proxy settings, choose Saved and select the line (or Custom to enter one there), then click Check proxy.
- Under Device information, pick the Charging method and the system Version, then click Create.
With Custom, the form also shows Change IP URL and Auto refresh. Leave the URL empty and the switch off: our lines change IP through the session key in the login, not through a link.
Check the proxy
Check proxy shows whether the connection works, the IP with its country, state, city and ISP, and a note on whether the IP has been used before. The IP query channel decides which location database places the IP; the default is usually fine.
Leave Location under Advanced settings on Based on IP, so the phone's location follows the proxy. To see what apps see, open a browser on the cloud phone and load aeonproxy.com/ip-checker.
Rotating or sticky
Give every phone profile a sticky line. A rotating login takes a new IP on every connection, which a signed-in app notices. Use one -sid- key per phone and keep its targeting:
gate.aeonproxy.com:7000:LOGIN-cc-gb-car-three-sid-phone01-ttl-60:PASSWORD
gate.aeonproxy.com:7000:LOGIN-cc-gb-car-three-sid-phone02-ttl-60:PASSWORDA sticky IP lasts at most 60 minutes (-ttl-60); then the line takes a new IP from the same country and carrier. There is no way to keep one mobile or residential IP for days. In the dashboard generator, set Session to Sticky (same IP) and Session time to 60 min; it writes up to 500 lines at once, and GeeLark takes 100 per Add proxy.
If it does not work
| What you see | What to check |
|---|---|
| Check proxy fails with 407 | The login, the password, or a value outside the lists, such as a carrier name not on the Mobile page. |
407 with -car- outside the US, UK or Germany | Carrier lists exist for those three countries so far. Drop the -car- key. |
| 402 | No traffic left on that product, or the sub-user reached its limit. |
| The check hangs on port 7000 | Type is HTTPS. Set it to HTTP. |
| The IP changes inside an app session | The line has no -sid- key, or its sticky time ran out. |
| GeeLark and the IP checker show different cities | Location databases differ. Try another IP query channel. |
| 502 | The exit failed. Retry: a rotating line takes another exit, a sticky one keeps its key. |
Questions
GeeLark's help does not say. Our SOCKS5 port 7001 relays UDP, but whether the phone sends UDP into the proxy is up to GeeLark. Check for leaks with the IP checker on the phone.
No. A sticky IP lasts up to 60 minutes; then the same line takes a new IP from the same country and carrier.