Connection Details
A MyOwnProxy connection combines a SOCKS5 endpoint with a valid Proxy Credential. Use the values displayed by MyOwnProxy rather than constructing a hostname or choosing a port yourself.
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. |
| Host | Identifies the Gateway that accepts the connection. | Copy it from the Proxy's Connection Details or the Node's Direct Access value. |
| Port | Identifies the selected Pool or Node endpoint on that Gateway. | Copy the displayed value for that target. |
| 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 host is Gateway-specific. Pools and direct Node endpoints served by the same Gateway use that Gateway host, but each target has its own assigned port. Ports are not a single fixed value shared by all customers, Gateways, Pools, or Nodes.
MyOwnProxy displays Pool endpoints as a Proxy URL and as separate Host and Port values. It displays a Node endpoint as Direct Access in the Node list and Node details. Copy the current displayed values, 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 or another endpoint. Confirm the Gateway and target are correctly configured and available.
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 |
| Specific Node | 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 model as a customer-created Proxy: the Gateway host plus the Pool's displayed port. The temporary-credential workflow shows pool-all as its default connection target.
See Understanding Proxy Credentials and Managing Proxy Credentials for credential scope, expiration, rotation, and secure storage.
SOCKS5 client configuration
Set the application's proxy protocol to SOCKS5 and provide the displayed host, port, username, and password. The Proxy URL shown by MyOwnProxy begins with socks5://; applications differ in how they accept credentials and resolve destination hostnames, so follow the application's SOCKS5 documentation for its remaining fields.
For curl, a verified example is:
curl --silent --show-error \
--socks5-hostname <host>:<port> \
--proxy-user '<username>:<password>' \
https://api.ipify.org
--socks5-hostname tells curl to send the destination hostname through the SOCKS5 connection for resolution. This avoids resolving the destination hostname on the application host before the proxy connection is made.
The current temporary-credential result also provides Copy curl command with its generated values. Treat that copied command as a secret because it contains the password.
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.