Getting connected

Connect to a Dedicated Server: Find Credentials in the Control Panel

Use SSH for Linux and RDP for Windows.

Configure a Dedicated Server View credentials in the control panel

For a provisioned order, start with the server details in the control panel. Use the address, login account, and authentication details shown for that server.

From order to first login

Five steps to get connected

Payment and provisioning are separate steps. Once payment is complete, wait for the provisioning notification. After receiving the email, open the relevant server details and check the connection information.

Choose a server and options

On the configuration page, select the memory tier, additional drives, bandwidth, extra IPv4 addresses, operating system, and billing period. The operating system determines the connection method.
Pay in USD

Confirm the amount due for the current billing period and complete payment. Available payment methods are listed on the configuration page. Check payment records and server provisioning status separately.
Receive the provisioning email

Check the notification in the account email and match it to the order. A payment confirmation page does not provide the credentials needed to connect.
Open the server details in the control panel

Open the relevant server, check its operating system and address list, then review the login account and authentication details. Keep credentials for different orders separate.
Log in with SSH or RDP

Open the appropriate client for the operating system. Connect using the first IPv4 address and the credentials shown in the control panel. After logging in, continue with system and security configuration.

Use the connection information shown in the server details; do not infer the account, port, or password from the operating system name. If the server has multiple addresses, the steps below use the first IPv4 address.

Linux · FreeBSD · Proxmox VE

First SSH login: match the server before entering credentials

Use the built-in terminal or a familiar SSH client. SSH is used to manage Linux, FreeBSD, and Proxmox VE systems. Refer to the control panel for the actual login details.

Gather the address and account

Check the operating system in the server details, copy the first IPv4 address, and note the login account and authentication details shown in the control panel. Check for spaces or line breaks at the beginning or end of copied text. Do not reuse connection settings saved for another server.

Connect over SSH

Enter the address and account in the client, then authenticate using the details provided in the control panel. When a host identity prompt appears for the first time, verify the target server. If an existing connection record shows a change in host identity, first check whether the system was reinstalled or the connection target changed; do not dismiss the warning without checking.

Secure the account after first login

After logging in, consider changing the initial password or setting up key-based authentication, and update the system. When using key-based authentication, verify that the key works in a separate session before disabling the existing authentication method. Keep the current session open before changing firewall rules to avoid blocking new management connections.

Keep Proxmox VE host management credentials separate from guest system login details. Host credentials do not grant access to guests. The renter manages guest network and authentication settings.

Windows Server

First RDP login: use the account for the provisioned system

Open a Remote Desktop client and enter the address and credentials shown in the control panel. SSH clients are not used for Windows Remote Desktop connections.

What to enter in the client

Use the first IPv4 address as the connection address. Get the login account and password from the relevant server details rather than guessing the default account based on the operating system version. If the client has saved credentials, first confirm that they belong to the server just provisioned.

If a Remote Desktop identity or certificate prompt appears, check the connection target and address. Do not rely on a saved connection name alone to identify the target, or treat a certificate prompt as a password error.

Connection: RDP

System language and first login

Windows is provisioned in the English, Traditional Chinese, or Simplified Chinese language selected at checkout. The Remote Desktop client's interface language does not determine the server's system language. Use the language of the system actually provisioned.

After reaching the desktop, consider changing the initial password, updating the system, and checking the firewall. Before changing remote access policies, confirm that the new login method works. Changing account permissions and network rules at the same time can result in a lost connection.

3 system languages, selected at checkout

Connecting to multiple addresses

For multiple IPv4 addresses, use the first one to connect

The same address rule applies to SSH and RDP

If the server has multiple IPv4 addresses, use the first address in the control panel list for the initial connection. Additional addresses must be configured in the operating system by the renter. An assigned address does not necessarily mean all network settings for that address are already in place.

After the first successful login, configure other addresses and their associated services as needed. Record the existing settings before changing network configuration, change one set of settings at a time, and verify the result. Check address configuration, service listeners, and firewall rules separately.

Narrow down the cause

Connection failed? Check the details, then the network

Record the complete error shown by the client, then work through the checks below in order. A timeout, a refused connection, and an authentication failure point to different issues. Avoid changing system settings before checking the error message.

Verify the target address

Confirm that the connection is to the server just provisioned and uses the first IPv4 address shown in the control panel. Check that the pasted text contains no extra spaces, old addresses, or other text, and that the client has not automatically selected a previously saved connection target.

Check the complete credentials

Get the account and authentication details again from the relevant server details. For authentication failures, check the input method, letter case, and client cache. Enter the password in the client's designated authentication field; do not put it in the address field, connection name, or ticket body.

Check the local network environment

Confirm that the local network is working, and check for restrictions from the local firewall or network. If possible, test from another trusted network to help distinguish a client-side environment issue from a server-side issue.

Review changes on the server

If the server connected successfully before, check for recent changes to addresses, routes, firewall rules, login policies, or authentication details. Keep any working session open. Avoid clearing all security rules at once while troubleshooting, as this can increase exposure.

If the connection still fails after these checks, submit a support ticket through the control panel. A list of the checks already completed is more useful for troubleshooting than simply reporting that the connection does not work.

Misconfigured network? Use the recovery option in the control panel

The control panel includes a browser-based graphical session for recovery after network or firewall misconfiguration. Use SSH or RDP for routine access.

Report a connection issue

Include the server ID and error details in the ticket

Submit a support request from the ticket page in the control panel. For server-related issues, identify the order and server ID, and explain whether the problem occurs before connecting, during authentication, or after login.

Provide details that can be verified

Include the server ID, operating system, connection method (SSH or RDP), complete error message, and when the issue was first noticed. Screenshots should show the error while hiding passwords, keys, and personal information unrelated to troubleshooting.

List the checks already completed

Note whether the first IPv4 address was used, credentials were checked again, another network was tested, and any recent system or firewall changes were made. Do not send full login passwords or private keys in public email or the ticket body.

Continue from the relevant server details

Check the address and credentials, or submit a connection issue through the ticket page. The hardware and network are managed by this service; the renter is responsible for the system, accounts, keys, and data backups.

Open the control panel to submit a ticket Contact support by email