Save your Proxy Rotator gateway once in the Octo Browser Proxy Manager, then attach it to any profile in a click. Residential and mobile IPs with a sticky session per profile, SOCKS5 or HTTPS, bulk import for hundreds of profiles, and the same credentials working through Octo's local API.
Sticky IP per profile SOCKS5 & HTTPS Bulk import ready
Octo is built for volume, with kernel-level fingerprinting and fast profile launches. The proxy side has to keep up.
Real home and cellular IPs from a 100M+ pool are what account-heavy work needs. Datacenter and IPv6 sit on the same plan for the jobs where speed matters more than disguise.
Give each profile its own sticky port and it keeps one consistent address across launches, so a fingerprint and its IP always tell the same story.
Octo's Proxy Manager stores proxies once and reuses them across profiles. Add the gateway a single time and attach it wherever you need it, with no retyping.
Octo supports HTTP, HTTPS, SOCKS5 and SSH, and recommends SOCKS5 over plain HTTP. Our gateway serves SOCKS5 and HTTPS, so you are on the recommended path either way.
Need IPv6? Octo takes it with the host in square brackets, and we sell IPv6 as a first-class type rather than an add-on. Good for high-volume, low-sensitivity work.
Switch a profile to the rotating endpoint for a fresh IP per connection when you are scraping rather than holding an account. See rotating proxies.
Save the gateway in the Proxy Manager once, then attach it to as many profiles as you like.
Open Proxy Gateways in your Proxy Rotator dashboard. Copy the host, the port for the proxy type and location you want, and your username and password. Each type lists a rotating port and a range of sticky ports, take a sticky port for account work.
In Octo Browser, go to the Proxies section and click Add Proxy. This saves the proxy to your list so any profile can pick it up later without re-entering credentials. Use Bulk Add instead if you are loading many at once.
Choose the protocol, then enter the host, port, login and password. Octo also accepts a single pasted line and detects the format automatically, which is quicker.
The Octo Browser Add Proxy form with Proxy Rotator gateway details.
Click Check Proxy. Octo connects through the gateway and reports the exit IP along with the ISP, connection type, location and timezone it detects. When the IP shows green, click Confirm to save it to the list.
Create or edit a profile, open its proxy setting and pick the saved entry from the Proxy Manager. Save, launch, and the browser runs on that IP. For multi-accounting, repeat with a different sticky port for every profile.
Rather than filling each field, you can paste one line and let Octo work out the format. All three of these describe the same gateway, so use whichever your notes are already in.
# Octo auto-detects each of these in the Add Proxy field. # Swap in your own host, port and credentials. socks5://USER:PASS@gateway.proxyrotator.com:8080 http://gateway.proxyrotator.com:8080:USER:PASS gateway.proxyrotator.com:8080:USER:PASS # IPv6 gateways wrap the host in square brackets [2001:db8::1]:8080:USER:PASS
For a batch, use Bulk Add and paste one proxy per line. The important detail for multi-accounting is the port: keep the host and credentials identical and change the sticky port on each line, so every line becomes an independent session holding its own IP.
# One line per profile. Same host and credentials, # a different sticky port from the range in your dashboard. gateway.proxyrotator.com:11001:USER:PASS gateway.proxyrotator.com:11002:USER:PASS gateway.proxyrotator.com:11003:USER:PASS gateway.proxyrotator.com:11004:USER:PASS gateway.proxyrotator.com:11005:USER:PASS
The Proxy Manager list shows how many profiles are using each proxy, along with the protocol, address, country and detected ISP, so you can see at a glance whether two profiles are sharing an address when they should not be.
What goes in each field of the Octo Browser proxy form.
| Octo Browser field | What to enter | Example |
|---|---|---|
| Title | Any label. Naming it after the profile keeps the list readable | Proxy Rotator - US sticky 01 |
| Protocol | SOCKS5 or HTTPS, both on the same gateway | SOCKS5 |
| Host | Your gateway hostname | gateway.proxyrotator.com |
| Port | The port for that proxy type and location | 8080 |
| Login | Your gateway username | USER |
| Password | Your gateway password | PASS |
| Protocol: HTTP | Skip it. Octo recommends SOCKS5 over plain HTTP | — |
Host, port and credentials all come from Proxy Gateways in your Proxy Rotator dashboard.
Octo runs a local HTTP server on http://localhost:58888, bound to 127.0.0.1 only, so nothing is exposed to the network. Start a profile through it and you get back a ws_endpoint to attach Playwright, Puppeteer or Selenium over the Chrome DevTools Protocol.
The proxy comes along for free. Because it is stored on the profile in the Proxy Manager, your script never handles credentials, it just starts a profile and inherits the IP.
import requests
from playwright.sync_api import sync_playwright
OCTO = "http://localhost:58888" # Octo Browser local API
PROFILE_UUID = "your-profile-uuid"
# The profile carries its Proxy Manager entry, so the browser starts
# behind your Proxy Rotator gateway. No proxy settings in code.
started = requests.post(f"{OCTO}/api/profiles/start",
json={"uuid": PROFILE_UUID, "headless": False},
timeout=120).json()
with sync_playwright() as p:
browser = p.chromium.connect_over_cdp(started["ws_endpoint"])
page = browser.contexts[0].new_page()
page.goto("https://api.ipify.org")
print("Exit IP:", page.inner_text("body"))
browser.close()
requests.post(f"{OCTO}/api/profiles/stop",
json={"uuid": PROFILE_UUID}, timeout=30)
Useful endpoints on the same local server: GET /api/profiles/active lists what is currently running with each profile's ws_endpoint and debug_port, and POST /api/profiles/force_stop clears a profile that will not close cleanly.
Octo also supports one-time profiles: disposable profiles created and launched in a single API call, then deleted automatically once stopped. Pair one with a rotating port and each run gets a fresh fingerprint and a fresh IP with nothing left behind, which is a clean pattern for bulk collection rather than account holding. Check Octo's API reference for the exact request body, since the fingerprint and proxy objects are passed inline.
When you check a proxy, Octo reports the ISP, connection type, location and timezone it detects for that IP. Read it. It is the fastest way to catch a residential IP that is really a hosting range, or a profile whose declared timezone is hours away from where its IP claims to be.
Octo notes that its geolocation database and the one used by whichever site you test against will not always agree, so an occasional flag mismatch is a database difference rather than a broken proxy. When a site's own idea of the location matters, set the language and timezone on the profile manually rather than trusting auto-detection.
This is where city-level targeting pays off. Pin the profile to a city on residential, set the matching timezone and language once, and every launch afterwards is consistent. Verify with the fingerprint checkers Octo recommends before you put a profile to work.
For anything holding an account, use sticky proxies. One IP per profile, held for the session, so the account looks like the same returning person on every launch. That is the whole point of pairing an antidetect browser with a proxy in the first place.
Use rotating proxies where a fresh IP per connection helps, such as bulk collection or availability checks driven through the API. Both modes are on the same gateway and the same plan, so switching is a port change.
The errors Octo reports, what usually causes them, and the fix.
| What Octo shows | Likely cause | Fix |
|---|---|---|
Proxy connection failed | Wrong protocol for the port, or a typo in host or port | Re-copy from Proxy Gateways, confirm SOCKS5 vs HTTPS |
Failed to get proxy data | Octo reached the proxy but could not read its details | Re-run Check Proxy, then verify with the cURL command below |
| Check Proxy fails, cURL works | IP-whitelist auth, or a local firewall blocking Octo | Switch to user:pass auth, or whitelist this machine's IP |
| Credentials rejected | Login or password mismatched, or a stray space when pasting | Paste the single-line format instead and let Octo split it |
| Country flag looks wrong | Geolocation database difference, not a proxy fault | Set language and timezone on the profile manually |
| Two profiles share an IP | Both point at the same entry, or at a rotating port | Give each profile its own sticky port and its own entry |
| IP changes between launches | Pointed at a rotating port | Switch to a sticky port from the range in your dashboard |
| IPv6 proxy fails on some sites | The target site has no IPv6 support | Use residential or datacenter IPv4 for those profiles |
Octo's own FAQ suggests testing a proxy with cURL before blaming the browser, which is exactly right. Run this from the same machine and it should print an IP that is not yours.
curl -x http://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
One plan and one set of credentials covers every tool here.
Proxy Library, bulk import and a sticky IP per profile.
View setup guideSticky IPs across the Mimic and Stealthfox engines.
View setup guidePer-profile proxies for multi-account work.
View setup guideCustom proxy per profile on the Orbita browser.
View setup guidePush any desktop app through the same gateway.
View setup guideEvery supported tool, with copy-paste setup guides.
Browse all guidesgateway.proxyrotator.com:8080:USER:PASS and Octo detects the format. Click Check Proxy, and when the IP shows green click Confirm to save it.socks5://USER:PASS@host:port, http://host:port:USER:PASS, and plain host:port:USER:PASS. IPv6 addresses go in square brackets, as [host]:port:login:password.http://localhost:58888. Start a profile through it and you get a ws_endpoint to attach Playwright, Puppeteer or Selenium over CDP. The profile applies its saved Proxy Manager entry, so the automated session uses the same IP as a manual launch.Residential, mobile, datacenter and IPv6 on one plan, with a sticky IP per profile and bulk import into the Proxy Manager. From $24.95/mo.