Getting started

Connect to a dedicated server
SSH for Linux, RDP for Windows

Login credentials are available in the server details in the console after delivery.

Configure a dedicated server View server credentials

For a server that has already been delivered, open the console and check the operating system and address before connecting for the first time.

Find the credentials

Connection details in one place

Payment confirmation and server delivery are separate steps. Check the server status before connecting. Once delivery is complete, use the address and credentials shown in the server details to log in; payment records do not confirm delivery.

Open the right server

After signing in to the console, open the server list and select the server associated with the order. If there are multiple servers, check the server ID and memory tier first to avoid combining an address and password from different machines.

  1. 01Sign in to the console

    Use the account associated with the order to open the account page and find the server linked to the paid order.

  2. 02Open the server list

    Find the target server and check its status. Use the credentials displayed in its details after delivery.

  3. 03Check the server details

    Note the first IPv4 address, login name and initial password, and confirm which operating system is installed.

Find a server in the console
Server details · field guide

Check these five details before connecting

Server ID
Matches the server for the target order
Operating system
Determines whether to use SSH or RDP
First IPv4
Address to use for the initial connection
Login name
Use the name shown in the server details
Initial password
View and use it only in the account
This guide explains the fields without displaying real addresses or credentials. Do not include passwords in public screenshots, email subject lines or support ticket attachments.
Linux / FreeBSD / Proxmox VE

Use the login name in the console for your first SSH login

SSH is an encrypted way to access a command line remotely. Use SSH for routine administration of Linux, FreeBSD and Proxmox VE systems. Enter the server's first IPv4 address as the destination in the local client.

Replace the placeholders in angle brackets below with the corresponding values from the server details, and omit the brackets when entering them. No login name or connection port is assumed here. If the client requires additional fields, use the information provided in the server details.

SSH command · use values from server details
ssh <username>@<first IPv4>

A host identity confirmation prompt may appear on the first connection. Check the destination address and host identity. If the client reports that a saved identity has changed, first confirm whether the system was reinstalled or the wrong server was selected; do not simply delete the saved record and continue.

Terminals usually do not display characters while a password is being entered. This does not mean the input has failed. After logging in, change the initial password and then configure a personal SSH key. Before tightening password-login rules, open a second connection to verify that the key works and keep the current session open to avoid locking out the management connection.

Check the processor, memory and two directly attached drives after login

The excerpts below illustrate how to read the output; they are not live data from a particular server. Command output varies by operating system, tool version and resource usage. FreeBSD uses different tools, so do not apply the Linux commands below directly.

Linux first-login checks · read in order
ssh <username>@<first IPv4>
First connection: verify the host identity prompt
Password prompt: enter the initial password from the server details
After login: change the initial password and configure a key

lscpu
Model name:          AMD EPYC 7543P 32-Core Processor
CPU(s):              64
Thread(s) per core:  2
L3 cache:            256 MiB
Virtualization:      AMD-V

free -g
               total        used        free
Mem:           Use the actual output from the server
Tier check: order lists 128GB or 256GB of memory

nvme list
Node                 Model / Capacity
/dev/nvme0n1         NVMe SSD / 1TB
/dev/nvme1n1         NVMe SSD / 1TB
Device paths are examples; use the paths shown by the operating system. The two 1TB NVMe drives appear independently and are not necessarily configured as an array. The listed memory capacity is not directly equivalent to the available GiB shown by system tools.

If a command is not found, first check the distribution and whether the required tool is installed. A missing tool does not by itself indicate a hardware issue. When checking the drives, do not format, wipe or repartition them.

Windows Server

Connect to the first IPv4 address with RDP

RDP is the Remote Desktop Protocol. Use the built-in Remote Desktop client and enter the first IPv4 address shown in the console as the computer address. Find the login name and initial password in the server details as well.

Connect to the remote desktop

First confirm that Windows Server is installed, then enter the address and credentials. If the client automatically fills in an account saved for the local computer or another server, replace it with the login name shown in the server details rather than reusing old credentials.

If an identity or certificate prompt appears, check the target server and address first. If the connection fails, keep the exact error message rather than repeatedly changing the address or guessing the account.

Address and credentials must match the same server

Security steps after the first login

After reaching the desktop, change the initial password and configure account permissions, firewall rules and system updates as required. After changing Remote Desktop or firewall settings, verify that a new connection works before ending the current session.

Windows display languages include English, Traditional Chinese and Simplified Chinese. Version details and monthly licensing information are on the Windows page.

Windows versions and licensing
Using multiple IP addresses

Use the first address for management

Each server includes 1 dedicated IPv4 address by default, with up to 255 additional addresses, for a maximum of 256. Additional addresses are billed individually by the month. Check the order and console details for the number assigned.

Use the first address for management

Whether connecting with SSH or RDP, use the first IPv4 address shown in the console. Multiple addresses do not need to be tried in turn and do not change which login name or credentials to use.

Bind additional addresses in the operating system

Additional IPv4 addresses are configured by the customer in the operating system or virtualization host. Before assigning them to a service or virtual machine, check the address mapping and review bridge, routing and firewall rules to avoid affecting host management access.

Before changing a multi-address configuration, record the current network settings and prepare a recovery plan. An address appearing in the order does not mean its operating-system binding and access rules are already configured.

After the first login

Configure firewalls, disk redundancy and backups separately

A successful remote login only confirms that the management connection works. Before deploying production workloads, configure access controls, storage and data recovery. These are separate measures and cannot replace one another.

Configure firewall rules

Allow access from the appropriate management sources and for the services required. Check that system rules match the application's listening ports. When changing rules, keep the current session open and verify the connection from another client.

If connection issues arise, first check whether firewall, bridge or remote service settings have recently changed, then decide whether a support ticket is needed.

Verify before closing the old session

Choose a layout for the two NVMe drives

The standard configuration has 2×1TB directly attached NVMe drives, with no hardware RAID and no preconfigured RAID-1. If disk redundancy is needed, software RAID or a ZFS mirror can be configured based on the operating system's capabilities.

Mirroring reduces the data capacity available for workloads. Creating an array or storage pool may overwrite existing data. Plan the layout before writing production data and verify each device path carefully.

Direct-attached does not mean redundant

Set up off-site backups

A disk mirror is not a substitute for backups. Accidental deletion, a faulty update or application-level corruption can affect mirrored data as well. Arrange backups independent of the server and test the recovery process.

Customers are responsible for system configuration, application security, data redundancy and backups. Hardware and network issues are handled through support tickets in the console.

Backups must be restorable
Connection issues

Include the server ID and exact error message in the ticket

Before submitting a ticket, return to the server details and confirm that the target server has been delivered, the address is its first IPv4, and the connection method matches the operating system. Do not mix in other addresses, credentials from an older system or login names from another server.

  1. 01Identify the server

    Include the server ID, operating system and address used. Explain whether the issue occurred during the first login or after a settings change. Do not include the initial password or private key.

  2. 02Keep the exact error

    Specify whether the connection used SSH or RDP, include the exact error shown by the client and give the approximate time it occurred. Redact passwords, verification codes and other sensitive details from screenshots.

  3. 03List the checks already completed

    Include the results of checking the address and account, any recent network or system changes, and whether the same issue occurs with all clients. This helps distinguish authentication, system and network problems.

Submit connection issues through a console support ticket

Technical troubleshooting and server records stay in the same account. For configuration options, system reinstalls and billing questions, start with the FAQs.

Open a support ticket in the console Configuration and system FAQs