Tnion.SH
Get Started
Tutorial8 min

Connect and verify a Linux server

Prepare a VPS, add its SSH connection, verify the destination, and review its system summary.

Server requirements

Use a Linux VPS or dedicated server you control. The current Tnion.SH connection supports password-based SSH. The account must be able to perform the installation and configuration required for Docker, PostgreSQL containers, Odoo files, and host-level Nginx.

The exact CPU, memory, and disk requirement depends on the Odoo database, installed modules, worker configuration, and user load. Start from your own capacity estimate and leave space for database growth and local backup archives.

Check SSH first

Confirm the credentials outside Tnion.SH from an authorized machine:

Code
ssh -p 22 deploy@203.0.113.10
hostname
uname -snrm

Replace the example IP, port, and username. If a firewall or provider security group limits SSH, allow the network path used by the Tnion.SH API.

Prefer a dedicated deployment account over a personal administrator login. Grant only the privileges required for the supported operations and review those privileges regularly.

Add the server

In the workspace, open Servers and select Add server. Enter:

  1. A recognizable server name.
  2. The IP address or valid hostname.
  3. The SSH port.
  4. The SSH username.
  5. The password.

The password is encrypted before storage. It is not returned in normal server API responses. Updating the password replaces the stored encrypted credential.

Verify the host

Run Test connection. The probe is read-only and returns connection status, hostname, system summary, and the SSH server-key fingerprint.

Compare the fingerprint with a trusted value from the VPS console or an administrator who has direct access. A changed fingerprint can be legitimate after a rebuild, but it must be investigated before provisioning.

Common connection failures include a blocked port, incorrect username, expired password, missing network allowlist, or an SSH service listening on a different address.

Review capacity

Open the server detail view and collect metrics. Tnion.SH reports CPU information, memory, root disk usage, uptime, and load averages when the probe succeeds.

Review free disk space before provisioning and before large backups or restores. Because backup archives remain on the registered host until downloaded or moved, local retention consumes the same infrastructure capacity as the running environment.