JustProxies

Connecting

Authentication

4-min readauthentication
How credentials are issued, what they authorise, and how to keep them safe. Same auth model across all four products.

Credential format

The dashboard delivers credentials as host:port:username:password records. Each line authorises a single order — the entire bandwidth or IP allocation you bought.

example.txttext
gw.justproxies.online:8080:cust_2c4f9a:5e2d31a8b6
gw.justproxies.online:8080:cust_91e2bd:7f0a44d9c2

The host and port are stable. The username is opaque — treat it as random. The password is a high-entropy secret; rotate it through the dashboard if it leaks.

Two ways to authenticate

The proxy gateway accepts both URL-embedded credentials and a standard Proxy-Authorization: Basic header. They're equivalent; pick the one your client library prefers.

URL-embedded (curl)shell
# Embedded in the proxy URL
$ curl -x http://USER:[email protected]:8080 https://example.com
Basic auth header (curl)shell
# Header-based — useful when secrets shouldn't sit in connection strings
$ curl -x http://gw.justproxies.online:8080 \
       --proxy-user USER:PASS \
       https://example.com
Library APIs vary on which form they accept. Python requestswants the URL form; httpx takes either. Node undici's ProxyAgent accepts both. See the Python and Node guides for snippets.

Per-order scoping

Each set of credentials is bound to one order. A residential 50 GB order has its own user/pass and pulls only from your residential balance. A static IP rental has its own user/pass and only authenticates against the IPs you rented.

That means a leaked credential cannot drain another order. Treat each as a single-purpose secret.

Credential lifetime

  • Rotating products — credentials work as long as the order has remaining balance. Once the bytes are spent, the credentials stop authenticating. Place a new order; you get new credentials.
  • Static IPs — credentials work for the calendar month period you rented. They expire automatically at month-end unless you place a renewal order before expiry.

Sticky-session token

Append -session-XXXXXXXX to the username to keep the same exit IP across requests. The token is opaque — pick any 8-16 character ID. Two requests using the same token go through the same IP for as long as the session is alive (default ~10 minutes).

sticky sessionshell
# Same exit IP for the entire login flow
$ curl -x http://cust_2c4f9a-session-A1B2C3D4:[email protected]:8080 \
       https://target.com/login

Full lifecycle and tuning lives in Sticky sessions.

Static IP credentials

Static IPs ship with one credential per IP. The host and port are fixed; the username is bound to that specific IP, so authenticating with the credential always exits through the same IP.

static-ips.txttext
gw.justproxies.online:8081:static_us_142_57_31_8:c30f7e1d09
gw.justproxies.online:8081:static_us_142_57_31_9:b48ae62015
gw.justproxies.online:8081:static_de_91_204_8_42:2d091f7f8c

Rotating a leaked credential

If you suspect a credential is compromised, open the order in the dashboard and click Rotate password. The new password takes effect within a minute and the old one is invalidated. Bandwidth balance is preserved.

Rate-limited
Rotation is rate-limited per order to one event per ten minutes. Email support if you need an emergency rotation outside that window.
Found a gap, or something wrong?
A real human reads support email.