How to Use Proxy Rotator

1. Create an account

Head to the pricing page and create an account. Choose a plan sized to the concurrency you need. There is one unified plan that includes every proxy type and both rotating and sticky modes at the same price, from $24.95/mo with metered bandwidth, so you are not picking a type at checkout, only your scale. Once your plan is active, your gateway is provisioned and ready.

2. Get your gateway host, port and credentials

Open your dashboard. There you will find your gateway host, the port, and your authentication details. The host is gateway.proxyrotator.com and the port is 8080. Your dashboard also shows the username and password to use for authentication, or lets you whitelist a server IP instead. Keep these handy; every client you connect uses the same values.

host: gateway.proxyrotator.com
port: 8080
auth: USER:PASS   (or whitelist your server IP in the dashboard)

3. Connect a client to the gateway

Point any HTTP client at the gateway over HTTPS or SOCKS5. There is no plain-HTTP node; connections are encrypted. The two snippets below send a request through the gateway and print the exit IP. Run either one and you are live.

curl -x https://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
# prints the exit IP your request came from

import requests

proxies = {
    "http":  "https://USER:PASS@gateway.proxyrotator.com:8080",
    "https": "https://USER:PASS@gateway.proxyrotator.com:8080",
}
r = requests.get("https://api.ipify.org", proxies=proxies, timeout=20)
print(r.text)   # the exit IP

Prefer SOCKS5? Swap the scheme to socks5h:// in the proxy URL (install requests[socks] for the Python client). The host, port and credentials stay the same.

4. Choose rotating or sticky

Decide how the gateway should hand out IPs. In rotating mode you get a new IP on every request, which is what you want for high-volume crawling and broad data collection. In sticky mode the gateway holds the same IP for a session, which suits logins, carts and any multi-step flow that must stay on one address. You select the mode in your dashboard, and the gateway behaves accordingly when you send traffic through the same endpoint. If you are unsure which to use, read what is a rotating proxy.

curl -x https://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
curl -x https://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
# in rotating mode, the two lines print different IPs

5. Target a proxy type and location

Pick which proxy type you want, residential, datacenter, mobile or IPv6, and the country or city you want to appear from. You set both the type and the geo in your dashboard, and the gateway routes your requests through matching exits. You do not append query parameters to URLs to do this; geo and type are configured in the dashboard and applied at the gateway, so your client code does not change. With 195+ countries available, you can match the target to the right type and location without switching providers or plans.

6. Authenticate via user:pass or IP whitelist

You have two ways to authenticate, both managed in the dashboard. The first is username and password (Basic auth), which is what the USER:PASS@ part of the proxy URL carries. The second is an IP whitelist: add your server IP in the dashboard, and requests from that IP are trusted with no credentials in the URL. Whitelisting is handy for servers with a stable IP because it keeps secrets out of your code.

# after whitelisting your server IP in the dashboard:
curl -x https://gateway.proxyrotator.com:8080 https://api.ipify.org

7. Troubleshoot common issues

If a request fails, work through the usual suspects. A 407 Proxy Authentication Required means the credentials are missing or wrong, or the request is coming from an IP that is not whitelisted; double-check the username, password and whitelist in your dashboard. A connection refused or timeout usually points at the scheme or port: confirm you are using gateway.proxyrotator.com on port 8080 over HTTPS or SOCKS5, not plain HTTP. If a specific target keeps blocking you, try a higher-trust type like residential or mobile, or switch to sticky mode for stateful flows, both from the dashboard. If a SOCKS5 request fails to resolve hostnames, use socks5h:// so the proxy resolves DNS instead of your client.