Browsers
ClonBrowser with a ProxyGuys proxy
ClonBrowser is a multi-profile browser with automation built in, so one routine can be repeated across many profiles. Whatever a profile does, by hand or by a scripted task, leaves through the proxy set on that profile. Give it a ProxyGuys proxy and that traffic comes from a US mobile IP on 4G and 5G networks.
The first half of this page puts the proxy on a profile. The second half covers what matters most for automation: getting a new IP between runs, without opening the dashboard every time.
Before starting
- ClonBrowser installed, with an account. It is available from the ClonBrowser website.
- A ProxyGuys proxy that has been started. New proxies sit at "Pending · starts on activation" until you press Start proxy; changing the IP only works after that.
- For the code route only: an API key. On the API page press Create key and store the key straight away, because it is shown once.
1. Note the proxy details
In My Proxies the proxy has two connection lines, "HTTP proxy" and "SOCKS5 proxy". They share a host but use different ports. For ClonBrowser, use SOCKS5 with its port. HTTP also works, provided the type you choose and the port you enter belong together.
Under Credentials, Copy username and Copy password put the login on your clipboard exactly as it is. The password is masked on screen; you never need to enter your account password to get it.
2. Put the proxy on a profile
Press New Browser to create a browser profile, or open an existing one to edit it.
In the profile's Proxy section, add a new proxy (New).
Choose socks5 as the protocol. Enter the host (the numeric IP shown on the proxy), the SOCKS5 port, the username and the password. ClonBrowser can also fill these in from one pasted line with Parse: the ⋮ → Details line, host:port:username:password, already carries the SOCKS5 port.
Press Connect Test. Once it passes, save the proxy, finish the profile with Create Browser, and open it from the browser list with Launch.
In the new window, open httpbin.org/ip. The "origin" value should be the proxy's mobile IP.
3. A fresh IP between runs
A change keeps the same city and carrier, usually takes 30 to 90 seconds, and can be requested once every 60 seconds. Build your runs around that: ask for the change, wait, then start the next pass.
Without code: the change-IP link
On the proxy, ⋮ → Copy change-IP link gives a URL that changes the IP when it is opened. It replies "OK — rotating your IP now. Allow up to ~90 seconds for the new IP." No login or API key is needed, which also means anyone holding the link can rotate your proxy: keep it as private as a password. If it leaks, ⋮ → New change-IP link replaces it and the old one stops working.
Anything that can open a URL can fire it: a bookmark, a scheduler, or a step at the end of a script. Then allow about 90 seconds before the next run loads its first page.
With code: the API
The rotate call answers once the change has happened and returns new_ip, which may be null. Replace pp123456 with the proxy's API id from GET /proxies; the id is not the login.
export PROXYGUYS_API_KEY="YOUR_API_KEY"
# URL-encode the password here if it contains special characters.
export PROXY_URL="socks5h://USERNAME:PASSWORD@HOST:SOCKS5_PORT"
# 1. Ask for a new IP. The call returns once the change is done.
# A 409 with "code": "cooldown" means: wait retry_after seconds, then try again.
curl -s -X POST \
-H "Authorization: Bearer $PROXYGUYS_API_KEY" \
https://proxyguys.com/api/v1/proxies/pp123456/rotate
# 2. See which address the proxy leaves from now.
curl -s -x "$PROXY_URL" "https://api.ipify.org?format=json"On a timer instead
If runs don't need to line up with IP changes, use the proxy's Rotation column: set IP rotation ("Same city & carrier") to Every 5 min, Every 10 min, Every 30 min or Hourly. The first change comes one interval after saving and it keeps going with the dashboard closed. Leave it on No rotation for tasks that sign in, because a timed change can land partway through a signed-in flow.
Troubleshooting
- Connect Test fails instantly. Type and port don't match: SOCKS5 needs the port from the "SOCKS5 proxy" line, HTTP the one from "HTTP proxy".
- It worked yesterday, now the login fails. If the password was changed with New password, every profile using the proxy needs the new one.
- The API answers 409. Too soon after the last change. Wait the retry_after seconds it returns.
- The API answers 401. The key is missing, mistyped or revoked. Create a new one on the API page if needed.
More on changing IPs is in the IP rotation guide, and the same proxy from Python is covered in the Python requests guide.