Linux VPS Access via SSH Gate

Linux VPS Access via SSH Gate

Connect to an Elastic VPS container through SSH to install, configure, and manage the required software. The platform provides both browser-based Web SSH and console access through the dedicated SSH Gate, with full root permissions for the VPS node.

In this article

Overview

The SSH Gate acts as a single secure access point for remotely managing the environments and servers available under your platform account. The SSH connection process for an Elastic VPS is similar to the process used for other platform containers, but the VPS session provides full root access.

!

Windows VPS access

Windows-based VPS containers are managed through Remote Desktop Protocol (RDP) rather than the Linux SSH access methods described on this page.

VPS SSH Access Options

Web SSH A one-click browser connection from the platform dashboard. No additional local SSH configuration is required.
SSH Gate A console-based SSH connection from your local computer. Authentication is performed through your custom SSH key pair.
Access level Both methods provide the same full root management capabilities inside the Linux VPS container.

Access through Web SSH

Web SSH allows you to open a terminal session directly from the platform dashboard without preparing a local SSH client or key-based console connection.

1

Locate the required Elastic VPS environment in the dashboard.

2

Expand the VPS node and click the Web SSH button.

3

The browser-based terminal opens automatically and provides root-level access to the VPS container.

Elastic VPS access through Web SSH
Open the VPS terminal directly from the dashboard using the Web SSH button.
✓

No local configuration required

Web SSH is the quickest option when you need immediate browser-based access to the VPS container.

Access through SSH Gate

SSH Gate allows you to connect to the Linux VPS from a terminal or SSH client on your local computer. The connection is authenticated by matching the private SSH key on your computer with the public key stored in your platform account.

SSH Gate Prerequisites

Complete the following preparation before establishing your first SSH Gate connection:

1

Generate a public and private SSH key pair on the local computer.

2

Add the generated public SSH key to the SSH Keys section of the platform dashboard.

3

Keep the corresponding private key securely on the local computer. It is used by your SSH client during authentication.

!

Account-level SSH key

The public key added through the dashboard is attached to your platform account and can be used to access the permitted environments and containers through SSH Gate.

Connect from the Local Console

Open the SSH Gate information in the dashboard and copy the generated connection command. The general connection format is:

ssh <user-id>@gate.<platform-domain> -p 3022
User ID The account identifier supplied by the platform as part of the SSH connection string.
SSH host The dedicated platform SSH Gate hostname, typically beginning with gate..
Port The SSH Gate connection uses port 3022.
Authentication The local SSH client uses the private key that matches the public key stored in the dashboard.
Elastic VPS connection command through SSH Gate
Copy the SSH Gate command and execute it in a terminal on the local computer.
4

Run the copied command in the local terminal.

5

If prompted during the first connection, verify and accept the SSH host fingerprint.

6

Select the required environment and VPS container when prompted by the SSH Gate interface.

✓

Full root management

After connecting, you can install software, modify system configuration, manage services, and perform other administrative operations with root permissions.

Public IP Alternative

You can also operate the Linux VPS through an external SSH client by connecting directly to its attached Public IP address. Access through SSH Gate, Web SSH, or Public IP provides the same VPS management functionality and root-level capabilities.

Web SSH Best for immediate access directly from the browser.
SSH Gate Best for key-based access through the platform’s central SSH endpoint.
Public IP Best when connecting directly to the VPS through a preferred third-party SSH client.

Related Documentation