Skip to main content
All CollectionsNew Dashboard Guides
Building sticky sessions connection
Building sticky sessions connection

Set up sticky sessions to maintain the same IP across multiple requests for stable and efficient proxy connections

Kate avatar
Written by Kate
Updated over 2 months ago

Note: This article is relevant only for users of the new dashboard.

If you use the older dashboard version, please refer to the article here for the applicable instructions.

Sticky sessions overview

Sticky sessions allow you to maintain the same IP address for multiple requests over a specified period. This helps ensure more stable and efficient proxy sessions by reducing node resets and offering smoother operations.

SOAX provides proxy access through a single endpoint: proxy.soax.com:5000


Quick setup of sticky sessions

Most of the necessary fields are already pre-filled in the dashboard, so you only need to make a few selections to complete your setup. Follow these steps:

  1. Target location
    The target country may already be set, but if you want to change it, simply choose a new location from the dropdown menu.
    Example: United States (pre-selected)

    • Deep Target Levels: If you need more granular targeting, you can enable "Deep targets levels" to specify a region, city, or ISP.

      • Region: Choose the desired region within the country (optional).

      • City: If you need to target a specific city, select it from the dropdown menu (optional).

      • ISP: You can also target a particular ISP to ensure more precise connections (optional).

      If you don’t need deep targeting, leave these fields as "Any" to allow random selection.

  2. Session length
    You can choose to keep the same IP for up to 5 minutes (default), or you can set a different session length by selecting from the dropdown.
    Example: Same IP up to 5 minutes (pre-selected)

    The maximum session length is 60 minutes.
    If you prefer to get a new IP with every request, check the "New IP on each request" option.

  3. Session ID prefix
    This field allows you to define a unique session ID prefix—a random string that creates a session, ensuring the same IP is used for multiple requests. You can enter any random string here, which will be used as the identifier for that session.
    Example: rand123456

  4. Bind IP (Optional)
    The "Bind IP" option determines how your IP address is managed if it goes offline:

    • Empty state (unchecked): The IP will refresh after the selected period, and if it goes offline earlier, you will be immediately reconnected with a new one.

    • Filled state (checked): The IP will only refresh after the selected period, even if it goes offline earlier. This ensures that the same IP is maintained for the entire session (Sticky IP mode).

  5. Login and Password
    The Login and Password fields are automatically generated based on the inputs above. The credentials are ready for use, so you don’t need to enter them manually.

  6. Server and Port
    These fields are pre-configured for your connection:

    • Server: proxy.soax.com

    • Port: 5000


Easily copy your connection details

You can get the necessary connection details directly from the SOAX dashboard in the following formats:

  • cURL Request: A pre-built cURL command that you can copy and paste into your software for quick setup.

    curl -k -x package-<your_package_id>-country-us-sessionid-number06-sessionlength-300:<your_package_login>@proxy.soax.com:5000 -L https://checker.soax.com/api/ipinfo
  • Credentials: This section provides the login, password, server, and port details needed for your connection.

  • URL: You can also retrieve the connection URL to input directly into your software.

    package-<your_package_id>-country-us-sessionid-number06-sessionlength-300:<your_package_login>@proxy.soax.com:5000

Additional notes on sticky sessions

  • Force IP change: To get a new IP, simply modify the sessionid.

  • Parallel sessions: You can start multiple parallel connections by using different sessionid values for each session.

  • Session timeout: The session will expire after 60 seconds of inactivity. To keep the session active, send a keep-alive request every 30 seconds.

  • Geo-targeting:

    • For different geo-targeting (e.g., switching countries, cities, or ISPs), use a different sessionid.

    • Use %20 instead of spaces when targeting multi-word locations (e.g., new%20york).

More helpful articles on session strings and their capabilities


Need Help?
If you have any questions or need assistance, feel free to reach out to our support team via live chat. We're here to help!

Did this answer your question?