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 Node provides the Internet exit for new connections.

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 the intended proxy method with username-and-password authentication.

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, choose the intended method under Connection Methods and copy its displayed proxy URL or host and port.
  3. Do not substitute a port from another method or Proxy, even when they use the same Gateway.

The host belongs to the Gateway and the port identifies this Pool endpoint and method. MyOwnProxy assigns the port, so use the displayed value rather than constructing one. Customer-created Pools and pool-all support the same methods.

Configure the application

  1. Select the intended supported method in the application.
  2. Enter the copied host and matching 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 of the selected Pool, use the matching curl example with that Pool's displayed hostname, protocol-specific port, and intended Proxy Credential. Avoid leaving the completed command in shell history or logs. In the temporary-credential result, Copy curl command provides a convenient test for pool-all on the issuing Gateway. Select the intended connection method before copying; the initial selection is SOCKS5. The generated command does not verify a customer-created Pool or another displayed Pool endpoint.

Connection behavior

Each new proxy connection uses the Pool's Current Node. The Node, not the Gateway, provides the residential public exit IP.

The Recommended Node is the Node MyOwnProxy would currently prefer when selection is reevaluated; it is not necessarily carrying traffic. Current and Recommended may temporarily differ without indicating a problem. See Current and Recommended Nodes.

Opening several connections does not guarantee a different Node for each connection. Current remains sticky until selection is reevaluated, and reevaluation may keep the same Node. Established connections remain attached to the Node they used when 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:

  • Proxy Credential authentication succeeds.
  • The Internet request succeeds.
  • The observed public IP corresponds to the Pool's Current Node.

Follow Verifying Connection for the full checklist.