Skip to content

Verifying Connection

Verify MyOwnProxy with a new SOCKS5 connection. Reusing an established application connection can hide a recent credential, Pool-selection, or endpoint change.

Run a connection test

  1. Copy the current host and port from the intended Proxy or Node in MyOwnProxy.
  2. Confirm that the Proxy Credential is compatible with the target and has not expired or been revoked.
  3. Configure an authenticated SOCKS5 connection using the copied endpoint.
  4. Open a new connection and request a public IP-check endpoint.
  5. Record whether authentication and the Internet request succeeded.
  6. Compare the returned public IP with the expected Node information in MyOwnProxy.

For curl, use the verified connection example. The current generated temporary-credential command uses the same public IP-check service. You may use an organization-approved equivalent if it returns only the request's public source IP.

An ADMIN can also select Run Test on Proxy details to test the current Pool path and view the reported Exit IP and latency when available. This is separate from testing the credential and settings used by an application. A VIEWER can see connection details but cannot run this test.

Interpret the result

Result Expected meaning
Authentication succeeds and the request returns an IP The new SOCKS5 connection and Internet path are working.
Pool connection returns an eligible Node's public IP The Pool path is using its selected Node as the Internet exit.
Direct Node connection returns that Node's public IP The direct endpoint is using the intended fixed Node as the Internet exit.

A Pool can return the same exit IP across repeated new connections. Pool reevaluation does not guarantee selection of a different Node. See Proxy Policy and TTL.

If authentication fails

Check:

  • The exact username and current password.
  • Whether the credential is expired or revoked.
  • Whether a temporary credential was generated by the same Gateway and is being used with a Pool endpoint.
  • Whether a persistent credential belongs to the same Customer.
  • Whether a recent persistent-credential create, rotation, or revocation has had approximately 30 seconds to propagate.
  • Whether the application is opening a new connection rather than reusing an established one.

See Managing Proxy Credentials for credential status and lifecycle operations.

If the request fails after authentication

Check that the Gateway and intended Node are ACTIVE and healthy. For Pool access, confirm that the Pool has at least one eligible, available Node. For direct access, confirm that the selected Node remains available and assigned to the displayed Gateway.

Review Health Explorer and Proxy Connection Problems if the path remains unavailable. If the exit IP is unexpected, see Unexpected Exit IP or Node Selection.

If the exit IP is unexpected

For a Pool connection, review the currently selected Node and eligible candidates in Proxy details. Opening multiple connections does not require MyOwnProxy to select a different Node, and TTL expiration does not guarantee a different exit.

Use Candidate Diagnostics to review the selected Pool's current candidate preference, eligibility, state, dataplane status, network score, and information age. The diagnostics snapshot does not identify the Node already serving an established connection.

For a direct Node connection, recopy the intended Node's Direct Access value and compare the result with its current Last Public IP. Check whether the Node was reassigned or replaced and whether the application is still using older connection details.