Skip to content

Installing a Gateway

Use this procedure to create a Gateway in MyOwnProxy and install it on a customer-controlled host or virtual machine.

Required role

You must be an ADMIN to create a Gateway. A VIEWER can review existing Gateways but cannot create or install one.

Before you begin

Prepare a Gateway host that has:

  • Ubuntu 24.04 LTS.
  • At least 4 GB of RAM.
  • Administrative access through sudo.
  • Stable Internet connectivity.

You also need the host's static public IPv4 address and a name and region that will identify the Gateway in MyOwnProxy.

CPU, disk, bandwidth, cloud-provider, and processor-architecture requirements are not defined here. Confirm unusual or high-traffic deployments with MyOwnProxy Support. See System Requirements for the full readiness checklist.

Create the Gateway in MyOwnProxy

  1. Create a Gateway for your Customer.
  2. Enter a descriptive name, the deployment region, and the static public IPv4 address of the Gateway host.
  3. Review the values, then create the Gateway.
  4. Securely copy the installation flow provided by MyOwnProxy.

The newly created Gateway remains in PENDING_ENROLLMENT until installation and enrollment complete.

The provided installation material is specific to that Gateway and contains sensitive, time-limited enrollment information. Copy the complete flow before leaving the creation result, store it only as long as needed, and do not share it in logs, tickets, or documentation.

If MyOwnProxy does not provide an authoritative installation flow, do not construct one yourself. Contact MyOwnProxy Support.

Run the provided installation flow

  1. Connect to the intended Gateway host with an account that can use sudo.
  2. Confirm that the host meets the requirements above and that you are installing the intended Gateway.
  3. Run the complete installation flow exactly as provided by MyOwnProxy.
  4. Allow the process to finish before closing the session or restarting the host.

The installation instructions are generated for the Gateway. Do not replace their values, reuse them on another host, or substitute a command copied from another environment.

What happens next

The installation flow installs the approved MyOwnProxy application software, enrolls the Gateway, starts normal operation, and begins reporting status to MyOwnProxy.

After enrollment, the Gateway normally progresses from ENROLLED to ACTIVE when it reports healthy operation. A DEGRADED state means that enrollment succeeded but a health problem requires attention.

Do not assign production workloads until the Gateway is ACTIVE and its information has been verified.

Verify success

Confirm that:

  • The Gateway state is ACTIVE.
  • Its last operational report is recent.
  • The displayed name, region, and static public IPv4 address match the intended host.
  • Health information does not show unresolved errors.
  • The reported Gateway software version is present.

For a replacement or staged deployment, move a low-impact Node to the Gateway when appropriate, review its Pool membership, and test a SOCKS5 connection before moving additional workloads.

Troubleshooting

If the Gateway remains PENDING_ENROLLMENT, confirm that the provided installation flow completed and that the host has stable Internet connectivity.

If the installation material is unavailable, has expired, or was exposed, stop and contact MyOwnProxy Support. Do not attempt to reconstruct enrollment values.

If the Gateway becomes DEGRADED or OFFLINE, review Observability and Gateway Problems. Avoid making undocumented changes to the installed MyOwnProxy software.

Software and operating-system maintenance

MyOwnProxy administrators currently perform Gateway application-software updates. Customer self-service Gateway upgrades are not part of the current workflow.

You remain responsible for Ubuntu upgrades and Gateway OS security packages. See Gateway Software Updates for the responsibility boundary.