Skip to content

Node Software Updates

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

Do not manually replace, modify, or upgrade MyOwnProxy Node software. Contact MyOwnProxy Support if a Node reports a missing or unexpected software version, or if Support has asked you to prepare for an update.

A Node software update is separate from an operating-system security patch and a reboot. Updating MyOwnProxy Node software does not mean that either of those maintenance actions will also be performed.

Prepare for an update

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

  1. Identify applications using direct access to the Node.
  2. Review every production Pool that includes the Node.
  3. If Pool availability must continue, verify that each affected Pool contains another eligible, healthy Node.
  4. Prepare applications to retry or reconnect if a connection is interrupted.
  5. Keep the Node powered on with stable Ethernet and Internet connectivity 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

The affected Node may be temporarily unavailable while its software is updated and validated. The update targets that Node and does not directly update other Nodes.

For Pool-based access:

  • Other eligible, available Pool members can serve subsequent connections.
  • Service cannot continue through that Pool when the affected Node is its only eligible member.
  • An established connection does not move automatically to another Node; the application may need to reconnect.

For direct Node access, the application depends on the affected Node. Direct access may be unavailable or interrupted while that Node is unavailable.

Do not assume a Node software update is zero-downtime.

Verify after the update

  1. Open Nodes and select the affected Node.
  2. Verify that it returns to ACTIVE and reports healthy operation.
  3. Confirm that its reported software version matches the version expected for the maintenance.
  4. Review its Gateway assignment and membership in production Pools.
  5. Establish new Pool and direct Node connections as applicable and verify the expected exit IP.

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