Rotate an account's egress proxy
Change which network path a connected account's browser session uses, without breaking the live session.
Goal
Move a connected account onto a different egress (proxy) without forcing a full reconnect.
Two different actions, not one
The egress dialog offers two distinct operations, and they are not interchangeable:
- Change egress — switch the account to a different proxy binding. This is a single call.
- Change address — ask the current proxy provider to rotate the exit IP
behind the same
host:port. This is two calls in a fixed order: the provider rotation happens first, then TEASE bumps an internal generation counter. The order matters because rotation changes the real exit IP without changinghost:port— every lock in the system compareshost:port, so skipping the generation bump would leave a browser tab believing it's still on the old connection while the engine has already moved to the new address.
Partial failure is reported, not hidden
If the provider rotation succeeds but the generation bump fails, TEASE tells you directly that the address changed but the tab hasn't caught up — it does not stay silent about a state that has drifted.
Steps
- Open the account's egress dialog from its card.
- Pick change egress to move to a different proxy, or change address to rotate the IP behind the current one.
- Wait for confirmation before assuming the account is on the new path.
How to verify it worked
The dialog reports success explicitly. For a rotation, a reported success means both the provider call and the generation bump completed — a partial failure is surfaced as its own state, not folded into "success."
If it doesn't work
If a rotation reports the drifted-state warning (address changed, tab not caught up), treat the account as needing a fresh check rather than assuming it recovered on its own — reconnect if the account subsequently shows as lost.
What's next
If the account still shows disconnected after a proxy change, see Reconnect a lost account.