Troubleshooting AdsPower and a mobile proxy
Connection test failed
Work through it in this order. Check the port belongs to the protocol in Proxy type, since that is the most common mistake with a plan that has both. Re-copy the username and password one at a time, because a trailing space is enough to break authentication. Then run the curl check above: a US carrier IP from curl proves the credentials and points the problem at the AdsPower profile instead.
The settings will not save
AdsPower's docs ask you to close the profile before changing its settings. If a field refuses to stick, close the profile window and edit it from the three-dot menu in the profile list.
The proxy works but the location looks wrong
Read our IP lookup inside the profile first and see what it actually reports. Our coverage is the United States only, on T-Mobile and Verizon, in Connecticut, Georgia, Maryland, New Jersey, New York, Pennsylvania and Virginia, so a US state you did not expect is normal and another country is not. There is no city targeting.
If the IP is right but a site still shows somewhere else, the cause is usually something in the profile reporting a location independently of the IP rather than the proxy itself. Check the profile's own fingerprint and language settings against the IP before you blame the connection.
Several profiles changed IP at once
That is the documented behaviour of a shared proxy, not a fault: refreshing the change-IP link moves the IP for every profile using it. If those profiles are meant to be separate identities, give each one its own plan.
The IP repeats after rotating
In normal use every rotation gives you a fresh IP. Repeats are only possible with very heavy rotation, roughly 1,000 or more IPs a day. If you are rotating that hard and need strict uniqueness, slow down or spread the work across more plans.