Skip to content

Node Security Patches and Reboots

Supported Node OS security patching and maintenance reboots are performed by MyOwnProxy administrators. They are not customer self-service actions for either ADMIN or VIEWER users.

This responsibility applies only to supported Node security maintenance. It does not mean that MyOwnProxy automatically manages every operating-system, firmware, or vendor update on a Node, and it does not apply to Gateway OS security updates.

Security patch behavior

Each supported security-patch operation applies to one Node. Security patching does not automatically reboot the Node.

If a reboot is required or recommended after patching, it is performed as a separate maintenance action by a MyOwnProxy administrator. A controlled reboot may also be used independently for supported maintenance.

Contact MyOwnProxy Support if Node OS maintenance is needed outside this supported workflow.

Prepare for maintenance

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

  1. Identify direct connections to the affected Node and production Pools that include it.
  2. Verify that affected Pools have another eligible, healthy Node when Pool availability must continue.
  3. Prepare applications to retry or reconnect.
  4. Keep the Node powered on with stable Ethernet and Internet connectivity unless Support instructs you otherwise.
  5. Confirm the maintenance window when one is required.

Expected service impact

During a reboot, the affected Node is unavailable until it starts again and returns to an operational state. Existing proxy connections through that Node end.

Pool-based applications can use other eligible, available Pool members for subsequent connections. They cannot use the Pool when the affected Node is its only eligible member. Direct access to the affected Node is unavailable while it is rebooting or otherwise unavailable.

Security patching does not automatically reboot the Node, but you should still prepare for possible temporary Node unavailability during the overall maintenance workflow. Do not assume maintenance is zero-downtime.

Verify after maintenance

  1. Open Nodes and select the affected Node.
  2. Verify that it returns to ACTIVE and reports healthy operation.
  3. Review its most recent operational reporting and Gateway assignment.
  4. Confirm that it remains in the intended production Pools.
  5. Establish new Pool and direct Node connections as applicable and verify the expected exit IP.

The customer portal does not provide dedicated security-patch or reboot progress and history. Contact MyOwnProxy Support if the Node does not recover as expected or if you need the maintenance result.

Gateway OS security remains customer-managed

Do not apply the Node maintenance model to Gateways. You remain responsible for Gateway operating-system upgrades and Gateway OS security updates. See Gateway Software Updates for the responsibility boundary.