Each mobile proxy is its own endpoint: a host and two ports that belong to your device, not a shared gateway name. This page explains each field and how to choose between HTTP and SOCKS5.
What the dashboard shows
| Field | What it is |
|---|---|
| Host | The address your client connects to. |
| HTTP port | Accepts HTTP proxy requests, including CONNECT tunnels for https:// websites. |
| SOCKS5 port | Accepts SOCKS5 connections with a username and password. |
| Username and password | The device's proxy credentials. |
| Outgoing IP | The carrier IP websites see. It changes when the device rotates. |
Some devices list the HTTP and SOCKS5 endpoints separately, each with its own host and login.
HTTP or SOCKS5
| HTTP port | SOCKS5 port | |
|---|---|---|
| Proxy URL | http://USERNAME:PASSWORD@HOST:HTTP_PORT | socks5h://USERNAME:PASSWORD@HOST:SOCKS5_PORT |
https:// websites | Tunnelled with CONNECT | Tunnelled |
| Errors from the proxy | HTTP status codes such as 407 or 502 | SOCKS replies or a closed connection |
| Browsers with a login | Playwright and Puppeteer | Chromium does not send SOCKS credentials |
| Libraries | curl, Requests, HTTPX, aiohttp, Node.js, Scrapy, Go | curl; Requests and HTTPX with their SOCKS extras |
Start with the HTTP port unless your tool only speaks SOCKS5. HTTP vs SOCKS5 proxies compares the two in more detail.
Use socks5h for SOCKS5
With socks5h:// the proxy resolves the website's hostname, so the DNS lookup also leaves from the mobile network. With socks5:// most clients resolve the name on your machine first and send only the IP address, which exposes the lookup to your own resolver. socks5 vs socks5h shows the difference across six clients.
Check the connection
Request an IP echo service through the proxy and compare the result with the outgoing IP in your dashboard:
curl -sS -x "http://USERNAME:PASSWORD@HOST:HTTP_PORT" https://api.ipify.orgCommon mistakes
- An
https://proxy URL on the HTTP port makes the client start TLS with the proxy, which fails withSSL: WRONG_VERSION_NUMBER. Usehttp://for the proxy. See SSL WRONG_VERSION_NUMBER behind a proxy. - An HTTP client pointed at the SOCKS5 port gets no status at all, for example
curl: (56) Proxy CONNECT aborted. Check the port. See Tunnel connection failed: 502. - A leftover
HTTPS_PROXYorNO_PROXYvariable can send traffic somewhere else or around the proxy. See Proxy environment variables.