> ## Documentation Index
> Fetch the complete documentation index at: https://help.miyaip.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Backconnect proxy gateways: setup and exit IPs

> Understand backconnect proxy gateways, configure the entry address and exit location, choose a session policy, and verify the observed exit IP.

A backconnect gateway provides access to a pool of proxy exits. Your client connects to a host and port; the destination observes the selected exit IP. The address resolved from the gateway hostname can differ from that exit. [Source: MiyaIP backconnect guide](https://miyaip.com/blog/backconnect-proxy).

## Separate three settings

| Setting | What you configure | What you check |
| - | - | - |
| Entry gateway | Host, port, and protocol used by the client | Connection and authentication |
| Exit location | Available country, region, city, or ASN filters | Exit and location observed by the destination |
| Session policy | Per-request rotation, sticky sessions, or supported manual switching | Exit changes and session continuity |

Backconnect describes the access architecture. Rotation describes when the exit changes. Residential, mobile, and datacenter describe the exit network. Check each independently.

## Configure a reproducible connection

<Steps>
  <Step title="Choose the product and entry gateway">
    Open the product's **Proxy Setup**. Current entry choices include **Smart Routing**, **America**, **Europe**, **Hong Kong**, and **CN Transit**. Use the options available in your dashboard.

    Selecting **America** does not also request a US exit. Select the entry route, then set the exit location separately.
  </Step>

  <Step title="Choose the exit and session policy">
    Use only location filters supported by the product and pool. Choose **Sticky Session** for a short workflow requiring one exit. Choose **Rotate every request** for independent requests.

    The dynamic generator initially selects a 30-minute sticky session, with 5, 10, 15, and 30-minute choices. See [rotation and sticky sessions](/guides/rotation-sessions) for manual switching and unlimited-product differences.
  </Step>

  <Step title="Copy the generated connection fields">
    Select **HTTP(S)** or **SOCKS5** according to your client, then generate the proxy. Copy **Host**, **Port**, **Username**, and **Password** into their matching client fields.

    Keep the gateway host separate from the exit IP. Use your dashboard's output rather than illustration addresses or another provider's parameters. Follow the [dynamic residential](/proxy/dynamic-residential/quick-start), [mobile](/proxy/mobile/quick-start), or [unlimited residential](/proxy/unlimited-residential/quick-start) setup.
  </Step>

  <Step title="Verify the exit and target request">
    Use the same generated fields to request an IP-reporting endpoint, then your actual target. Record the timestamp, gateway, requested location, observed exit, session policy, and result. Omit the password.

    For dynamic proxies, check the selected location and observed exit. For static proxies, compare with the purchased static IP and intended location in your dashboard. The gateway host is not the expected exit IP. Use the [exit test](/guides/rotation-sessions#verify-the-session) and [latency test](/guides/latency) to check different aspects of the connection.
  </Step>
</Steps>

## Match the persistence to your task

A sticky session requests a temporary exit mapping. Your application still manages cookies and logins. For a longer-lived assigned address, follow the [static residential tutorial](/proxy/static-residential/quick-start) and check allocation, expiry, and replacement rules. Static describes persistence; dedicated describes resource allocation.

With a client-managed list, you select endpoints and maintain their availability and replacements. A gateway simplifies that selection, while your client still handles timeouts, authentication errors, and destination responses. A hostname alone does not reveal internal balancing or recovery behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.