Skip to content

Proxy Connection Problems

Use this page when an application cannot reach a SOCKS5 endpoint, cannot complete a SOCKS5 connection, or connects but cannot reach its destination.

Identify the symptom

Symptom Likely scope
The host or port is unreachable Stale connection values, Gateway availability, or the network path from the application
The endpoint rejects the username or password Proxy Credential value, status, expiry, or scope; see Authentication Problems
Authentication succeeds but the destination fails Node availability, destination reachability, or application SOCKS5 configuration
A Pool endpoint has no usable path No currently eligible Node, an unavailable Gateway, or incorrect Pool membership
A direct Node endpoint fails The selected Node, its assigned Gateway, or stale Direct Access values

Checks

  1. Copy the current displayed Host and Port, Proxy URL, or Direct Access value again. Do not construct a hostname or port from a resource ID or another endpoint.
  2. Open a new connection so that you are testing current endpoint, credential, and selection behavior.
  3. Confirm that the serving Gateway is ACTIVE and healthy in Health Explorer.
  4. For a Pool connection, confirm that the Proxy and Pool are available and use Candidate Diagnostics to verify that the Pool has an eligible Node.
  5. For direct access, confirm that the selected Node is ACTIVE, healthy, and still assigned to the expected Gateway.
  6. If authentication is rejected, follow Authentication Problems.
  7. An ADMIN can use Run Test in Proxy details to test the Pool endpoint and review the reported exit IP and latency when available. A VIEWER cannot run this live test.
  8. When a command-line check is useful, use the verified example in Connection Details. Keep the command and password out of tickets and logs.

What the result means

  • Failure before authentication normally points to the endpoint, Gateway, or network path rather than credential scope.
  • Authentication rejection points to the supplied credential or whether that credential is valid for the target.
  • A healthy Gateway with no eligible Pool Node means the Pool cannot serve a new connection until a member becomes eligible.
  • A successful Proxy live test with an application failure narrows the problem to the application's network path, configuration, or destination.
  • After a Node reassignment, previously copied Direct Access values can be stale. Copy the complete current value again. A Pool's endpoint remains associated with its Proxy Gateway, but its usable membership can change.

Supported recovery

Correct stale endpoint values or application SOCKS5 settings, restore the affected Gateway or Node, or have an ADMIN correct Pool membership or credentials. Pool membership and persistent-credential changes can take approximately 30 seconds to become effective; test with a new connection after that interval.

Contact Support

Contact MyOwnProxy Support when the displayed endpoint, resource health, Pool eligibility, and credential status are correct but a new connection still fails. Include whether the failure occurs before authentication, during authentication, or after authentication, plus the information in Contacting Support.