Troubleshooting GoLogin and a mobile proxy
GoLogin publishes an ordered troubleshooting routine, and it is a good one. The steps below follow theirs, with the JesusProxy-specific answer added where it applies.
Read the full error first
Hover the red or yellow icon next to the proxy field. Their docs note that GoLogin expands the error on hover and that the expanded text often says exactly what failed, which beats guessing.
Prove the proxy outside GoLogin
Their step two is to test the proxy independently. Use the curl command above against our own IP check: a US carrier result means the credentials are good and the fault is in GoLogin, and a failure means fix the login first. Their list of usual causes is worth checking against: an incorrect IP, port, username or password, a proxy that is not responding, or a blocked or expired proxy.
The IP field refuses the string
That field takes the address only. Paste full ip:port:login:password lines into the Proxy & Location column instead, which their docs describe as adding the proxy with all its details.
Proxy doesn't work, with a Quick fix button
Click Not now if you want to stay on your own IP. Quick fix swaps in a GoLogin proxy from the same country, which gets the profile running but means your account is now being seen from a different network than you planned, and their docs note it consumes your GoLogin proxy traffic.
Right IP, wrong location on the site
Set Geolocation in the profile to Blocked, or to coordinates matching the proxy. This is their documented fix for sites that read the browser Geolocation API rather than the IP, and it is a profile setting rather than anything to do with the proxy.
Wrong US state
Expected within limits. 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. A different one of those states is normal; another country means the profile is not using the proxy at all, so re-read our IP lookup inside the profile.
Still stuck
Their remaining steps are to switch network, try the same profile on the web version at app.gologin.com, and update the desktop app. If a profile works on the web version but not on the desktop one, their docs read that as a local environment problem rather than a proxy problem, which also means it is not something we can fix from our side.