Evomi sessions in CloakBrowser: keep working or keep the IP?
Your browser job opens the first page successfully. Before the next step, the residential exit becomes unavailable. Should the job continue through another IP, or stop so you can investigate? That decision matters more than simply selecting a setting called “sticky session.”
Quick answer: Choose Evomi’s session when an IP replacement is acceptable, consider hardsession when holding the address longer is the priority, and use lockedsession when a failed request is preferable to replacing a disconnected exit. Pass the chosen mode in the full proxy password to CloakBrowser.
Evomi is a CloakBrowser ecosystem partner.
Choose the failure you can accept
Evomi’s residential session reference distinguishes three policies. The task examples below are ways to apply those documented differences.
| Mode | Documented behavior and a suitable task |
|---|---|
session | May replace the IP to keep requests working. Consider it for independent checks of your own pages when a changed exit does not invalidate the result. |
hardsession | Prioritizes keeping the IP for as long as possible. Consider it when continuity is useful, but do not treat it as a promise never to replace the exit. |
lockedsession | Does not substitute another IP when the bound peer disconnects; the request fails. Consider it for a QA sequence where an unnoticed IP change would invalidate later steps. |
For example, checking whether ten unrelated pages on your site render correctly may tolerate an exit change. A test of how your application handles several actions from one IP needs a different failure policy: stop and review the sequence if that assumption breaks.
Decide what the job may retry before adding automatic recovery. Keep its session ID when a retry is intended to continue the same run.
Live check of the example
On November 12, 2026, we ran the example below against Evomi Core Residential on Windows with CloakBrowser Python 0.7.0 and Chromium 156. Each of the three HTTP configurations returned two matching IPv4 readings. The SOCKS5 session variant also returned a matching pair. In a separate 65-second observation for each mode, three browser readings kept the same IP. Separate connection-level controls without a session parameter returned four different IPs across four fresh HTTP proxy connections. With lifetime-1 and an unchanged session ID, fresh connections saw one IP at approximately 0 and 26 seconds, then a different IP at 76 and 96 seconds. These live checks cover connection and short-session behavior; the peer-disconnection policies and idle tunnel settings follow Evomi’s documentation.
Carry the decision into the password
If you need a proxy account, get started with Evomi. In Evomi’s Proxy Generator, select your residential product and HTTP connection. Keep the complete generated password, including any existing location settings. Evomi’s examples put the session parameters in this password field, not in the username.
These fictional endings show the three choices. BASE_PASSWORD stands for your actual proxy password; the alphanumeric IDs below are examples. Use one mode per configuration rather than stacking the rows together.
| Chosen mode | Password illustration |
|---|---|
session | BASE_PASSWORD_session-job123ab_lifetime-10 |
hardsession | BASE_PASSWORD_hardsession-job456cd |
lockedsession | BASE_PASSWORD_lockedsession-job789ef |
Evomi requires session IDs of 6 to 10 alphanumeric characters. Keep the same ID for the whole job.
lifetime sets how long a session lasts: 30 minutes by default, up to 1,440 minutes. After it expires, Evomi assigns a new IP. It applies only to session; leave it out of hardsession and lockedsession. Keep the value within this documented range.
Keep the ID and targeting settings consistent throughout a job. Evomi retains the established IP when location or ISP settings change while the same session is kept. To select an exit with new targeting, start a new session.
Without a session, hardsession or lockedsession parameter, Evomi rotates the IP for each proxy request. A browser can reuse an existing connection, so check the behavior of the actual browser workflow rather than assuming every page resource opens a fresh proxy connection.
For the example below, use the residential HTTP endpoint http://rp.evomi.com:1000. The destination may still be HTTPS. You need active Evomi residential traffic, Python and configured CloakBrowser license access. Install the wrapper with python -m pip install cloakbrowser and follow the CloakBrowser Quick Start for your first browser launch. If you need license access, get a free key.
Evomi also provides SOCKS5 on port 1002. To use it with the same username and complete password, change the example’s server value to socks5://rp.evomi.com:1002. We verified this alternative with the session configuration.
If your browser presents a Windows profile, Evomi Core Residential can also pick an exit running Windows: append _device-windows to the password, for example BASE_PASSWORD_session-job123ab_device-windows. It combines with location and session settings. See Evomi’s device filter documentation for availability and bandwidth cost.
Observe one configuration in CloakBrowser
Save this as check_evomi.py and run python check_evomi.py in an interactive terminal. Paste the complete password for the mode you selected. Hidden input must be available. The same script accepts any of the three password formats; it does not choose or switch modes for you.
import warnings
from getpass import GetPassWarning, getpass
from ipaddress import IPv4Address
from cloakbrowser import launch
warnings.simplefilter("error", GetPassWarning)
username = input("Evomi proxy username: ").strip()
password = getpass("Complete Evomi proxy password, including session settings: ")
if not username or not password:
raise ValueError("Both proxy credentials are required.")
browser = launch(proxy={
"server": "http://rp.evomi.com:1000",
"username": username,
"password": password,
})
try:
page = browser.new_page()
readings = []
for check in (1, 2):
page.goto(f"https://api.ipify.org?check={check}", timeout=30000)
observed = IPv4Address(page.locator("body").inner_text().strip())
readings.append(observed)
print(f"Check {check}: {observed}")
print("Same exit in these checks:", readings[0] == readings[1])
finally:
browser.close()
The script checks the browser’s public IP twice using ipify, a service that returns the caller’s IP address. Matching results show that these two requests used the same exit IP. They do not prove how long it will stay unchanged or what happens if the proxy disconnects.
Use the reading to choose the next step
Both readings match
The endpoint saw the same exit for both requests. Keep that session ID for the rest of the job and use the password parameters to identify the selected mode.
The second reading has a different IP
Check the complete password, session ID and elapsed lifetime. With session, an expired lifetime or a replacement exit can explain the change.
If a lockedsession sequence changes IP unexpectedly, stop the sequence and inspect its configuration and retries before continuing. Reusing a different ID starts a new session.
The request fails instead of returning an IP
Check proxy authorization, available traffic and destination reachability first. A proxy-side 407 points to authentication. If you use lifetime, keep it within the documented limit of 1,440 minutes. The browser may show a connection error instead of exposing the proxy’s status code. With valid access, a disconnected bound peer is the documented lockedsession failure case. The script also rejects a response that is not an IPv4 address.
For a job that must retain one exit, do not silently remove the session suffix, change the ID or switch modes to make the next request pass. If you deliberately start a new configuration, repeat the IP check and restart any QA sequence that depended on the previous address. When a change is acceptable, your recovery logic can instead handle the interrupted work according to your application’s rules.
Keep tunnel timeout separate from IP lifetime
Evomi Core Residential has an idle tunnel timeout: by default, a TCP tunnel closes after 45 seconds without data in either direction. This is separate from how long a session keeps its exit IP.
For a workflow that leaves a connection idle longer, append _maxtimeout-120 to the proxy password to allow 120 seconds. The documented range is 5-300 seconds, and the setting applies to HTTP CONNECT and SOCKS5 TCP connections. Including _maxtimeout adds a 1.2x bandwidth multiplier, so use it when the workflow needs it. A browser may reopen a closed connection automatically; a later successful navigation alone does not measure this timeout.
Apply the choice to the real job
Repeat the relevant actions on your own QA site and inspect the IP recorded in its request logs. Keep browser state separate from proxy state: this script starts a fresh browser and does not preserve cookies or logins.
The useful outcome is an explicit rule for the job: whether an IP change is acceptable, what stops the sequence, and when a retry becomes a new run. Use the CloakBrowser Quick Start for the basic browser launch, and the production recovery guide to plan what happens after an interruption.
Ready to use Evomi with CloakBrowser? Get started with Evomi, choose the session mode that fits your job, and run the browser IP check above before starting your workflow.
Disclosure: This article may contain referral links. CloakBrowser may earn a commission if you make a purchase through them.