Authentication

Where to find your mobile proxy username and password, how to pass them in a proxy URL, and how to keep them out of code and logs.

All docs pages

Every ipvolt mobile proxy has its own username and password. You send them to the proxy, never to the website you visit. This page shows the formats clients accept and how to keep the credentials out of your code.

Where to find the credentials

In the dashboard, open the device and select Show connection details. Most devices use one username and password for both protocols, on two ports. Some list a separate host, port, username and password for HTTP and for SOCKS5; use the set that belongs to the protocol you connect with.

The proxy URL

Most clients take the proxy as one URL:

code
http://USERNAME:PASSWORD@HOST:HTTP_PORT
socks5h://USERNAME:PASSWORD@HOST:SOCKS5_PORT

The scheme describes how your client talks to the proxy, not to the website. Use http:// for the HTTP port even when the website is https://: the client asks the proxy for a tunnel, and the TLS session with the website runs inside it. If the username or password contains characters such as @, :, / or %, percent-encode them in the URL, or use your client's separate username and password fields.

How the credentials travel

On the HTTP port, clients send a Proxy-Authorization: Basic header to the proxy, either with each plain HTTP request or once with the CONNECT request that opens a tunnel. On the SOCKS5 port, they use the username and password method of the SOCKS5 handshake. In both cases the website never receives them.

Keep them out of code

Store the proxy URL in an environment variable or your secret manager and read it at runtime:

sh
export PROXY_URL="http://USERNAME:PASSWORD@HOST:HTTP_PORT"

Do not commit it, print it or paste it into error reports. When you share logs with support, remove the password and keep the host, the port and the error.

Dashboard sign-in is separate

The email code or wallet you sign in with only opens the dashboard. Proxy credentials cannot sign in to the dashboard, and your dashboard sign-in cannot authenticate proxy traffic.

When authentication fails

A wrong or missing password makes the proxy answer 407 Proxy Authentication Required. Fix proxy error 407 shows the symptom in each client and the order of checks.

Plug in your first proxy.

Mobile from $9 a day. Residential from $2.40 per GB, opening soon.