Custom Container SSH Access

Custom Container SSH Access

SSH access provides full command-line control over a custom container. It can be used to install packages, edit configuration files, inspect processes, review logs and perform other administrative operations with root permissions.

In this article

SSH Access Overview

Custom containers do not include a dedicated graphical administration interface. SSH is therefore one of the main ways to obtain full control over a container and perform advanced management through terminal commands.

✓

Dashboard tools may be sufficient

Many common tasks can be completed without SSH by using Container Configuration, Configuration Manager, logs, variables, volumes, links, ports and run settings directly from the platform dashboard.

The platform also provides a dedicated command-line client for remote management and automation of environment lifecycle operations.

SSH GatewayConnects through the platform gateway using an SSH key pair. A public IP is not required.
Public IP accessConnects directly to the container using its public IP, username and password.

Connect Through the SSH Gateway

The SSH Gateway provides a central access point for containers and environments in the account. The connection is authenticated using an SSH key pair.

1

Generate an SSH key pair

Create a private and public SSH key pair on your computer using an SSH-compatible terminal or key-generation utility.

2

Add the public key to the dashboard

Open the account settings, navigate to the SSH Keys section and add the public part of the generated key pair.

3

Connect to the SSH Gateway

Use the SSH Gateway address and the account access instructions supplied by the platform. After authentication, select the required environment and custom container.

Connect to a custom container through the SSH Gateway
Connect to the required custom container through the platform SSH Gateway.
i

No public IP is required

The SSH Gateway can provide terminal access to containers even when they do not have an external public IP address.

Connect Through a Public IP

Direct SSH access can be established without SSH keys when a public IP address is attached to the required container.

1

Attach a public IP

Open the environment topology and enable a public IP for the required node.

2

Find the container credentials

Use the username, public IP address and password sent by email when the container is created or added to the environment.

3

Open a terminal

Launch a terminal emulator or an SSH client on your computer.

4

Run the SSH command

Enter the username and public IP address using the following format:

ssh username@public-ip-address
5

Enter the password

Provide the password from the container-creation email when prompted.

After successful authentication, the terminal opens inside the container with full root permissions.

Troubleshoot the SSH Connection

When the connection cannot be established, verify both network access and the SSH service inside the container.

Firewall rulesConfirm that SSH traffic is allowed for the required port and source address.
OpenSSH serviceVerify that the OpenSSH server is installed and running inside the container.
Public IPFor direct access, confirm that the correct public IP is attached to the selected node.
CredentialsCheck the username and password from the most recent platform email.
SSH keyFor gateway access, verify that the correct public key is added to the account and the matching private key is available locally.
!

Check the SSH service first

A valid IP address and firewall rule are not enough if the container image does not include a running OpenSSH server.

Reset the Container Password

If the password has been forgotten or the original email is no longer available, generate new credentials from the platform dashboard.

1

Open the node actions

Locate the required custom container and expand the Additional actions using the gear icon.

2

Select Reset Password

Choose Reset Password for the required node or group of nodes.

3

Check the email notification

The platform generates a new password and sends it to the account email address.

Expected Result

The custom container is accessible through the SSH Gateway or its public IP address. After authentication, the user receives root-level terminal access and can perform the required administrative operations.

Important Notes

  • Use the SSH Gateway when a public IP is not required.
  • Direct username-and-password access requires a public IP attached to the container.
  • Protect private SSH keys and never share them with unauthorized users.
  • Review firewall rules before exposing SSH access over the Internet.
  • Confirm that the custom image includes an active OpenSSH server.
  • Root access allows system-wide changes, so use commands carefully.

Common Issues and Solutions

Connection timed outVerify the public IP, network route, firewall rule and SSH service status.
Permission deniedConfirm the username, password or SSH key and ensure the correct credentials are being used.
SSH Gateway authentication failsCheck that the public key is registered in the account and that the local private key matches it.
Password email is unavailableUse the Reset Password action and check the account email for newly generated credentials.
Port is open but SSH still failsConfirm that the OpenSSH server is installed, running and listening on the expected port.

Related Guides