🔐
Common Issue2025 Updated

Fix Proxy Authentication Errors

Resolve 407 Proxy Authentication Required errors, invalid credential issues, and login failures. Step-by-step solutions for all platforms.

Read the code in the 407 body

The Proxies.sx Pool Gateway starts every 407 body with a code and ends it with a request id. Four codes share the 407 status, and only one of them means the password is wrong.

  • E_AUTH_REQUIRED: no credentials reached the gateway. Check where your client takes proxy credentials.
  • E_AUTH_INVALID: the username or password was rejected. Use the proxy password from the dashboard or a pak_ key, never the dashboard login password.
  • E_BALANCE_EXHAUSTED: the password was accepted, but the account has no traffic left.
  • E_CAP_EXCEEDED: a pak_ key reached the traffic cap its owner set.

The gateway error code reference shows how to read the body, and the username format guide covers the routing part of the username.

⚡

Quick Check

1. Username Format

Must be exactly as shown in dashboard

2. Special Characters

URL-encode: @ → %40, # → %23

3. Active Subscription

Check bandwidth/port expiry

🚫

407 Proxy Authentication Required

The proxy server requires authentication but either no credentials were provided, or the provided credentials were rejected.

Solutions

1

Verify Credentials in Dashboard

  1. aLog in to client.proxies.sx
  2. bGo to "My Proxies" → Select your port
  3. cCopy the exact username and password (use copy button)
2

Check URL Encoding

If your password contains special characters, they must be URL-encoded:

# Wrong (special characters break the URL)
http://user:p@ss#123@proxy-host.com:8080
# Correct (URL-encoded)
http://user:p%40ss%23123@proxy-host.com:8080
CharacterEncoded
@%40
#%23
:%3A
/%2F
?%3F
&%26
3

Check Account Status

📊
Bandwidth Balance

Ensure you have remaining GB

📅
Port Expiry

Check if port subscription is active

🔒
IP Whitelist

If using IP auth, verify your current IP