Skip to content

Remote Access Problems

Use this page when temporary SSH access to a Node cannot be requested, issued, or used.

Identify the symptom

Symptom Check and action
The certificate action is not available Only an ADMIN can request temporary SSH access. A VIEWER cannot see or use the action.
The public key is rejected Submit one complete, supported OpenSSH public-key line. Never submit the private key.
The result was closed or not saved The result cannot be reopened. An ADMIN must submit the public key again and save the new material before closing the dialog.
The local command reports a missing program Install or make available both OpenSSH and ncat, as required by the generated instructions.
Authentication is too early or expired Start new authentication at or after Valid After and before Valid Before. Request new material if the window has ended.
The command reaches the wrong path or cannot connect Use the complete generated instructions and values without alteration; then check the Node and assigned Gateway reachability.

Checks

  1. Confirm that the requester has the ADMIN role for the Node's Customer.
  2. Confirm that the submitted value is the public key and that the matching private key remains on the connecting computer.
  3. Use one of the supported durations: 15 or 30 minutes.
  4. Save the complete issued certificate and instructions before closing the result.
  5. Confirm that the local OpenSSH client and ncat are available.
  6. Use the exact certificate paths, private-key selection, host, port, and command shown in the generated instructions.
  7. Connect within the displayed validity window.
  8. Whenever possible, confirm that both the Node and its assigned Gateway are ACTIVE and healthy. Successful issuance does not prove that either resource is reachable.

What the result means

  • Material that is not yet valid or is past Valid Before cannot start a new authenticated session.
  • Expiry does not automatically close a session that authenticated earlier and remains open.
  • The portal does not provide early revocation. Multiple unexpired certificates and sessions can overlap, and issuing new material does not invalidate earlier material.
  • The prpn-customer account is highly privileged. Use the shortest practical duration, protect all access material, perform only the intended diagnostic work, and close the session promptly.

Supported recovery

Correct the role, public-key input, local tools, saved files, validity timing, or generated-command usage as applicable. Follow Accessing Your Nodes Remotely rather than constructing connection values or alternate commands.

Do not modify MyOwnProxy-managed software or persistent Node network and access configuration. If normal temporary access cannot reach the Node, emergency rescue is performed only by MyOwnProxy Support.

Contact Support

Contact MyOwnProxy Support when issuance succeeds but exact generated instructions still cannot reach an ACTIVE, healthy Node through an ACTIVE, healthy Gateway; when access material may have been exposed; or when Emergency Node Rescue is required. Never send a private key or issued certificate. See Contacting Support.