Skip to content

Verifying Connection

Verify MyOwnProxy with a new connection using the intended supported method. Reusing an established application connection can hide a recent credential, Pool-selection, or endpoint change.

Run a connection test

  1. Select the intended method and copy its current host and port from the 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 connection using the selected method and matching 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 matching connection example with a public IP-check destination. The generated temporary-credential command provides a current test command. You may use an organization-approved IP-check destination 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 connection and Internet path are working for the selected method.
Pool connection returns the Current Node's public IP The Pool path is using its Current 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.

Verify DNS and egress behavior

Use an application mode that sends the destination hostname to the proxy for remote resolution. The SOCKS5 curl example uses --socks5-hostname; HTTP requests and HTTPS CONNECT also use proxy-side resolution when the application supplies a hostname. When MyOwnProxy performs the lookup, DNS resolution and the proxied connection follow the same residential Node.

Open a new connection to a hostname and confirm that the request succeeds and returns the expected Node's exit IP. An exit-IP check confirms the proxy egress path but does not by itself identify the DNS resolver. If the application resolves the hostname locally before connecting, the test does not exercise MyOwnProxy's proxy-side DNS behavior.

See Connection Details for method-specific behavior and Residential DNS resolution for the resolver path and failure behavior.

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 Current, Recommended, and the eligible candidates in Proxy details. New connections use Current; Recommended may differ without already carrying traffic. 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 selected method under Connection Methods 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.