How to use a ProxyWing static IP with CloakBrowser
If your QA site allows traffic from one IPv4 address, start by checking the address your browser presents to an IP check page. Then close the browser and check again. This guide connects a ProxyWing static IP to CloakBrowser in Python using a dedicated ProxyWing datacenter proxy. The address to compare against is the IPv4 assigned to your order.
Quick answer: Give CloakBrowser the proxy’s HTTP address and port as server, and pass the username and password separately. Open an IP check page inside that browser. Close the browser and repeat with the same settings. Both readings should match the assigned IPv4; two identical readings alone aren’t enough.
ProxyWing is a CloakBrowser directory partner and provided proxies for evaluation.
The setup steps below follow ProxyWing’s documentation. The code was checked with CloakBrowser through a local authenticated proxy; that check did not use ProxyWing’s network.
Get the four values from ProxyWing
Start with an active Datacenter proxy and a working CloakBrowser Python installation with license access configured. Use the CloakBrowser Quick Start to check a basic browser launch before adding the proxy. ProxyWing provides the network exit; CloakBrowser opens the page through it.
In your ProxyWing dashboard, open the datacenter product card, select HTTP, and use username/password access. Under CREDENTIAL FORMAT, choose domain:port:username:password. The label says “domain,” but this product displays an IPv4 address in that position. ProxyWing’s connection format reference shows the other layouts if your fields are in a different order.
For the fictional row 192.0.2.44:8080:qa_reader:demo_only, the mapping is:
| From the ProxyWing row | Where it goes in CloakBrowser |
|---|---|
192.0.2.44 and 8080 | server: http://192.0.2.44:8080 |
qa_reader | username |
demo_only | password |
Check your ProxyWing static IP in two fresh browsers
Save the following as check_proxy.py and run python check_proxy.py in an interactive terminal in your CloakBrowser environment. Enter the four values from your row when prompted. Enter only the number at the port prompt, and use the proxy password, not your dashboard password.
The script keeps the password out of the file and uses getpass to hide terminal input. If you see GetPassWarning, stop before entering the password and use a terminal that supports hidden input.
from getpass import getpass
from ipaddress import IPv4Address
from cloakbrowser import launch
assigned = IPv4Address(input("ProxyWing IPv4: ").strip())
port = int(input("HTTP port: ").strip())
proxy = {
"server": f"http://{assigned}:{port}",
"username": input("Proxy username: "),
"password": getpass("Proxy password: "),
}
for run in (1, 2):
browser = launch(proxy=proxy)
try:
page = browser.new_page()
page.goto("https://api.ipify.org", timeout=30000)
observed = IPv4Address(page.locator("body").inner_text().strip())
verdict = "MATCH" if observed == assigned else "MISMATCH"
print(f"Run {run}: {observed} ({verdict})")
finally:
browser.close()
The script reads the address from ipify’s IPv4 text endpoint. Look for MATCH on both runs. That means the endpoint saw the assigned address on two separate browser launches. It is a short connection check; it does not establish how long the address will remain available or test other network channels.
After both runs match, repeat your QA scenario against your own site and compare its request logs. Keep the same proxy settings for that check.
What if the check fails?
The script stops at the IPv4 or port prompt. Check the input before troubleshooting the proxy connection. Enter only the assigned IPv4 at the first prompt and only the HTTP port number at the second. A blank or nonnumeric port causes ValueError before the browser launches. Restart the script and enter the values from your row.
The IP page doesn’t load. First check that the proxy is active and the port matches the HTTP service on the selected card. If the browser reports an authentication error, check the credential format: in the layout above the username comes third. Re-enter the matching password and rerun the same script. If your machine is also on ProxyWing’s IP whitelist, a successful connection alone won’t tell you whether the password was accepted.
Both runs show the same IP, but it’s the wrong one. Compare the printed address with the IPv4 on the exact order you meant to test. If you have several orders, copy all four fields from that one row and run again. Don’t add the unexpected address to your site’s allowlist just to make the check pass.
FAQ
Can I check the IP in my everyday browser or with curl?
That tells you which IP that request used. To verify your CloakBrowser job, read the result from the tab created by the job itself.
Why compare both runs with the assigned IPv4?
Two identical readings can still be the wrong exit. Each run must match the address assigned to the ProxyWing order you intended to use.
Does MATCH prove that my own site will work?
It confirms the address seen by the IP endpoint for that request. Check your own site separately: its access rules and application responses are outside this test.
Does restarting with the same proxy preserve my login?
This script opens fresh browsers and does not save cookies or login state. Reusing a proxy address and preserving a browser session are separate tasks.
Related reading: Browser automation in production: failure modes and recovery.
Next step: Set up your ProxyWing Datacenter connection and run the two-launch check above with CloakBrowser. Then use the same settings in your QA job and verify the address in your site’s logs. If you still need your first browser launch, start with the CloakBrowser Quick Start.