Connection Details
A MyOwnProxy connection combines a supported proxy method with a valid Proxy Credential. Choose the intended Pool or Direct Node access, then use the host and protocol-specific port displayed by MyOwnProxy.
Required values
| Value | Purpose | Where to get it |
|---|---|---|
| Target | Selects either a Pool or one specific Node. | Choose the intended Proxy under Proxies, or the intended Node under Nodes. |
| Method | Selects SOCKS5 or HTTP / HTTPS CONNECT. | Choose from the target's displayed Connection Methods. |
| Host | Identifies the Gateway that accepts the connection. | Copy it from the selected connection method. |
| Port | Identifies the selected Pool or Node endpoint and method on that Gateway. | Copy it from the selected connection method. |
| Username | Identifies the Proxy Credential. | Obtain it when creating or generating the credential, or from the persistent-credential list. |
| Password | Authenticates the Proxy Credential. | Store it when the credential is created, generated, or rotated; it cannot be retrieved later. |
The canonical host is provided by MyOwnProxy and is Gateway-specific. Pools and Direct Node access served by the same Gateway use that Gateway host, with displayed ports for the target's supported methods.
MyOwnProxy shows protocol-labeled Connection Methods for Proxies and Nodes. The HTTP and HTTPS CONNECT methods share one HTTP proxy endpoint. Copy the current displayed URL or host and port, especially after replacing a Gateway or reassigning a Node.
If MyOwnProxy does not display a host or port, do not infer one from a resource ID, port range, or another endpoint. Confirm the Gateway and target are correctly configured and available.
Supported methods and port families
| Access mode | SOCKS5 | HTTP / HTTPS CONNECT |
|---|---|---|
| Pool | 33xxx |
43xxx |
| Direct Node access | 34xxx |
44xxx |
These ranges help identify a method or troubleshoot a mismatch. They are not instructions for constructing a port. Always use the hostname and port displayed for your target and method.
When using the HTTP / HTTPS CONNECT method, configure an HTTP proxy for an http:// destination and use the same displayed endpoint for an https:// destination; the application establishes an HTTP CONNECT tunnel. SOCKS5 can carry either destination type without changing the proxy method. The HTTP proxy URL uses http://<host>:<port> for both cases. CONNECT preserves end-to-end TLS between the application and destination. MyOwnProxy does not terminate TLS or inspect HTTPS content as part of CONNECT.
Pool connections use the Pool's Current Node; Direct Node access uses the selected Node. Both access modes support all three methods and preserve residential egress. This includes customer-created Pools and pool-all. Recommended is a selection preference, not evidence that it is carrying a new connection. See Understanding Proxies and Pools.
Permissions
An ADMIN and a VIEWER can view and copy Pool and Direct Node connection information. An ADMIN is required to create or manage Proxy Credentials and to run the live test from Proxy details. A VIEWER cannot access credential management in the current customer interface.
Pool and Node compatibility
| Connection target | Normal use | Temporary Gateway-scoped credential | Persistent Customer-scoped credential |
|---|---|---|---|
| Pool | Recommended for normal application traffic | Yes, on the Gateway that generated it | Yes, on an applicable Customer Gateway |
| Direct Node access | Secondary option when one fixed exit Node is required | No | Yes, on an applicable Customer Gateway |
The system-managed pool-all Pool uses the same connection methods as a customer-created Proxy. The temporary-credential workflow shows pool-all as its default connection target.
The same Proxy Credential username and password model authenticates SOCKS5, HTTP proxy, and HTTPS CONNECT connections. MyOwnProxy consumes proxy authentication credentials; for HTTP/CONNECT, Proxy-Authorization credentials are not forwarded to the origin server. See Understanding Proxy Credentials and Managing Proxy Credentials for scope, expiration, rotation, and secure storage.
Curl connection examples
Select the displayed method and its matching host and port. Applications differ in how they accept proxy credentials and destination hostnames; follow your application's proxy configuration guidance.
SOCKS5
curl --silent --show-error \
--socks5-hostname <host>:<port> \
--proxy-user '<username>:<password>' \
<url>
--socks5-hostname tells curl to send the destination hostname through the SOCKS5 connection for remote resolution. MyOwnProxy then performs that resolution through the same residential Node path as the proxy connection, rather than resolving the hostname on the application host.
HTTP destination through the HTTP proxy
Use an http:// destination for <http-url>:
curl --silent --show-error \
--proxy 'http://<host>:<port>' \
--proxy-user '<username>:<password>' \
<http-url>
HTTPS destination through CONNECT
Use an https:// destination for <https-url>. Curl uses HTTP CONNECT through the same HTTP / HTTPS CONNECT endpoint:
curl --silent --show-error \
--proxy 'http://<host>:<port>' \
--proxy-user '<username>:<password>' \
<https-url>
Use the displayed port for the selected access mode and method in every example. For a customer-created Pool or a specific displayed Pool endpoint, use the matching example with that Pool's displayed hostname, protocol-specific port, and intended Proxy Credential. Once real credentials are substituted, these commands contain secrets. The temporary-credential result also provides Copy curl command for pool-all; select the intended connection method before copying. The generated command does not verify a customer-created Pool. Treat it as a secret.
Proxy-side hostname resolution
When the proxy receives a destination hostname, MyOwnProxy keeps DNS resolution on the same residential Node path as the proxy connection:
- With SOCKS5 remote hostname resolution, sometimes called SOCKS5h, the application sends the hostname to the proxy. The curl example above uses this mode.
- For an HTTP proxy request that supplies a destination hostname, DNS resolution performed by MyOwnProxy follows the same Node as the HTTP traffic.
- For HTTPS CONNECT, when MyOwnProxy must resolve the supplied CONNECT hostname, resolution follows the same Node as the CONNECT traffic.
This behavior does not apply to a DNS lookup that the application performs locally before sending only an IP address to the proxy. See Residential DNS resolution for the resolver path and failure behavior.
Security note
Do not put real Proxy Credential passwords in source code, documentation, tickets, or logs. A command containing a password may also be retained in shell history. Use your application's secret facility or an approved secret manager. See Managing Proxy Credentials and Security and Responsibilities.