Remote Access Overview
Normal Node onboarding and operation do not require SSH. Remote access is an optional, temporary capability for investigation and support.
MyOwnProxy provides two distinct remote-access workflows:
| Workflow | Who performs it | How it starts |
|---|---|---|
| Customer-initiated temporary access | A customer ADMIN connects as prpn-customer |
The ADMIN requests an SSH certificate from the Node details page. |
| Emergency Node rescue | MyOwnProxy administrators | The customer contacts MyOwnProxy Support outside the portal. |
These workflows do not use the same customer procedure. A VIEWER cannot request temporary SSH access, and emergency rescue is not customer self-service.
Customer-initiated temporary access
An ADMIN supplies the public key from their SSH key pair. MyOwnProxy signs that public key and returns a temporary SSH certificate with connection instructions for the selected Node.
Only the public key is supplied to MyOwnProxy. The corresponding private key remains on the customer's system.
Never upload, paste, or send your SSH private key to MyOwnProxy.
The certificate stops authorizing new SSH sessions at the Valid Before time shown with it. It does not automatically close a session that is already connected. See Accessing Your Nodes Remotely for prerequisites, the exact portal workflow, and the privilege boundary, or Remote Access Problems when issued access cannot be used.
Emergency Node rescue
Emergency rescue is for a Node that cannot be recovered through the normal customer checks or temporary-access workflow. There is no customer rescue command or rescue request in the portal. Contact MyOwnProxy Support; a MyOwnProxy administrator determines whether remote recovery is possible.
The Node must be powered on and connected for remote recovery to be possible. See Emergency Node Rescue and Contacting Support for the information to collect before contacting Support. The Shared Responsibility Model summarizes the access-material and recovery boundary.