Skip to content

Proxy Connection Problems

Use this page when an application cannot reach a proxy endpoint, cannot complete a connection, or connects but cannot reach its destination. See Connection Details for supported methods and examples.

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 responds but the proxy connection fails Application method does not match the displayed endpoint's port family
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 proxy configuration
When using HTTP / HTTPS CONNECT, an HTTP destination works but an HTTPS destination fails Check that the application uses HTTP CONNECT for the HTTPS destination through the displayed HTTP / HTTPS CONNECT endpoint
A hostname fails but a known IP destination works Application resolution mode or proxy-side DNS availability through the residential Node used by the proxy connection
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 displayed connection values

Checks

  1. In the Proxy's or Node's Connection Methods, select the intended method and recopy both the displayed host and port. Do not construct either value from a resource ID or port range.
  2. Check that the application method matches the port family: Pool SOCKS5 uses 33xxx, Direct Node SOCKS5 uses 34xxx, Pool HTTP / HTTPS CONNECT uses 43xxx, and Direct Node HTTP / HTTPS CONNECT uses 44xxx. Use the actual displayed value, not a calculated port.
  3. When using the HTTP / HTTPS CONNECT method, use HTTP proxy behavior for an http:// destination and CONNECT through the same displayed endpoint for an https:// destination. SOCKS5 can carry either destination type without changing the proxy method. CONNECT preserves end-to-end TLS; MyOwnProxy does not terminate it.
  4. Open a new connection so that you are testing current endpoint, credential, and selection behavior.
  5. Confirm that the serving Gateway is ACTIVE and healthy in Health Explorer.
  6. For Pool access, confirm that the Proxy and Pool are available and use Candidate Diagnostics to verify that the Pool has an eligible Node. New connections use the Pool's Current Node for residential egress.
  7. For Direct Node access, confirm that the selected Node is ACTIVE, healthy, and still assigned to the expected Gateway. It provides the residential exit; a temporary credential cannot authenticate this access mode, so use a persistent credential.
  8. Confirm that the application sends the destination hostname to the proxy when proxy-side resolution is intended. For SOCKS5 curl, preserve --socks5-hostname. HTTP requests and CONNECT that supply a hostname use the same residential Node path for proxy-side resolution. A client that resolves locally and sends only an IP does not use MyOwnProxy for that DNS lookup.
  9. If authentication is rejected, check the current username and password, credential status, expiry, scope, and propagation interval; then follow Authentication Problems. For HTTP/CONNECT, Proxy-Authorization credentials are consumed by MyOwnProxy and are not forwarded to the origin.
  10. An ADMIN can use Run Test in Proxy details to test the Pool path and review the reported exit IP and latency when available. A VIEWER cannot run this live test.
  11. When a command-line check is useful, use the matching example in Connection Details. Keep the completed 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 method and port-family mismatch must be corrected before credential or destination behavior can be evaluated.
  • A healthy Gateway with no eligible Pool Node means the Pool cannot serve a new connection until a member becomes eligible.
  • If proxy-side hostname resolution is unavailable through the residential Node used by the proxy connection, the request fails. MyOwnProxy does not fall back to the Gateway or hosting provider's resolver path.
  • A successful Proxy live test confirms the tested Pool path is working. If the application still fails, verify its intended proxy method, exact displayed hostname and matching protocol-specific port with a fresh connection.
  • After a Node reassignment, previously copied connection values can be stale. Recopy the intended method's complete current value. A Pool's endpoint remains associated with its Proxy Gateway, but its usable membership can change.

Supported recovery

Correct stale displayed endpoint values or application proxy settings, restore the affected Gateway or Node, or have an ADMIN correct Pool membership or credentials. For a hostname-resolution failure, confirm the application supplies the hostname to the proxy and restore the residential Node path; no separate Node DNS configuration is required. 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.