Troubleshooting GeeLark and a mobile proxy
Check Proxy fails when saving the proxy
Check the port against the type you selected, because HTTP and SOCKS5 are separate logins with separate ports on a Private plan. Re-copy the username and password one at a time, since a trailing space breaks authentication silently. Then run the curl check above from your own machine: a US carrier result proves the credentials and moves the problem into GeeLark.
The phone has no internet at all
The whole device is behind the proxy, so a bad proxy looks like a broken phone rather than one failing app. Re-check the saved proxy entry first, and bear in mind that a plan which has run out of days will fail exactly this way.
The proxy expired and I do not want to lose the phone
You do not have to. Their guide says to use the three-dot menu on the profile and choose Change proxy, then enter a custom proxy or select a saved one and check it. Apps, logins and files stay put. Keeping the new proxy close to the old one, ideally the same country, is their advice and ours.
Several phones changed IP together
They are sharing one plan. Check the Number of cloud phones column on the proxy: a Private plan is one SIM, so everything pointed at it rotates as a group. Separate identities need separate plans.
The location is a US state I did not pick
Expected. We cover the United States only, on T-Mobile and Verizon, in Connecticut, Georgia, Maryland, New Jersey, New York, Pennsylvania and Virginia, with no city targeting. Another country means the phone is not using the proxy, so read our IP lookup on the phone to see what it really has.
GeeLark reports a country but I want the carrier
Their IP query channel setting only identifies the country or region of the proxy IP, and their docs say the default is usually sufficient. It is not meant to tell you the network owner, so use our lookup on the phone for that.