Linux Servers

A Linux server is a KVM-based virtual server with dedicated CPU, memory and root access, billed monthly. This page covers everything from ordering to day-to-day operations.

Specs and images

Each plan has the following parameters. The exact combinations are shown on the product page and the purchase page:

Different regions use different price multipliers. The "×N" next to a region name on the purchase page shows that region's monthly price relative to the base price.

System images

The images actually available are shown on the purchase page. Some application images require a minimum plan; if your plan does not meet it, the purchase page shows that the plan does not support the image. For example:

The access address, port and initialization steps of an application image are shown in the "App Info" card on the resource detail page. Most admin interfaces (Portainer, Nginx Proxy Manager, code-server, etc.) listen only on the instance itself; open an SSH tunnel first and then use your local browser. The detail page provides a copyable SSH tunnel command.

Ordering

1. Choose a plan on the Linux server product page to open the purchase page.
2. Select the plan configuration, billing period, server region and image. A region that cannot be selected has insufficient resources.
3. Check the order summary, click "Buy Now" and complete payment. See Top-up, payment & invoices.
4. Once created, the instance appears under User Center → Resources.

SSH connection

The instance's IP address, username and password are shown in the basic information on the "Overview" tab of the resource detail page; click the eye icon to reveal the password. The default SSH port is 22.

Password login

macOS, Linux and Windows 10 or later include the ssh command:

ssh root@<instance IP>
# if you changed the SSH port
ssh -p <port> root@<instance IP>

Use the username shown on the detail page. You can also use third-party clients such as Xshell, PuTTY, WindTerm, MobaXterm or Termius: create a session with the IP, port 22, username and password.

Key login

Instances use password login by default. To switch to key login, log in once with the password, then add your local public key to the instance:

# generate a key locally (skip if you already have one)
ssh-keygen -t ed25519
# write the public key to ~/.ssh/authorized_keys on the instance
ssh-copy-id root@<instance IP>
# log in with the key from now on
ssh -i ~/.ssh/id_ed25519 root@<instance IP>

Web console

While the instance is running, click "Login Console" on the detail page to open a web terminal in a new window. You can log in with the password or by uploading a private key, with no client to install.

Troubleshooting connection failures

1. On the detail page, confirm the instance status is "Running" and the IP matches the one you are connecting to.
2. Confirm the port, username and password. If you just reset the password, wait for the instance to finish restarting.
3. Run MTR in both directions: from the instance to your local public IP, and from your computer to the instance IP. Submit screenshots of both results in a technical ticket or send them to voyracloud@gmail.com.

Latency on routes from mainland China to overseas regions can cause SSH timeouts.

Console operations

The resource detail page offers the following operations:

Reset password, reinstall and change IP are available only when the instance is "Running" or "Stopped". If another operation is in progress, wait for it to finish.

Password requirements

• 8–32 characters.
• At least three of: uppercase letters, lowercase letters, digits, special characters.
• Only letters, digits and these symbols are allowed:

()`~!@#$%^&*-+=_|{}[]:;'<>,.?/

Reinstalling the system

1. Open the "Reinstall System" tab on the detail page and select the target image.
2. Click "Reinstall" and confirm in the dialog.
3. Wait for the status to change from "Reinstalling" to "Running".

Reinstalling erases all data on the system disk. Back up first.

Outbound proxy configuration

The "Proxy configuration" tab sets up a SOCKS5 or HTTP/HTTPS proxy for a Linux instance so that all of its IPv4 outbound traffic reaches the internet through the proxy. Browsers, scripts and Docker containers do not need individual proxy settings.

Prerequisites

• The instance runs Linux and is running.
• The system uses systemd, runs on amd64 or arm64, uses apt or dnf (or already has the required dependencies), and provides the /dev/net/tun device.
• The instance can reach GitHub to download sing-box.
• The proxy exit IP must differ from the instance's public IP.

Steps

1. Open the "Proxy configuration" tab on the detail page.
2. Under "Choose a proxy", pick a saved proxy or select "Enter an address manually". Static ISP proxies and rotating residential proxies bought on VoyraCloud can be selected directly from the list.
3. If you changed the instance's SSH port, enter it under "Advanced settings" (default 22).
4. Click "Save and apply configuration", confirm in the "Authorize remote configuration" dialog, and click "Authorize and run". The platform connects to the instance over SSH using the saved login credentials, installs sing-box, and configures a systemd service, a TUN device and IPv4 routes.
5. Wait until the status shows "Applied"; the page then displays the verified IPv4 exit.
6. To restore direct connections, click "Disable proxy".

Supported formats for manual entry:

socks5://host:port
socks5h://user:password@host:port
http://user:password@host:8080
https://host:443
host:port                      # SOCKS5 when no scheme is given
host:port:user:password        # SOCKS5

A port is required; wrap IPv6 addresses in square brackets; percent-encode special characters in URI credentials.

Scope

• SSH, internal network access and replies to inbound connections keep their original path, so enabling the proxy does not affect SSH login.
• IPv6 does not go through the proxy.
• HTTP proxies support TCP only; UDP over SOCKS5 depends on the proxy service.
• Proxy credentials are stored encrypted and not shown again after saving. An account can save up to 100 proxies and reuse them across instances; editing or deleting a saved proxy does not change configurations already applied to instances.
• If changing the configuration fails, the installer tries to restore the previous one. If both installation and restore fail, check the instance network through the web console.

Traffic billing

• One-way billing: plan traffic counts outbound traffic only; inbound traffic is free and unlimited.
• Monthly reset: traffic resets every calendar month from the purchase time, in line with the resource's billing cycle.
• When exhausted: the instance's public network speed is limited to 1 Mbps and the traffic bar on the detail page turns red.
• Traffic add-on packages: click "Buy Traffic Package" under the traffic package on the detail page, choose a package and pay. A package is valid until the date shown in the dialog and becomes invalid when it expires or is used up.

IPv4 change rules

• Changing the IP is a paid operation with a fixed fee per change; the amount is shown in the change dialog.
• The new IP is assigned at random from the available pool in the same region; you cannot choose a specific range.
• The old IP is released immediately and cannot be recovered.
• Traffic usage on the current IP is kept.
• The instance stays in service during the change.
• IP change fees are non-refundable.
• Additional IPv4 addresses cannot be added to an instance at this time.

Steps: click "Change IP Address" next to the IP on the detail page, check the resource information, tick the confirmation box, choose a payment method and pay.

A sudden traffic burst may trigger the upstream carrier's risk controls and block the IP. If this happens, submit a ticket or email voyracloud@gmail.com to request unblocking.

Refunds

A Linux server is eligible for a full refund within 24 hours of purchase if less than 5 GB of data transfer has been used. After 24 hours, or once at least 5 GB has been used, the refund is prorated by the lower of the remaining time and remaining traffic in the billing period. A 10% fee is charged on every approved refund. After a refund is confirmed the instance is deleted and its data cannot be recovered. See Renewal, expiry & refunds for the full rules.