SSH Access

Beta

SSH requires a compatible guest with SSH enabled and the connection details supplied by your hosting provider. Panel key management and browser SSH depend on the installed release, provider and plan.

SSH Keys

If you need a new key, generate it on your own device:

ssh-keygen -t ed25519 -C "my-vps"

Choose an unused filename when prompted so you do not overwrite an existing key. Protect the private key with a passphrase. Add only the contents of the public key file, normally ending in .pub, to the panel's key control if offered. Give it a recognizable name so you can select the correct key later.

Private keys

Never upload or paste a private SSH key into the panel, browser console or a support message. Keep the private key on your own device; only the public key belongs in the panel.

SSH Provisioning

Select your public key when creating the VPS if the selected image supports that login method. Allow first-boot setup to finish before connecting. Do not assume adding a key to your panel account changes an already running guest. Follow your provider's instructions for updating access to an existing VPS.

SSH User

Use the username shown for the selected image rather than assuming root. Ubuntu cloud images commonly use ubuntu; Debian cloud images commonly use debian. Custom images can use different accounts, including root only when explicitly documented. See Images or ask your provider if the username is unclear.

SSH Information

Use the host, port and username supplied for your instance. The following addresses are examples; replace them with your own connection details:

ssh [email protected]

For a provider-supplied custom port, such as an enabled NAT service:

ssh -p 23145 [email protected]

Use the assigned public port, not an assumed guest port; see Port Forwarding. For a key outside the default location, add -i /path/to/private_key to the SSH command on your own device. Verify the server's host-key fingerprint through a trusted source before accepting it. Do not bypass a changed-host-key warning without confirming the change with your provider or trusted records.

Browser SSH

Use browser SSH only if your release and provider enable it for your service. Open it from the intended instance's page over HTTPS and disconnect when finished. Do not upload a private key or assume browser access has the same privacy properties as a local SSH client. Ask the provider about credential handling if it is unclear.

Connection Problems

• For a timeout, check the VPS state, address, port and applicable firewall rules.
• For authentication failure, check the image username and that your local client uses the matching key.
• For a refused connection, check whether SSH is running using an available console.

See Troubleshooting before reinstalling or making destructive changes. Send your provider only relevant, redacted errors through private support; never include private keys or passwords.