Skip to content

Connecting through a Pool

Pool access is the normal and recommended way to use MyOwnProxy. The application connects to a Proxy on its Gateway, and the Pool's current selection determines which eligible Node provides the Internet exit.

Before you begin

  • Confirm that the Proxy's Gateway is ACTIVE and healthy.
  • Confirm that the Pool contains at least one eligible, available Node. The system-managed pool-all Pool includes the Gateway's Nodes automatically.
  • Have a valid Proxy Credential. A temporary credential must have been generated by this Gateway; a persistent credential must belong to the same Customer.
  • Make sure the application supports authenticated SOCKS5 connections.

See Managing Proxies and Pool Nodes if the Pool needs to be created or its membership changed.

Obtain the endpoint

  1. Open Proxies and choose the intended Proxy or pool-all.
  2. In Connection Details, copy the Host and Port, or copy the displayed Proxy URL.
  3. Do not substitute a port from another Proxy, even when both Proxies use the same Gateway.

The Host belongs to the Gateway and the Port identifies this Pool endpoint. MyOwnProxy assigns the port, so use the displayed value rather than constructing one.

Configure the application

  1. Select SOCKS5 as the application's proxy protocol.
  2. Enter the copied Host and Port.
  3. Enter the Proxy Credential username and current password.
  4. Configure destination-name resolution through the proxy when the application supports it.
  5. Save the configuration and establish a new connection.

For a command-line test, use the verified curl example with this Pool's endpoint and credential. Avoid leaving the completed command in shell history or logs. If you generated a temporary credential, the result's Copy curl command action provides the current test command directly.

Connection behavior

Each new SOCKS5 connection uses the Pool's currently selected Node. The Node, not the Gateway, provides the public exit IP.

Opening several connections does not guarantee a different Node for each connection. The selected Node may remain the same until MyOwnProxy makes a deliberate selection change, and a later reevaluation may select the same Node again. Established connections remain attached to the Node selected when they were opened.

See Proxy Policy and TTL for the selection-refresh behavior without changing the application's endpoint.

Verify the result

Use a new connection and confirm that:

  • SOCKS5 authentication succeeds.
  • The Internet request succeeds.
  • The observed public IP corresponds to the selected eligible Node shown for the Pool.

Follow Verifying Connection for the full checklist.