How to create a cloud server on serverplus

A cloud server is a virtual machine in a serverplus data center that you create in a couple of minutes and fully control: your own OS, your own resources (vCPU, RAM, disk), your own public IP. You pay per minute for the chosen configuration, and you can change the scale as you go.

Everything is created in the cloud.serverplus.uz panel in a single wizard: you pick the region, image, configuration, disk, network and access key — and click "Create". Below is the whole path step by step, exactly as it looks in the panel.

What you will need

• A serverplus panel account and a positive project balance (the cost of the chosen configuration is shown right in the wizard).
• An SSH key to log in to a Linux server. You can add the key to the panel in advance or generate it right in the wizard (the "SSH key" step). For Windows servers a password/RDP is used instead of a key.

Step 1. Open server creation

In the left menu open the Servers section and click the blue "+ Create cloud server" button. The wizard opens: on the left are the settings themselves, on the right is a navigation panel with the list of steps and the total cost.

Tip. On the right each item is marked with a check when it is filled in, and with an orange icon if it needs attention. The total price (UZS / month) is recalculated on the fly as you make choices.

Step 2. Placement region

Choose the site where the server will physically run. In Uzbekistan this is uz-tas1 (RegionOne). The region determines the data center location and the latency to your users.

Step 3. Operating system and image

The section is split into tabs — choose what to deploy the server from:

• OS. Clean operating systems: Ubuntu, Debian, Alma Linux, CentOS, FreeBSD, Windows, SuSE, Rocky Linux. Under each is a "Select version" drop-down (for example, for Ubuntu — 24.04, 22.04, 20.04).
• Security. Security images — this is where FortiGate (a virtual firewall) lives.
• Apps. Out-of-the-box applications: Zabbix (monitoring) and Bitrix (the 1C-Bitrix web environment).
• My images. Your own images (snapshots of previous servers). If you have none yet, the section is empty.
• Disks and volumes. Booting the server from a previously created disk/volume.

As an example we will take OS → Ubuntu → 24.04. Once selected, the image appears in the right panel as a completed step.

The administrator name depends on the image. For Ubuntu the default user is ubuntu, for other OSes it is its own (for example debian, almalinux). It is shown in the "Authentication" block.

Step 4. Server configuration

This is the choice of power (vCPU and RAM). Configurations are grouped into line tabs:

• Basic. Balanced "everyday" plans: from s1-1 (1 vCPU, 1 GB RAM) to s24-96 (24 vCPU, 96 GB RAM).
• CPU Line. Processor configurations (more vCPU per gigabyte of memory): c4-8 … c24-48. Suitable for CPU-bound workloads.
• Memory Line. Memory-focused configurations — for databases and applications that need a lot of RAM.
• Custom. Your own combination of vCPU and RAM if the ready options do not fit.

In the table each option shows vCPU, RAM, disk and cost in UZS/month. Reference points for the Basic line:

• s1-1 — 1 vCPU / 1 GB — 60,000 UZS/mo (minimal, for tests and light tasks).
• s1-2 — 1 vCPU / 2 GB — 75,000 UZS/mo.
• s2-4 — 2 vCPU / 4 GB — 150,000 UZS/mo (a common choice for a site/application).
• s4-16 — 4 vCPU / 16 GB — 420,000 UZS/mo and up — for heavier load.

Click the row you need — the configuration is marked in the right panel.

Step 5. Disks and volumes

Here you configure the server's boot disk. By default a 20 GB volume is created with the SSD Universal type and the boot (bootable) flag enabled. What you can change:

• Disk type. Available: NVMe Fast, SSD Universal, SSD Basic, HDD Basic — from the fastest NVMe to a budget HDD. More details in the article about disk types.
• Size (GB). Increase it for your data. The disk can be expanded later.
• Delete volume together with the VM. If enabled, deleting the server also deletes the disk. Off by default (the disk is kept).
• + Create volume / Select volume. You can add an extra disk or attach an existing one.

Step 6. Network

Defines how the server is connected to the network. By default Interface #1 is added in the public2 public network — this gives the server an external IP address. The Disable port security option is only needed in special scenarios (for example, for routing VMs) — usually it is left untouched.

Important about internet reachability. If you do not assign a security group, the panel warns: "The virtual machine is not reachable from the internet". Inbound connections (SSH, RDP, web) are opened precisely by the security group — see Step 8.

Step 7. Authentication and the SSH key

This is how you will log in to the server. The "SSH key" block has options:

• Select an existing key. If keys are already added to the account, they are shown as badges (for example "1key") — click to select.
• + Add a public SSH key. Paste the public part of your key (id_ed25519.pub or id_rsa.pub).
• + Generate an SSH key. The panel creates a new pair and offers to download the private key — store it securely.
• No SSH key. Without a key. Then access is configured with a password via cloud-init (below) — this is less secure.

There is also "Configuration via cloud-init" — you can paste a startup script (updates, package installation) or set a text administrator password.

Recommendation. Use an SSH key rather than a password: it is more secure and convenient. Without a selected key the panel will remind you that there will be nothing to connect to the server with.

Step 8. Security groups

A security group is a cloud network firewall: it decides which inbound traffic to let through to the server. Click Select security group and add the one you need. Typical ready-made groups:

• SSH — allows SSH login (port 22). Needed for a Linux server.
• ICMP — allows ping (reachability diagnostics).
• default — the project's base group.

You can select several groups at once or create your own via + Create security group (for example, open ports 80/443 for a site). Without a suitable group the server will boot but be unreachable from outside.

Step 9. Name and creation

• Placement group (optional) — if you need to spread servers across different physical nodes for fault tolerance.
• Additional parameters (optional) — service metadata (properties) for the server.
• Name. Give a clear name, for example web-prod-1 or test-ubuntu. You will find the server in the list by it.

Check the total cost in the right panel and click "+ Create server". The server appears in the list with the status Build (being deployed) and in a minute or two becomes Active, receiving a public IP address.

After creation: managing the server

Click the server name in the list — the "Overview" card opens with the key data: vCPU, RAM, type, status, IPv4 and the selected SSH key. On the left are the management sections:

• Disks and volumes, Snapshots. Managing disks and creating snapshots (backups) of the server.
• Reinstall. Recreate the server on a different image.
• Network, Security groups. Interfaces, IP and firewall rules (can be changed after creation).
• Resize. Change the configuration (vCPU/RAM) if resources run short.
• Prices, Monitoring, Logs. Cost, load charts and journals.
• Buttons at the top: >_ Console (a web console — access to the server right from the browser, even without a network), Reboot, Power off.

Next, connect to the server over SSH by its public IP — this is covered in a separate article, "Connecting to a server over SSH".

FAQ

How much does a server cost and how is money charged?

The cost of the chosen configuration is shown in the wizard in UZS / month and consists of the plan (vCPU/RAM), disk and network. In practice the charge is taken from the project balance per minute — for the actual server runtime, while the monthly price is just a reference for a fully loaded month.

Which configuration should I choose to start?

For a test or a light site s1-1 or s1-2 is enough. For a working site/application s2-4 is more commonly taken. If resources run short, the size can be increased later in the "Resize" section.

I can't connect to the server — what should I check?

Make sure a security group with the needed port is assigned (for Linux — SSH), the correct SSH key is selected and the server is in the Active status. If the network is unavailable, log in through the >_ Console in the panel.

What is a boot disk and the NVMe/SSD/HDD types?

The boot (boot) disk is the one the OS starts from. The type affects speed and price: NVMe Fast is the fastest, SSD Universal is the universal choice, HDD Basic is cheap for bulky data that is not speed-sensitive.

Can I install a ready application instead of a clean OS?

Yes. The Apps tab has ready images (Zabbix, Bitrix), and the Security tab has FortiGate. The server will boot right away with the application installed.

How do I delete a server I no longer need?

In the server card on the left choose Delete. If the "Delete volume together with the VM" flag was enabled when creating the disk, the disk is deleted too; otherwise the disk stays in the "Disks and volumes" section. Deletion is irreversible.