Troubleshooting Octo Browser and a mobile proxy
A red Unavailable notification
Start with the port, because HTTP and SOCKS5 are separate logins with separate ports on a Private plan and crossing them fails every time. Re-copy the username and password one at a time, since a trailing space breaks authentication silently. Then run the curl check above: a US carrier result from curl means the credentials are good and the problem is in Octo.
The proxy works but Octo will not pass it
This one has a documented answer that is easy to miss. Their docs say that if a proxy is in fact functioning but does not pass the test, you should change your own internet connection, because your ISP may be blocking the proxy checker URL. They suggest mobile internet or a VPN, which gives you a different ISP. So a failing check on a proxy that curl reaches is often about your network, not ours.
No UDP icon appears
Expected. JesusProxy SOCKS5 is TCP only, so UDP is not supported and the icon will not show on a perfectly good proxy. If something inside the profile genuinely needs UDP, it will not travel through the proxy at all, and no setting in Octo changes that.
The country is a US state you did not pick
Normal. Our coverage is the United States only, on T-Mobile and Verizon, in Connecticut, Georgia, Maryland, New Jersey, New York, Pennsylvania and Virginia, and there is no city targeting. Another country means the profile is not using the proxy, so re-read our IP lookup inside the profile window rather than in your normal browser.
The Proxy Manager shows something I do not recognise
The list can display advanced information per proxy including IP, ISP, connection type, network fingerprint, location and timezone. Their docs name those columns without defining all of them, so treat the ones you recognise as the useful ones: ISP and location are what you want to match against a US carrier.
Credentials ended up somewhere they should not
Worth knowing because it is easy to do by accident: Copy Proxy puts the whole connection on your clipboard as protocol://login:password@host:port, password included. Treat anything you paste out of Octo as a secret, and rotate the username and password from your dashboard if it went somewhere public.