Connecting to residential
How the gateway, username and password work for residential, with a test request, SOCKS5 notes and fixes if it will not connect.
Updated 2 min read
A residential proxy is one gateway address plus one username and password. Point your client at the gateway and the pool picks the exit.
Get the values
- Open Proxies > Residential in the side menu and click the proxy.
- On the Connection card, copy the Gateway, the Username and the Password.
- Note the Protocol line: it names the protocol and the port to use.
Make a test request
curl -x http://HOST:PORT -U "USERNAME:PASSWORD" https://api.ipify.org
Put the gateway's host and the port from the Protocol line in place of HOST:PORT; this command is for a proxy whose Protocol line says HTTP, and the SOCKS5 one is below. The reply is the exit IP a site would see.
The Integration examples card on the same page has this request ready in cURL, Python, Node.js, PHP, Go, Java and C#, and Setup guides for browsers, languages and tools covers specific clients.
A list of proxy strings
Some tools want a list of proxies rather than one. If the proxy page shows Generate proxy strings, click Open generator, set the Quantity and the Format your tool expects, then Copy list or Download list. Every line uses the same gateway and credentials.
SOCKS5
If the Protocol line says SOCKS5, use a socks5h:// proxy URL so the target's host name is resolved on the proxy side:
curl -x "socks5h://USERNAME:PASSWORD@HOST:PORT" https://api.ipify.org
Where the proxy offers more than one protocol, Change protocol on the Connection card switches it.
If it does not connect
- If the Connection card says there is no gateway to show for the proxy, write to support@proxyhive.io with the proxy's ID.
- A
407means the proxy did not accept how you authenticated: see Connecting with a username and password. - Check the proxy still has bandwidth on its Capacity card; requests stop when it runs out.
- Then work through A proxy stopped working: tell us from the dashboard.