Skip to content

Quick Start

This guide provides the recommended path from an empty MyOwnProxy environment to a working Pool-based Proxy. It is an orientation guide; follow the instructions supplied by MyOwnProxy and the detailed product sections for each procedure.

The setup actions in this guide require an ADMIN user. A VIEWER can review resources and status but cannot complete administrative setup.

1. Verify the requirements

Review the System Requirements before preparing infrastructure. Confirm any deployment-specific compatibility or network requirements with MyOwnProxy Support.

2. Add and install a Gateway

Create the Gateway in MyOwnProxy, then follow the customer-facing installation flow provided for that Gateway. Run only the installation command and values supplied by MyOwnProxy, and keep enrollment material private.

Wait until the Gateway reports operational status before continuing. See Installing a Gateway for the complete customer procedure.

3. Create and prepare a Node

Create the Node in MyOwnProxy. MyOwnProxy provides the configuration values required to enroll it.

Flash the provided Node image to the Node's SD card, then write the complete provided values into the required configuration file on the SD card. Do not reconstruct or change the generated values. Insert the SD card, connect the Node as instructed, and start it.

After boot, the Node completes its MyOwnProxy setup and enrolls automatically. See Preparing and Adding a Node for the full preparation procedure.

4. Verify that the Node is available

Use Observability to confirm that the Node is reporting health and has become available. If it does not become available, recheck the supplied installation instructions and see Troubleshooting.

5. Confirm the Gateway assignment

Confirm that the Node is assigned to the intended Gateway. If you move it to another Gateway later, MyOwnProxy applies the change automatically; no manual changes on the Node are required.

The Node is automatically included in the Gateway's system-managed pool-all. Membership in customer-created Pools is configured separately.

6. Create the Proxy and configure its Pool

Create a Proxy and configure its Pool membership. A customer-created Proxy starts with an empty Pool, so explicitly add the Nodes that should be eligible to serve traffic for it.

The Gateway's system-managed pool-all is different: it already contains the Gateway's Nodes and MyOwnProxy maintains that membership automatically.

Pool access is the recommended mode. Use direct Node access only when an application must use a specific exit Node. See Managing Proxies and Pool Nodes for the procedure and Key Concepts for the distinction.

7. Create a Proxy Credential

Choose a credential type that matches the use case:

  • Create a temporary, Gateway-scoped credential for time-limited access.
  • Create a persistent, Customer-scoped credential for ongoing application use.

Store the credential securely. Persistent credential rotation and revocation may take around 30 seconds to propagate and become fully effective. See Managing Proxy Credentials.

8. Connect through the Pool

Configure your application with the Pool connection details and Proxy Credential supplied by MyOwnProxy. Both Pool access and direct Node access use SOCKS5.

Use the Pool endpoint for normal proxy traffic. See Connecting through a Pool for connection guidance.

9. Verify operation

Send a request through the configured SOCKS5 connection and verify that it succeeds. Confirm that the observed exit IP belongs to an eligible Node in the Pool, and check Observability for current Gateway and Node health. See Verifying Connection for the operational checklist.

If the request fails or the exit is unexpected, confirm Pool membership, Node availability, Gateway assignment, and credential status before contacting MyOwnProxy Support.