Browser environments
Choose SOCKS5 when creating or editing an environment, then enter host, port, username, and password separately. Keep connection assignment clear for each account group.
STATIC ACCESS / SETUP GUIDE
Four fields.
One clear workflow.
If you already have a host, port, username, and password, this guide helps you add the SOCKS5 connection to a compatible browser, desktop client, mobile client, or script.
01ProtocolSOCKS5
02AuthenticationUSER + PASS
03VerifyEXIT MARKET
04If blockedSUPPORT
STEP ONE / READ THE FIELDS
Start with the four connection fields.
Do not treat the example values as a real connection. Your actual credentials appear only in your account delivery details. Avoid extra spaces or line breaks when copying.
EXAMPLE FORMAT
host:port:user:password
A common full format is 203.0.113.10:1080:username:password. It can also be represented as socks5://username:password@203.0.113.10:1080.
HOSTSERVER / IP
PORT1–65535
USERNAMEAUTH USER
PASSWORDAUTH SECRET
STEP TWO / CHOOSE A CLIENT
Enter each field in a compatible client.
Interfaces change between tools and versions, but the core fields remain the same. Use only clients you trust and install them from their official source.
Desktop clients
Add a new SOCKS profile, save it, set it as the active connection, and enable system proxy routing only when needed.
Mobile clients
Add SOCKS5 manually in a compatible client, confirm the operating system VPN permission, then enable it. Do not mix untrusted profiles.
Code and CLI
Pass the proxy address and authentication to a SOCKS5-compatible library or command. Never commit real passwords to source control.
Tip: if the client accepts only a single URI, use the free 518Proxy credential converter. Conversion runs locally in your browser.
STEP THREE / VERIFY THE CONNECTION
Connected is not the same as verified.
Before using the connection in a long-running workflow, confirm authentication, exit market, baseline reachability, and the account or purpose assigned to it.
Enable the profile
Make sure the profile you just added is selected and the client is enabled.
Check authentication
If authentication fails immediately, copy the username and password again and check for extra spaces.
Confirm the exit market
Use a trusted IP lookup or the 518Proxy checker to confirm the exit country matches the purchased market.
Record the assignment
Label the connection with its market, account group, or expiry date to prevent accidental sharing across team workflows.
STEP FOUR / TROUBLESHOOT
Rule out the common issues first.
Is the host or IP complete?
Is the port a valid number?
Do the credentials contain spaces?
Is the protocol set to SOCKS5?
Is the correct profile active?
Does the device have internet access?
Is another VPN or proxy conflicting?
Does the exit match the purchased market?
Is the service term still active?
STILL NOT CONNECTING?
Bring the error details to support.
Share the device, client, target market, error message, and checks already completed. Do not post the full password in public chat; site support will guide you through a safe verification flow.