Skip to main content
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.

​
Separate three settings

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

1

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.
2

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 for manual switching and unlimited-product differences.
3

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, mobile, or unlimited residential setup.
4

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 and latency test to check different aspects of the connection.

​
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 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.