Skip to content

Understanding Gateways

A Gateway is the customer-controlled entry point for MyOwnProxy proxy connections. Applications connect to it using SOCKS5, and the Gateway routes each connection through an eligible Node.

Where a Gateway fits

The normal Pool-based traffic path is:

Application -> Gateway -> Pool selection -> Node -> Internet

The Gateway accepts the application's proxy connection. The selected Node, not the Gateway, provides the Internet exit connection.

This path is part of the customer-controlled data plane. Proxy traffic does not pass through the MyOwnProxy control plane. See How MyOwnProxy Works for the separation between the control plane and data plane.

Relationships to Nodes, Pools, and Proxies

A Gateway participates in several distinct relationships:

  • A Node is assigned to a Gateway for connectivity and management.
  • A Node is included in a Pool when it is eligible to serve that Pool's proxy traffic.
  • A Proxy uses a Pool to expose eligible Nodes to applications.

Gateway assignment does not automatically mean that a Node belongs to every Pool on that Gateway. When moving a Node between Gateways, review its Pool membership and Proxy availability separately.

Pool access is the normal operating mode. Direct access through a specific Node is also available through its assigned Gateway when a particular exit Node is required. Both modes use SOCKS5 and a Proxy Credential.

Ownership and responsibilities

Gateways run on customer-controlled hosts or virtual machines. A Gateway requires Ubuntu 24.04 LTS, at least 4 GB of RAM, administrative access through sudo, a static public IPv4 address, and stable Internet connectivity. See System Requirements before provisioning a host.

MyOwnProxy manages the MyOwnProxy application software installed on the Gateway. Gateway software updates are currently performed by MyOwnProxy administrators. See Gateway Software Updates.

You remain responsible for:

  • The Gateway host or virtual machine.
  • The Ubuntu operating-system lifecycle.
  • Gateway OS security packages.
  • Host-level security and connectivity outside MyOwnProxy.

See the Shared Responsibility Model for the complete product and Customer boundary.

Gateway lifecycle

A Gateway moves through customer-visible states as it is created, installed, operated, or retired:

State Meaning
PENDING_ENROLLMENT The Gateway record exists, but installation and enrollment have not completed.
ENROLLED The Gateway has enrolled and is beginning to report operational information.
ACTIVE The Gateway is reporting healthy operation and can serve normal workloads.
DEGRADED The Gateway is reporting a health problem. Review its health information before assigning new workloads.
OFFLINE MyOwnProxy is no longer receiving current operational reports from the Gateway. Proxy access through it may be unavailable.
DECOMMISSIONED The Gateway has been retired and is stopped for normal use. It cannot be selected as a Node assignment target.

Gateway status is based on operational reports sent to the MyOwnProxy control plane. These reports contain health and status information, not customer proxy traffic.

When a Gateway is unavailable

Applications cannot rely on proxy endpoints served by an unavailable Gateway. Nodes assigned to it cannot serve proxy connections through that Gateway until service is restored or the Nodes are moved to another operational Gateway.

Use Health Explorer to review status, the last operational report, and health information. If recovery is not appropriate, follow the safe replacement workflow in Managing Gateways.

Next steps