Skip to content

Managing Nodes

Use Node information and lifecycle operations to monitor availability, change Gateway assignment, arrange temporary remote access, and safely retire or replace customer hardware.

An ADMIN can update Node information, reassign or reactivate a Node, decommission or permanently remove it, and request temporary SSH access material. A VIEWER can review Node information and status but cannot perform these actions.

View Node information and status

The Node list and details provide information such as:

  • Node identity, region, and lifecycle state.
  • Current and intended Gateway assignment.
  • Last heartbeat, health results, warnings, and errors.
  • Reported software version and host resource observations.
  • Last reported public IP and direct-access details when available.

Use Understanding Nodes to interpret lifecycle states. Use Observability when investigating health or availability.

Update Node information

An ADMIN can edit a Node's display name and region. These are descriptive changes: they do not move the Node to another Gateway or change Pool membership.

After saving, verify the updated values in Node details.

Move a Node to another Gateway

Move a Node when changing its serving location, draining or replacing a Gateway, or restoring a Node that has lost its operational Gateway assignment.

Before you begin

  • You must be an ADMIN.
  • The destination Gateway must belong to the same Customer.
  • Use an ACTIVE, healthy destination Gateway that you have already validated.
  • A Node in PENDING_ENROLLMENT cannot be moved. Complete enrollment first.
  • Expect a temporary interruption while the Node changes Gateway assignment.

Move and verify the Node

  1. Open the Node and start the Gateway reassignment.
  2. Select the destination Gateway and provide a reason when useful.
  3. Confirm the reassignment.
  4. Wait for the Node to receive and apply the new assignment.
  5. Confirm that the Node shows the destination Gateway and returns to ACTIVE.
  6. Review its required Pool memberships and test affected Proxy connections.

MyOwnProxy applies the new assignment automatically. Do not manually reconfigure the Node.

Gateway assignment and Pool membership are separate. Do not assume that moving a Node preserves or establishes its eligibility for a Proxy. Review the intended membership through Proxies after every move. See Managing Gateways and Proxies.

Respond to an unavailable Node

When a Node is DEGRADED or OFFLINE:

  1. Review its last heartbeat, health results, resource observations, and last reported public IP.
  2. Check the Raspberry Pi's power, Ethernet connection, and local Internet service.
  3. Determine which Pools and direct-access applications depend on the Node.
  4. Confirm whether other eligible Nodes are available for affected Pools.
  5. Use Node Problems or contact MyOwnProxy Support if it does not recover.

Pool traffic may continue through another eligible, available Node. Direct access to this Node fails while it is unavailable, and a Pool with no other eligible available Node cannot provide service.

Do not decommission a Node merely to clear a health alert. Decommissioning removes it from proxy service and should be used for retirement or a deliberate service withdrawal.

Request temporary remote access

An ADMIN can request temporary SSH access to a Node from MyOwnProxy.

You provide an SSH public key; the corresponding private key remains on your computer. MyOwnProxy signs the public key and provides temporary connection material and the exact connection instructions in the interface.

The certificate stops authorizing new SSH sessions at the displayed Valid Before time. It does not automatically close a session that is already connected.

See Accessing Your Nodes Remotely for the complete procedure and security guidance.

Replace a Node

Create a replacement as a new Node. Use this sequence to limit service interruption:

  1. Prepare and add the replacement Node.
  2. Confirm that it is ACTIVE, healthy, reporting the expected public IP, and assigned to the intended Gateway.
  3. Add it to the required Pools through Proxies.
  4. Test Pool-based traffic and any application that must use the replacement directly.
  5. Remove production dependencies on the old Node.
  6. Decommission the old Node.
  7. Verify production traffic through the replacement before disconnecting or repurposing the old hardware.

Proxy Credentials are scoped to a Customer or Gateway rather than an individual Node, so replacing a Node does not by itself require new credentials. Update application connection details if its direct-access destination changes.

Decommission a Node

Decommissioning is reversible. It removes a Node from proxy service while retaining its managed identity and record in MyOwnProxy. It is not identity revocation. The Node may continue communicating with the control plane as allowed by its lifecycle and can later be returned to service.

Before you begin

  • You must be an ADMIN.
  • Confirm that other eligible Nodes can carry any required Pool traffic.
  • Remove or replace applications that connect directly through this Node.
  • Prepare and validate a replacement first when service must continue.

Decommission and verify

  1. Open the Node and start the decommission action.
  2. Review the impact, provide a reason, and confirm the operation.
  3. Confirm that the Node reaches DECOMMISSIONED state.
  4. Verify that the Node no longer serves Pool or direct-access traffic before disconnecting or repurposing the hardware.

A decommissioned Node no longer participates in Pool selection or direct Node access.

Decommissioning does not revoke Proxy Credentials because credentials are scoped to the Customer or Gateway rather than to an individual Node.

If the Node needs to return to service, reactivate it in MyOwnProxy, assign it to an ACTIVE Gateway, review its Pool membership, and verify proxy traffic before relying on it in production.

Permanently remove a Node

Permanently remove is irreversible and is not a Node lifecycle state. It removes the logical Node identity, makes existing provisioning material unusable, and invalidates Node identity credentials associated with that Node.

Use permanent removal when deliberately destroying a Node's managed identity, permanently retiring it from MyOwnProxy, or responding to lost, stolen, exposed, or potentially compromised provisioning material before first enrollment. Do not use permanent removal as a routine response to an OFFLINE or DEGRADED Node; follow the supported recovery steps first.

Before you begin

  • You must be an ADMIN for the Customer that owns the Node. A VIEWER cannot permanently remove a Node.
  • Confirm that other eligible Nodes can carry any required Pool traffic.
  • Remove or replace applications that connect directly through this Node.
  • Prepare and validate a replacement first when service must continue.
  • Be ready to type the Node's exact name to confirm the action.

Permanently remove the Node

  1. Open the Node's Node Detail page.
  2. Select Permanently remove.
  3. Review the irreversible-action warning and type the exact Node name shown in the confirmation.
  4. Select Permanently remove to confirm.

The removed Node cannot be reactivated or reassigned. Provisioning material prepared while it was in PENDING_ENROLLMENT can no longer enroll it, and previously issued Node identity credentials can no longer authenticate it.

Permanent Node removal does not revoke general Proxy Credentials. Temporary Proxy Credentials remain Gateway-scoped, and persistent Proxy Credentials remain Customer-scoped; manage their lifecycle separately. If the same physical Raspberry Pi will be used with MyOwnProxy again, create a new Node and prepare it with the new Node's provisioning material.

Node software and maintenance

MyOwnProxy manages the MyOwnProxy application software on Nodes. Node software updates, supported operating-system security patches, and remote reboots are performed by MyOwnProxy administrators and coordinated with you when needed. These maintenance controls are not customer self-service actions for ADMIN users.

See Node Software Updates, Node Security Patches and Reboots, and Security and Responsibilities.