Using SOCKS5 instead of HTTP

Our proxies work with HTTP and with SOCKS5. HTTP is the usual choice, and it still reaches https websites through an encrypted tunnel. Choose SOCKS5 when your tool or bot only speaks SOCKS5.

See which protocol a proxy uses

Open the proxy in the dashboard. On its connection card, the Protocol line names the protocol and the port it uses. Your tool must use that protocol and that port.

Change the protocol on an ISP or datacenter proxy

1. Open the proxy in the dashboard.
2. On its connection card, press Change protocol, and pick the protocol you need.
3. Confirm. Anything still using the old protocol stops connecting straight away.
4. Copy the port again from the proxy's page. The port can change together with the protocol.

Test it with curl

curl -x "socks5h://USERNAME:PASSWORD@HOST:PORT" https://api.ipify.org

Use the values from the proxy's page. The socks5h:// form lets the proxy look up the website's name for you. If it prints an IP address, SOCKS5 works.

Common mistakes

• The tool saves proxies as SOCKS5 by default. Some antidetect browsers do this when you leave out the type. Write http:// or socks5:// at the start of each proxy line, so the type is clear.
• The protocol does not match. Your tool must use the protocol and the port on the Protocol line of the proxy's page.
• An old port. After a protocol change, the old port may no longer work. Copy the port again.
• A browser. For everyday browsing, HTTP is the simpler choice. Our browser setup guide uses HTTP.

If it still does not connect, see When the proxy will not connect.