Skip to content

Connecting through a Specific Node

Direct Node access is an optional, secondary connection method. Use it only when an application must use one specific Node and its public exit IP. For normal traffic, use Pool access so MyOwnProxy can select from eligible, available Nodes.

Direct access bypasses Pool selection. If the chosen Node or its Gateway is unavailable, MyOwnProxy does not move that direct connection to another Node.

Before you begin

  • Choose an ACTIVE, healthy Node with an operational Gateway assignment.
  • Confirm that its assigned Gateway is ACTIVE and healthy.
  • Have an Active persistent Customer-scoped Proxy Credential.
  • Make sure the application supports authenticated SOCKS5 connections.

Temporary Proxy Credentials currently support Pool endpoints only and cannot authenticate direct Node access.

Obtain the endpoint

  1. Open Nodes and choose the intended Node.
  2. Copy its displayed Direct Access value. It contains the Gateway-specific host and the Node's assigned port.
  3. Confirm the Node's displayed Last Public IP so that you can compare it with the observed exit IP during verification.

Not every Node has usable direct connection details at all times. MyOwnProxy displays Direct Access when the Node has a current Gateway assignment and assigned connection port; successful traffic still requires the Node and Gateway to be operational. Do not construct missing details yourself.

Configure the application

  1. Select SOCKS5 as the application's proxy protocol.
  2. Split the displayed Direct Access value into its host and port if the application uses separate fields.
  3. Enter the persistent 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 the Node's current Direct Access endpoint and persistent credential. Avoid leaving the completed command in shell history or logs.

Verify the result

The request's observed public IP should match the selected Node's current public IP. A direct connection should exit through that specific Node.

Use a new connection for every verification attempt. Follow Verifying Connection if authentication fails, the request cannot reach the Internet, or the exit IP is unexpected.

Reassignment and replacement

After reassigning a Node to another Gateway, copy its current Direct Access value again and update the application if the host or port changed. A replacement Node is a different target and has its own connection details.

Node reassignment or replacement does not by itself require a new persistent Proxy Credential, because that credential is scoped to the Customer rather than the individual Node. See Managing Nodes.