/ GUIDES / SOCKS5
Connect with SOCKS5. Check the small details.
You need four values from an active proxy: host, port, username and password. Copy them from your dashboard or export them through the API. The addresses below are examples; replace them with your own credentials.
Test a connection with curl
curl --proxy socks5h://203.0.113.10:1080 \
--proxy-user 'YOUR_USERNAME:YOUR_PASSWORD' \
https://example.com/socks5h tells curl to resolve the destination hostname through the proxy. With socks5, curl resolves it locally. Keep proxy passwords out of shell history and shared logs; for recurring jobs use a protected curl config or your application's secret storage.
Use Firefox with SOCKS5
In Firefox, open Settings → General → Network Settings → Settings. Choose Manual proxy configuration, enter the host and port in SOCKS Host, and select SOCKS v5. Enable Proxy DNS when using SOCKS v5 if you want DNS resolved through the proxy. Firefox prompts for the username and password when needed.
Read the export format
username:password@host:port
host:port:username:passwordDifferent tools expect different field orders. The dashboard copies username:password@host:port; the API also provides format=ipport. Choose SOCKS5 in your tool. HTTP proxy mode is a different protocol and will not work with a SOCKS5-only endpoint.
If a request fails
An authentication error usually means a mistyped username or password, or a lease that has expired. A timeout can come from the proxy, your connection or the destination. Test a second destination and check the proxy status before changing your code. A 403 or CAPTCHA from one website does not by itself mean the proxy is offline.
After an automatic replacement
Refresh your proxy list or export. A replacement keeps your permanent SOCKS5 login and original expiry. Its IP and port may change. Scripts should read replacement_of from the API and reload the connection details rather than storing the first IP forever.