Proxies for SessionBox

Where Sessionbox specifically needs this

SessionBox is not a separate browser. It is an extension that isolates sessions inside Chrome at the tab level, so profiles are much lighter than a full antidetect build and much easier to spin up.

That lightness is the trade. Tab level isolation separates cookies and storage convincingly, but every tab still leaves through the browser's own network stack. Without a per session proxy, ten isolated tabs share one address and the isolation stops at the cookie jar.

Rotating or sticky for profiles

Use a sticky port for profile work. A profile that changes IP mid session looks like a hijacked account, which is the opposite of what you want. Each sticky port holds one address for the session, so assign a different port per profile.

Rotating ports suit collection and crawling, where a new address per request is an advantage rather than a red flag.

Setting it up

SessionBox assigns a proxy per session rather than per browser profile. Open the session settings, add the gateway host and a sticky port, then supply credentials.

Because sessions are cheap to create here, it is easy to outgrow your sticky port allocation. The standard gateway provides 500 concurrent sticky ports, so track which port belongs to which session before creating them in bulk.

Where to go next

Running more than one tool against the same gateway is normal. These cover the others.

• All integration guides, setup notes for every tool we cover
• Guides and tutorials, the concepts behind the config, including when to rotate and when not to
• AdsPower setup, another antidetect browser, same one sticky IP per profile rule
• Dolphin Anty setup, another antidetect browser, same one sticky IP per profile rule
• Sticky proxies, why profile work needs a held address rather than rotation