Troubleshooting: Start Here

Find your symptom below. Run the numbered checks in order, then follow the link for the full fix. Most connection problems are solved by the two-minute self-test in the callout. Run it first.

curl -x http://USERNAME:[email protected]:16666 https://ipinfo.io -v

Proxy won't connect at all

1. Run the self-test above. If you see Connection refused or a timeout to geo.proxio.cc:16666, your network or firewall is blocking outbound port 16666. Retest from another network (or mobile hotspot) to confirm.
2. Confirm the endpoint is exactly geo.proxio.cc:16666 and the scheme is http://. Use http:// even when your target site is HTTPS.
3. Still stuck? Work the full checklist in Connection & Authentication.

Authentication keeps failing (Error 407)

1. Re-copy your username and password from the service's Sub-users tab. No leading or trailing spaces, and keep the whole 12-character base plus any targeting segments intact.
2. Using IP-allowlist (passwordless) auth? Confirm your current public IP is still whitelisted on that credential. Dynamic IPs and CGNAT change it. Check yours with curl https://ipinfo.io/ip.
3. Confirm the credential still exists and was not rotated or reset in the dashboard.
4. Full walkthrough: Connection & Authentication and the Error 407 reference.

IP shows the wrong location

1. Check your slugs. Geo values are lowercase with everything except letters and numbers stripped: newyork, not new-york.
2. Respect the hierarchy: a city requires a state, and a state requires a country.
3. Geolocation databases disagree; verify the exit IP against more than one source before assuming targeting failed.
4. Full fix: Geo-Targeting Not Working.

Same IP won't stick, or the IP changes mid-session

1. auto rotation gives a fresh IP on every request by design. For a stable IP you need a sticky or smart session with -sessid- and -sesstime- segments.
2. Your session prefix must be letters, numbers, or underscores only. A dash corrupts parsing and silently breaks stickiness.
3. sesstime is capped at 90 minutes; after it expires the IP is released.
4. How sessions work: Session Types.

Speeds are slower than expected

1. Try another country. The distance between the exit IP and the target server adds latency you can not always avoid.
2. A tighter geo scope raises latency: pinning a specific city draws from a smaller IP pool than a whole country. Widen the scope if you do not need the precision.
3. Rule out your own network by running the self-test and comparing timing against a request sent without the proxy.

Target site blocks me or shows CAPTCHAs

1. Rotate more aggressively: switch the credential to auto (fresh IP per request), or start a new sessid.
2. Narrow your geo targeting to the region the site expects its visitors to come from.
3. Respect the target's rate limits. Spreading requests out beats getting the whole IP banned.
4. Try SOCKS5 (socks5h://) if the site fingerprints HTTP proxies.

Payment made but no balance

1. Card top-ups (Stripe) are instant. Crypto top-ups (NOWPayments) clear only after enough network confirmations. Check the transaction in your Wallet history.
2. If an order is stuck on PENDING, re-pay it from the Orders page.
3. Full billing fixes: Billing & Wallet FAQ.

Quota ran out unexpectedly

1. Check today's usage and your exact remaining quota (KB-precision) in Usage Statistics.
2. If one credential stopped working while others keep running, it may have hit its own per-credential quota cap. Check that cap in the Sub-users tab.
3. Using IP-allowlist auth? Anyone connecting from a whitelisted IP spends your data with no password. On a shared or NAT'd IP, everyone behind it can drain your quota, so review your bindings.

Go deeper