Troubleshooting

Diagnose and fix common issues with RaxyProxy connections.

407 Proxy Authentication Required

The proxy server rejected your credentials. Check the following:

• Correct username — copy it exactly from your Dashboard (case-sensitive)
• Correct password — no extra spaces or newline characters
• If using geo-targeting, the modifier is appended to the username with a double underscore: USERNAME__cr.us, not USERNAME_cr.us
• Package status is active — suspended packages reject connections
• Package has remaining traffic — zero-balance packages also return 407

# Quick credential check — should print your exit IP, not an error
curl -v -x http://USERNAME:PASSWORD@proxy.raxyproxy.com:823 \
     https://httpbin.org/ip 2>&1 | grep -E '< HTTP|origin'

503 / Connection Refused

The connection to the proxy server failed before authentication. Possible causes:

• Wrong port — HTTP port is 823, SOCKS5 is 824. Common mistake: using 8080 or 1080.
• Wrong hostname — the correct host is proxy.raxyproxy.com. Do not use any other hostname.
• Firewall blocking outbound — ensure ports 823 and 824 are open in your network/cloud security group.
• DNS resolution failure — try connecting by IP to confirm it's a DNS issue.

# Test TCP reachability
nc -zv proxy.raxyproxy.com 823
nc -zv proxy.raxyproxy.com 824

Connection Timeouts

Timeouts often mean the proxy connected but the target was slow or the proxy pool was under load. Try:

• Increase your HTTP client timeout to at least 30 seconds
• Retry on timeout — the next request will get a different exit IP
• Switch to a different proxy type — residential IPs may be slower than datacenter for latency-sensitive targets
• Check if the target domain itself is down

Wrong Exit Country

If https://httpbin.org/ip shows an IP from an unexpected country:

• Confirm your geo modifier uses double underscore: USERNAME__cr.us (two underscores before cr)
• Country codes are ISO 3166-1 alpha-2 lowercase: us, gb, de — not USA or United States
• Semicolons separate multiple parameters: USERNAME__cr.us;city.newyork
• If coverage is thin for your target country, the proxy pool may fall back to an available IP — try a neighbouring country or switch to a larger pool type

# Check exit country
curl -s -x "http://USERNAME__cr.us:PASSWORD@proxy.raxyproxy.com:823" \
     "https://ipapi.co/json" | python3 -m json.tool | grep country

IP Not Rotating

If you're getting the same exit IP on every request when you expect rotation:

• Check you are using the rotating port (823), not a sticky port (10000–20000) by mistake
• Remove any sessid. modifier from your username — a session ID pins the IP
• Some targets serve cached responses — test with httpbin.org/ip to isolate whether the IP is actually changing
• HTTP keep-alive can reuse a TCP connection for multiple requests — use separate connections (new sessions) to force IP rotation

Debug Commands

# 1. Confirm proxy is reachable on both ports
nc -zv proxy.raxyproxy.com 823
nc -zv proxy.raxyproxy.com 824

# 2. Test HTTP proxy + auth
curl -v -x http://USERNAME:PASSWORD@proxy.raxyproxy.com:823 https://httpbin.org/ip

# 3. Test SOCKS5
curl -v --socks5-hostname proxy.raxyproxy.com:824 \
     -U USERNAME:PASSWORD https://httpbin.org/ip

# 4. Test geo modifier (US exit)
curl -s -x "http://USERNAME__cr.us:PASSWORD@proxy.raxyproxy.com:823" https://httpbin.org/ip

# 5. Test sticky session (same IP across calls)
curl -s -x "http://USERNAME__sessid.test-1:PASSWORD@proxy.raxyproxy.com:823" https://httpbin.org/ip
curl -s -x "http://USERNAME__sessid.test-1:PASSWORD@proxy.raxyproxy.com:823" https://httpbin.org/ip

# 6. Check API balance
curl https://raxyproxy.com/api/v1/account \
     -H "Authorization: Bearer raxy_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Still stuck? Open a support ticket and include the output of the debug commands above — it helps us diagnose the issue quickly.