Connection Guide

Connect to a Dedicated Server: Find Credentials in the Console

Use SSH for Linux and RDP for Windows.

View Credentials in Console Configure a Server

For the first connection after payment and delivery. Use the login address, username and credentials shown in the server details.

After Payment and Delivery

Get Connection Details from the Server Record

First, confirm the account and server, then copy the connection details. The operating system selected at checkout determines the connection method; a payment record alone does not confirm that the server has been delivered.

01
Sign In to the Ordering Account

Open the console and sign in with the account associated with the order. If multiple servers are listed, identify the right one by order number, model and memory tier. Do not use credentials from another server.
02
Open the Server Details

Wait until the delivery details are visible, then find the login address and credentials. If connection details are not shown yet, do not guess the username based on the server model or reuse credentials from another server.
03
Check and Copy Each Field

Enter the address, username and corresponding credentials in the client. Check for leading or trailing spaces. For a server with multiple addresses, use the first IPv4 address in the list; do not paste the full list into the connection field.

Example Server Details

Server ID: Order number and model
Operating System: Delivered OS version
Login Address: First address in the IPv4 list
Login User: Username shown in the details
Credentials: Connection credentials shown in the details

This card shows where to find each field and what it is for. It does not display actual account details, addresses or passwords. The console shows the current information.

IPv4 Connection Rules

Use the First Address for the Initial Connection

Each server includes 1 dedicated IPv4 address by default. Additional addresses are billed individually per month. Adding addresses does not change which address to use for the initial connection.

Included by Default

1dedicated IPv4 address

Find the address in the server details in the console. If only one address is listed, use it for the first SSH or RDP connection.

Included with the server

Additional Addresses

255maximum additional addresses

Additional IPv4 addresses cost $2/month each and are billed individually. Plan business address allocation and in-system network settings separately; these do not replace the host connection address.

Billed by quantity selected

Maximum Total

256IPv4 addresses

That is 1 included address plus up to 255 additional addresses. Always use the first address in the list for the initial connection, not an arbitrary business address.

Check address order first

When copying an address, include only the address itself—not the list number, comma or any explanatory text. Check the network documentation for information about additional addresses and bandwidth tiers.

Bandwidth and IPv4 Rules

Linux, FreeBSD and Proxmox VE

Make the First Connection over SSH

In a local SSH client, enter the first IPv4 address and the username shown in the console. The command below uses example field labels; it does not show default account details or a real address.

Enter the Connection Target

Replace LOGIN_USER in the command with the login username, and FIRST_IPV4 with the first address. If the client requires other connection parameters, use the information shown in the console rather than guessing defaults.

Check the address and username

Verify the Host Identity

A host key confirmation prompt may appear on the first connection. Check the target address and verify the fingerprint against a trusted record before proceeding. If a previously recorded key changes, investigate a reinstall or change of target rather than ignoring the warning.

Verify before authenticating

Update Authentication

After signing in, change the initial password or configure an SSH key. Keep the current session open while changing authentication settings. Test the new method in a separate connection before closing the original session to avoid losing access due to a configuration error.

Test before closing the session

Check Hardware After Connecting

Check CPU, Memory and NVMe Details

The following are examples of Linux commands and output, not live test results. Usernames, addresses and fingerprints are placeholders; device names and system-reported values depend on the server.

First SSH Login and Specification Check · Linux Example

$ ssh LOGIN_USER@FIRST_IPV4
The authenticity of host 'FIRST_IPV4' can't be established.
Host key fingerprint: HOST_KEY_FINGERPRINT
Are you sure you want to continue connecting (yes/no/[fingerprint])?

LOGIN_USER@FIRST_IPV4's password:

$ lscpu
CPU(s):                  64
Model name:              AMD EPYC 7543P 32-Core Processor

$ free -g
               total
Mem:             125

$ nvme list
Node             Model               Namespace   Usage
/dev/nvme0n1     NVME_MODEL           1           1 TB
/dev/nvme1n1     NVME_MODEL           1           1 TB

Memory Readings Are Not Free Memory

The total value from free -g is the amount of memory recognised by the operating system. A 128GB tier may show about 125, and a 256GB tier about 251; unit conversion and system reservations affect the displayed value. available changes with workload and is not a fixed reading for a memory tier.

Commands Depend on the Operating System

The lscpu, free and nvme list examples are for Linux, and the relevant tools must be installed. Use the appropriate system utilities on FreeBSD. Do not format disks, create pools or repartition drives just to reproduce the example output.

Windows Server

Connect to the Remote Desktop over RDP

Use the remote desktop client included with the local operating system. Enter the first IPv4 address and the credentials shown in the console. If the client has saved details for another account, check which username is actually being submitted.

Check	Where to Find It	What to Enter
Remote computer address	IPv4 list in the server details	Enter only the first address. Do not use an additional business address.
Username and credentials	Connection details for the same server	Enter the values shown. Do not use the local computer account or a password from another server.
OS and licence edition	Order configuration and delivered OS	Windows Server Standard or Datacenter. The edition is the one selected at checkout.
System language	Language selected at checkout	English, Traditional Chinese or Simplified Chinese. Interface labels appear in the selected language.

If a certificate or identity prompt appears, first confirm that the connection target matches the server details; do not dismiss every prompt automatically. After signing in, check the OS version, update the credentials, and confirm that the system firewall and remote access settings meet business requirements. Windows licensing is billed monthly. The licence edition is not determined by the local client's display language.

Keep Useful Details When Troubleshooting Connection Issues

If SSH or RDP will not connect, first check the first IPv4 address, server status and client error. Then submit a support ticket through the console for assistance.

After the First Login

Check the Drives Before Planning Storage

The standard configuration has two directly attached 1TB NVMe drives, with no hardware RAID. A successful connection confirms access only; it does not mean redundancy or backups are in place.

01
Check Each Drive

Check the device identifiers, capacity and mount status of both NVMe drives. System partitions and file systems use space, so the combined advertised capacity of both drives is not a ready-to-use volume. Direct attachment is not a preconfigured RAID-1 array.
02
Choose a Redundancy Setup

Choose software RAID or a ZFS mirror to suit the workload, and confirm the target devices and existing data before making changes. Mirroring reduces usable capacity. Creating an array or storage pool can overwrite existing data, so arrange data migration and backups first.
03
Set Up Separate Backups

The account holder is responsible for system configuration, business data and backups. Mirroring is not a substitute for off-site backups. Include recovery tests in the backup plan to confirm that essential data can be restored after accidental deletion, configuration changes or a service failure.

Connection Support Ticket

Include the Server, Address and Exact Error

Submit a ticket through the console and include the details from a single connection attempt in one record. The exact error message is more useful than a general description such as “unable to log in” for distinguishing network, host identity and account authentication issues.

Describe the Target and Environment

Include the order number or server ID, the first IPv4 address used, whether the connection was over SSH or RDP, the target OS and the name of the local client. Note whether the issue occurred on the first login or after a change to the password, key, firewall or network settings.

One set of details per server

Include the Exact Error and Checks Performed

Paste the full error message and, if needed, attach a screenshot with sensitive details redacted. Include the fields already checked. Do not paste plaintext passwords, private keys or verification codes into a ticket. Redact account details unrelated to the issue from screenshots.

Keep error text; redact sensitive details

Server Details Are the Source of Truth

Check credentials for an existing server or report connection issues through the console.

Submit a Support Ticket Configure a New Server