Skip to content

Gateway Software Updates

MyOwnProxy manages the MyOwnProxy application software installed on a Gateway. Customer users cannot initiate a Gateway software update in the current portal.

Do not manually replace, modify, or upgrade the installed MyOwnProxy application software. Contact MyOwnProxy Support if the reported version is missing or unexpected, or if Support has asked you to prepare for an update.

Responsibility boundary

A MyOwnProxy application-software update is not a Gateway operating-system update.

  • MyOwnProxy performs updates to MyOwnProxy application software.
  • You maintain the Gateway host, its Ubuntu operating-system lifecycle, and its OS security updates.

When maintaining the Gateway OS, follow your organization's host-management process and account for the effect of making the Gateway unavailable. Avoid changing the installed MyOwnProxy application files as part of OS maintenance.

Prepare for an update

MyOwnProxy Support coordinates with you when an update requires customer action or a maintenance window. When coordination is requested:

  1. Identify Proxies and applications that connect through the Gateway.
  2. Prepare applications to reconnect after an interruption.
  3. If continuous service is required, arrange and verify an alternative connection path before the maintenance window.
  4. Keep the Gateway powered on and connected unless MyOwnProxy Support instructs you otherwise.

MyOwnProxy performs the software update. Customer users do not need to run an update command or upload software.

Expected service impact

A Gateway software update can briefly interrupt proxy service through the affected Gateway. Pool and direct Node connections that enter through that Gateway may be interrupted, and new connections may fail until the Gateway returns to service.

The update changes MyOwnProxy software on the Gateway; it does not update the MyOwnProxy software installed on assigned Nodes. However, those Nodes depend on the Gateway for their proxy entry path, so traffic through them may still be affected during the Gateway interruption.

Do not assume a Gateway software update is zero-downtime. Applications should be able to reconnect or retry according to your operational requirements.

Verify after the update

  1. Open Gateways and select the affected Gateway.
  2. Verify that it returns to ACTIVE and reports healthy operation.
  3. Confirm that the reported Gateway software version matches the version expected for the maintenance.
  4. Review the assigned Nodes and confirm that required Nodes are operational.
  5. Establish a new Pool or direct Node connection through the Gateway and verify the expected exit behavior.

If the Gateway remains DEGRADED or OFFLINE, its version is unexpected, or proxy connections fail after the maintenance window, contact MyOwnProxy Support and see Software Update/Reboot Problems.