Cantech Cloud

Blog

  • Managing Kubernetes Clusters

    1. Overview

    Users can deploy ready-to-use Kubernetes clusters with persistent storage for managing containerized applications.
    Only users who have access to the related Project can create and manage Kubernetes clusters.

    2. Create a Kubernetes Cluster

    Step 1: Start Cluster Creation

    1. Go to the Kubernetes Clusters screen.
    2. Click Create.
    3. A window will open where you can configure the Kubernetes cluster.

    K8S

    Step 2: Configure Basic Settings

    Enter or select the following:

    • Cluster Name
    • Kubernetes Version
    • SSH Key

    cluster

    Step 3: Configure the Network

    In the Network section, select the network that will connect the Kubernetes nodes.

    If you select a virtual network, choose the required floating IP configuration.

    Network

    None

    If you select None, you will not have access to the Kubernetes API.

    For Kubernetes API

    A floating IP address will be assigned to:

    • The master node, or
    • The load balancer if the master node uses High Availability.

    For Kubernetes API and Nodes

    Floating IP addresses will be assigned to:

    • The Kubernetes API.
    • Master nodes.
    • Worker nodes.

    You can also choose whether to enable High Availability for the master node.

    If High Availability is enabled, three master node instances will be created and will operate in Active/Active mode.

    Step 4: Configure the Master Node

    In the Master Node section, select a flavor for the master node.

    For production Kubernetes clusters, it is strongly recommended to use a flavor with at least:

    • 2 vCPUs
    • 8 GiB RAM

    master

    You can also enable Integrated Monitoring.

    When enabled, the following monitoring components are automatically deployed:

    • Prometheus
    • Alertmanager
    • Grafana

    Step 5: Configure Container Volumes

    In the Container Volume section:

    1. Select a storage policy.
    2. Enter the required volume size for the master and worker nodes.

    volume

    Step 6: Configure the Default Worker Group

    In the Default Worker Group section:

    1. Select a flavor for each worker node.
    2. Configure the required number of worker nodes.
    3. Choose whether to enable Autoscaling.

    Autoscaling Enabled

    When Autoscaling is enabled:

    • Worker nodes are automatically added if pods remain in a pending state because of insufficient resources.
    • Worker nodes are automatically removed when they have no pods running.
    • Configure the minimum and maximum number of workers.

    Autoscaling Disabled

    When Autoscaling is disabled, the configured number of worker nodes remains fixed.

    Step 7: Configure Labels

    In the Labels section, enter additional Kubernetes cluster parameters using the following format:

    key=value

    Example:

    selinux_mode=permissive

    Currently supported labels are:

    • selinux
    • flannel_network_cidr

    Labels

    Step 8: Create the Cluster

    Click Create.

    The Kubernetes cluster creation process will begin.

    After creation:

    • Master and worker nodes will appear on the Virtual Machines screen.
    • Their storage volumes will appear on the Volumes screen.

    After the cluster is ready, click Kubernetes Access to view instructions for accessing the Kubernetes dashboard.

    You can also access the master and worker nodes through SSH using the assigned SSH key and the username core.

    3. Access Kubernetes Nodes Using SSH

    To access a Kubernetes node, run:

    Bash
    ssh -i <private-key> core@<IP-address>

    Replace:

    <private-key> with the path to your private key file.
    <IP-address> with the public IP address of the VM.

    Note: Verify the required port accessibility from your network or firewall if needed.

    4. Delete a Kubernetes Cluster

    To delete a Kubernetes cluster:

    1. Go to the Kubernetes Clusters screen.
    2. Select the required Kubernetes cluster.
    3. Click Delete.

    The master and worker Virtual Machines will be deleted along with their volumes.

    delete

    5. Managing Kubernetes Worker Groups

    Kubernetes worker groups allow you to use worker nodes with different CPU and RAM configurations based on application requirements.

    When creating a Kubernetes cluster, you can configure only one worker group called the Default Worker Group.

    After the cluster is created, you can:

    • Add additional worker groups.
    • Use different configurations for each worker group.
    • Change the number of workers in each group.

    Note: The Default Worker Group cannot be deleted.

    6. Add a Worker Group

    Step 1: Open the Worker Groups

    1. Go to the Kubernetes Clusters screen.
    2. Select the required Kubernetes cluster.
    3. Open the Groups tab.
    4. In the Workers section, click Add.

    worker node

    Step 2: Configure the Worker Group

    In the Add Worker Group window, enter a name for the group.

    Workers

    In the Worker Group section:

    1. Select a flavor for each worker.
    2. Choose whether to enable Autoscaling.

    Autoscaling Enabled

    The number of workers will automatically increase when pods remain pending because of insufficient resources.

    Workers will be reduced when there are worker nodes with no pods running.

    Configure the minimum and maximum worker group size.

    Autoscaling Disabled

    The number of worker nodes you configure will remain fixed.

    Step 3: Configure Labels

    Enter additional parameters using the following format:
    key=value

    Example:
    selinux_mode=permissive

    Currently supported labels are:

    • selinux
    • flannel_network_cidr

    Other labels can be used at your own risk. Refer to the OpenStack documentation for the complete list of supported labels.

    Step 4: Add the Worker Group

    Click Add.

    After the worker group is created, pods can be assigned to these worker nodes as explained in Assigning Kubernetes Pods to Specific Nodes.

    7. Change the Number of Workers

    To modify the number of worker nodes:

    1. Open the Kubernetes cluster.
    2. Go to the Groups tab.
    3. In the Workers section:
      • Click the pencil icon for the Default Worker Group.
      • For other worker groups, click the ellipsis (⋯) and select Edit.
    4. In the Edit Workers window:
      • Enable or disable Autoscaling, or
      • Change the number of worker nodes.
    5. Click Save.

    Edit worker

    8. Delete a Worker Group

    To delete a worker group:

    1. Click the ellipsis (⋯) next to the required worker group.
    2. Select Delete.

    The worker group and all of its worker nodes will be deleted.

    Note: After deletion, the worker group data will be lost.

    9. Updating Kubernetes Clusters

    When a new Kubernetes version becomes available, you can update the cluster.

    Worker nodes are updated one at a time to maintain data availability.

    The Kubernetes API will be unavailable during the update unless High Availability is enabled for the master node.

    Before starting the update, ensure that the compute cluster has enough resources and quota for at least one additional VM using the largest flavor configured in the Kubernetes cluster.

    If the master and worker nodes use different flavors, consider the largest flavor when checking available resources.

    10. Kubernetes Update Limitations

    The following limitations apply:

    • Kubernetes clusters running versions 1.15.x to 1.17.x cannot be updated to newer versions.
    • Kubernetes can be updated only one minor version at a time.
      Example:
      1.28 → 1.29 → 1.30
    • Node groups can have only a one-minor-version difference.
      Example:
      1.29 and 1.30
    • Kubernetes 1.29 clusters can be updated to 1.30 only if they were created using the Cilium network plugin.
    • Kubernetes clusters cannot be managed through the self-service panel while an update is in progress.

    11. Update a Kubernetes Cluster

    Step 1: Select the Cluster

    Select a Kubernetes cluster that displays the Update Available tag.

    Step 2: Start the Update

    On the Kubernetes cluster pane, click Update in the Kubernetes Version field.

    Step 3: Select the Kubernetes Version

    In the Update window:

    1. Select the Kubernetes version you want to update to.
    2. Follow the provided link to review API resources that are deprecated or obsolete in the selected version.
    3. Click Next.

    Step 4: Select the Update Type

    Choose one of the following options:

    Update All

    Select Update All to update all node groups in the Kubernetes cluster.

    Custom Update

    Select Custom Update to update only specific node groups.

    The master node group is automatically selected and is required for the update.

    Step 5: Confirm the Update

    Click Confirm.

    The Kubernetes cluster update process will begin.

    If different node groups are running different Kubernetes versions, the cluster status will change to Partially Updated.

    In this state, new worker groups will use the same Kubernetes version as the master node group.

    To complete the cluster update, repeat the update process for any worker groups that are still running an older Kubernetes version.

  • How to access Linux VM from Windows and Linux

    Accessing a Linux VM from Windows

    You can connect to a Linux virtual machine from a Windows system using SSH (Secure Shell) or Remote Desktop Protocol (RDP) if a graphical interface is installed.

    Requirements

    Before connecting, ensure you have the following:

    • The IP address of the Linux virtual machine.
    • The SSH service is installed and running on the VM (default SSH port: 22).
    • A valid username and password, or an SSH private key if key-based authentication is configured.

    Method 1: Connect Using PuTTY (SSH Client)

    Step 1: Install PuTTY

    Download the latest version of PuTTY from the official website and install it on your Windows computer.

    Step 2: Launch PuTTY

    Open the PuTTY application.

    • Enter the IP address of your Linux VM in the Host Name (or IP address) field.
    • Verify that the Port is set to 22.
    • Keep the connection type as SSH.

    Launch PuTTY

    Step 3: Establish the Connection

    Click Open.

    The first time you connect, PuTTY will display the server’s SSH fingerprint.

    Click Accept (or Yes) to continue.

    Step 4: Authenticate

    When prompted:

    • Enter the Linux username (for example, root or another user).
    • Enter the corresponding password.

    If you are using SSH key authentication, configure your private key by navigating to:

    Connection → SSH → Auth

    Then browse and select your .ppk private key file.

    Establish the Connection

    Method 2: Connect Using Windows Terminal or PowerShell

    Step 1: Open Windows Terminal

    Launch Windows Terminal, PowerShell, or Command Prompt.

    Step 2: Connect Using SSH

    Execute the following command:

    Bash
    ssh username@<Linux_VM_IP>

    Replace:

    • username with your Linux account name.
    • <Linux_VM_IP> with the IP address of the virtual machine.

    Example:

    Bash
    ssh root@192.168.1.1

    Step 3: Login

    Enter the password when prompted.

    If SSH key authentication is configured, ensure your private key is located in the default Windows SSH directory:

    Bash
    C:\Users\<username>\.ssh\

    Login SSH

    Method 3: Connect Using Remote Desktop (GUI Access)

    If your Linux VM has a desktop environment installed, you can connect through Remote Desktop.

    Step 1: Install XRDP on the Linux VM

    Update the package list and install XRDP

    Bash
    sudo apt update
sudo apt install xrdp

    Step 2: Enable the XRDP Service

    Start the service and enable it to launch automatically after reboot.

    Bash
    sudo systemctl enable –now xrdp

    Step 3: Open Remote Desktop Connection

    On your Windows machine:

    • Open Remote Desktop Connection.
    • Enter the Linux VM IP address.
    • Click Connect.

    Step 4: Sign In

    Provide your Linux username and password to access the graphical desktop.

    Connecting from one Linux system to another is simple using SSH. You can also use SCP for secure file transfers.

    Requirements

    Before connecting, verify that:

    • You know the Linux VM’s IP address.
    • SSH is installed and active on the VM.
    • You have valid login credentials or an SSH key.

    Method 1: Connect Using SSH

    Step 1: Open the Terminal

    Launch the Terminal application on your Linux computer.

    Step 2: Run the SSH Command

    Use the following command:

    Bash
    ssh username@<Linux_VM_IP>

    Example:

    Bash
    ssh ubuntu@192.168.1.100

    Step 3: Authenticate

    Enter your password when prompted.

    If you are using an SSH key, verify that the key exists in your local SSH directory.

    Example:

    Bash
    ~/.ssh/id_rsa

    Ensure the private key has the correct permissions.

    Bash
    chmod 600 ~/.ssh/id_rsa

    Method 2: Access Using Cockpit (Web Interface)

    Cockpit provides a browser-based interface for managing Linux systems.

    Step 1: Install Cockpit

    Log in to your Linux VM using SSH and install Cockpit.

    For Ubuntu/Debian:

    Bash
    sudo apt update
sudo apt install cockpit -y

    For RHEL, Rocky Linux, AlmaLinux, or CentOS:

    Bash
    sudo dnf install cockpit -y

    Step 2: Enable and Start the Cockpit Service

    Enable the Cockpit socket so that it starts automatically during system boot, and then start the service.

    Bash
    sudo systemctl enable cockpit.socket
sudo systemctl start cockpit.socket

    Verify that the Cockpit socket is running.

    Bash
    sudo systemctl status cockpit.socket

    Step 3: Allow Port 9090 Through the Firewall (Optional)

    If your firewall is enabled, allow access to TCP port 9090.

    Ubuntu (UFW):

    Bash
    sudo ufw allow 9090/tcp
sudo ufw reload

    RHEL/Rocky/AlmaLinux:

    Bash
    sudo firewall-cmd –permanent –add-service=cockpit
sudo firewall-cmd –reload

    Step 4: Verify Cockpit is Listening

    Run the following command to verify that Cockpit is listening on port 9090.

    Bash
    sudo ss -tulnp | grep 9090

    Expected output:

    Bash
    LISTEN 0 4096 *:9090

    Step 5: Open Cockpit in a Web Browser

    On your Windows or Linux computer, open your preferred web browser and enter the following URL:

    Bash
    https://<Linux_VM_IP>:9090

    Step 6: Log In to Cockpit

    On the Cockpit login page, enter your Linux VM credentials.

    Log In to Cockpit

    Cockpit Login Successfully

    Troubleshooting

    Connection Refused

    If you cannot establish an SSH connection:

    Check whether the SSH service is running.

    Bash
    sudo systemctl status ssh

    If necessary, start the service.

    Bash
    sudo systemctl start ssh

    Ensure the firewall permits SSH traffic.

    Bash
    sudo ufw allow ssh

    Authentication Failed

    If login fails:

    • Verify the username and password.
    • If using an SSH key, confirm the correct private key is selected.
    • Make sure the private key permissions are set properly.
    Bash
    chmod 600 ~/.ssh/id_rsa

    Timeout Issues:

    • Verify the Linux VM is running and accessible via the network.
    • Check network configurations and routes.

  • Assign Multiple Secondary IPs on Different Operating Systems

    Assign Multiple Secondary IPs on Different Operating Systems

    Linux (RHEL / CentOS / Alma Linux / Rocky Linux)

    Method 1: Permanent Configuration (Alma Linux 8/9, Rocky Linux 8/9)

    Edit the network configuration:

    Bash
    nmcli connection modify eth0 +ipv4.addresses 192.168.1.101/24
nmcli connection modify eth0 +ipv4.addresses 192.168.1.102/24
nmcli connection modify eth0 +ipv4.addresses 192.168.1.103/24
nmcli connection up eth0

    Verify:

    Bash
    nmcli connection show eth0
ip addr show eth0

    Ubuntu 20.04 / 22.04 / 24.04

    Edit Netplan configuration:

    Bash
    nano /etc/netplan/00-installer-config.yaml

    Example:

    Bash
    network:
version: 2
ethernets:
ens18:
addresses:
– 192.168.1.100/24
– 192.168.1.101/24
– 192.168.1.102/24
– 192.168.1.103/24
gateway4: 192.168.1.1
nameservers:
addresses:
– 8.8.8.8
– 1.1.1.1

    Apply:

    Bash
    netplan generate
netplan apply

    Verify:

    Bash
    ip addr

    Debian 11 / 12

    Edit:

    Bash
    nano /etc/network/interfaces

    Example:

    Bash
    
auto ens18
iface ens18 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.1
auto ens18:0
iface ens18:0 inet static
address 192.168.1.101
netmask 255.255.255.0
auto ens18:1
iface ens18:1 inet static
address 192.168.1.102
netmask 255.255.255.0
auto ens18:2
iface ens18:2 inet static
address 192.168.1.103
netmask 255.255.255.0

    Restart networking:

    Bash
    systemctl restart networking

    Assign Multiple Secondary IPs on Windows Server 2016 / 2019 / 2022 / 2025

    Method:  GUI Method

    • Open Network Connections
    • Right-click Network Adapter → Properties
    • Select Internet Protocol Version 4 (TCP/IPv4) → Properties
    • Click Advanced
    • Under IP addresses, click Add
    • Add each secondary IP:
      192.168.1.101
      192.168.1.102
    • Click OK

    PowerShell Method

    PowerShell
    New-NetIPAddress -InterfaceAlias “Ethernet” -IPAddress 192.168.1.101 -PrefixLength 24
New-NetIPAddress -InterfaceAlias “Ethernet” -IPAddress 192.168.1.102 -PrefixLength 24
New-NetIPAddress -InterfaceAlias “Ethernet” -IPAddress 192.168.1.103 -PrefixLength 24

    Verify:

    PowerShell
    Get-NetIPAddress

     

     

     

     

     

  • How to Install and Secure OpenClaw (Moltbot) on a Cloud Server

    1. Overview

    This guide explains how to deploy and secure OpenClaw (Moltbot) on a Cloud Virtual Machine.

    By following this guide, you will:

    • Choose the appropriate Cloud plan.
    • Create a Virtual Machine.
    • Install OpenClaw.
    • Connect messaging channels.
    • Secure the installation for production use.

    2. System Requirements

    RequirementMinimumRecommended
    CPU1 vCPU2 vCPU
    Memory (RAM)1 GB4–8 GB
    Storage500 MB20–30 GB
    Operating SystemLinux (any)Ubuntu 22.04 or 24.04 LTS
    RuntimeNode.js 22+Node.js 22 LTS
    NetworkPublic IPv4Public IPv4 + Firewall

    3. Create the Virtual Machine

    1. Log in to the Cloud dashboard.
    2. Navigate to Compute → Create VM.
    3. Select the required plan.
    4. Choose Ubuntu 22.04 LTS or Ubuntu 24.04 LTS.
    5. Add an SSH key or configure a root password.
    6. Create the Virtual Machine.
    7. Note the public IP address after deployment.

    4. Install OpenClaw

    Step 1: Update the System

    Bash
    sudo apt update && sudo apt upgrade -y
curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash – && sudo apt install -y nodejs

    Step 2: Configure Corepack

    Bash
    corepack enable
corepack prepare pnpm@latest –activate
pnpm setup
source ~/.bashrc

    Step 3: Install npm

    Bash
    npm install -g npm@11.8.0
Verify the installation:
node –version
npm –version

    Step 4: Install Docker

    Bash
    curl -fsSL https://get.docker.com | sudo sh
sudo usermod -aG docker $USER

    Verify Docker:

    Bash
    docker –version

    Step 5: Install OpenClaw

    Bash
    curl -fsSL https://openclaw.ai/install.sh | bash

    Verify the installation:

    Bash
    openclaw –version

    Open claw

    Set up

    Step 6: Run the Initial Configuration

    openclaw onboard

    Follow the prompts to configure:

    • AI provider
    • API key
    • Basic settings

    Setup

    Setup

    6. Connect Communication Channels

    Telegram

    1. Open Telegram.
    2. Search for @BotFather.
    3. Run /newbot.
    4. Copy the bot token.
    5. Paste the token when prompted by OpenClaw.

    WhatsApp

    Run:

    Bash
    openclaw channels login whatsapp

    A QR code is displayed.

    Open WhatsApp on your phone:

    Linked Devices → Link a Device

    Scan the QR code to complete the connection.

    Configure the allowed users:

    channels:
    whatsapp:
    allowFrom:
    – “+91XXXXXXXXXX”
    – “+91XXXXXXXXXX”

    Slack

    Create a Slack application.

    Enable Socket Mode.

    Configure the required Bot Token and App Token.

    Add the tokens to the configuration:

    channels:
    slack:
    botToken: “xoxb-your-bot-token-here”
    appToken: “xapp-your-app-token-here”

    Gmail

    Configure Gmail by:

    • Creating a Google Cloud project.
    • Enabling the Gmail API.
    • Enabling the Pub/Sub API.
    • Creating a Service Account.
    • Creating a Pub/Sub topic and subscription.
    • Adding the credentials path to the OpenClaw configuration.

    7. Secure the Installation

    Enable Docker Sandboxing

    Configure:

    agents:
    defaults:
    sandbox:
    mode: “non-main”

    Configure the Cloud Firewall

    Create firewall rules to:

    • Allow SSH only from trusted IP addresses.
    • Block the gateway port from public access.
    • Deny all other inbound traffic by default.

    Configure UFW

    Bash
    sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow ssh
sudo ufw enable
sudo ufw status

    Access the Dashboard

    Create an SSH tunnel:

    Bash
    ssh -L 18789:localhost:18789 moltbot-user@your-server-ip

    Open:
    http://localhost:18789/

    If a gateway token is required, run:

    Bash
    openclaw dashboard –no-open

    Use the generated URL to access the dashboard.

    Configure Allowed Users

    Example:

    channels:
    whatsapp:
    allowFrom:
    – “+91XXXXXXXXXX”

    slack:
    allowUsers:
    – “U01XXXXXXXX”

    Enable Automated Backups

    Open the Cloud dashboard.

    Navigate to:

    Virtual Machine → Backups

    Enable automated backups.

    Run the Health Check

    Bash
    moltbot doctor

    8. Run OpenClaw as a Service

    Create the systemd service:

    Bash
    sudo tee /etc/systemd/system/openclaw.service

    Reload systemd:

    Bash
    sudo systemctl daemon-reexec
sudo systemctl daemon-reload

    Enable and start the service:

    Bash
    sudo systemctl enable openclaw
sudo systemctl start openclaw

    Verify the service:

    Bash
    sudo systemctl status openclaw

    View the logs:

    Bash
    journalctl -u openclaw -f

    9. Troubleshooting

    WhatsApp QR Code Does Not Appear

    Verify that Node.js 22 or later is installed.

    Bash
    node –version

    Slack Bot Does Not Respond

    Verify that:

    • Socket Mode is enabled.
    • Bot Token and App Token are configured correctly.

    High Memory Usage

    If multiple communication channels are enabled with browser automation, consider upgrading the Virtual Machine to a larger plan.

    Health Check Shows Warnings

    Run:

    Bash
    moltbot doctor

    Review each warning and apply the recommended corrections.

  • How to create Virtual Machines from Advance Panel

    Cloud delivers a flexible and scalable cloud infrastructure that helps you deploy virtual machines based on your workload requirements. Whether you’re hosting applications, building development environments, or performing testing and data analysis, you can quickly create and manage Windows virtual machines through the Cloud platform.

    If you want to create a Windows Virtual Machine using the standard Cloud Dashboard, refer to the relevant documentation.

    To deploy a Windows Virtual Machine using the Cloud Advanced Dashboard, follow these instructions.

    Step 1: Open the Advanced Dashboard

    Log in to your Cloud account.

    Navigate to the required region and click the arrow icon to open the Region Advanced Dashboard. From this dashboard, you can deploy, configure, and manage your virtual machines.

    Open the Advanced Dashboard

    Step 2: Start Creating a Virtual Machine

    Click the + Create Virtual Machine button.

    This opens the virtual machine deployment wizard where you can configure all required settings before launching the instance.

    Start Creating a Virtual Machine

    Step 3: Configure the Virtual Machine

    Enter the Virtual Machine Name

    Provide a unique and meaningful name for your virtual machine.

    You can customize additional settings such as:

    • Image
    • Boot Volume
    • Flavor
    • Network Interface

    To modify any of these options, click the Edit (Pencil) icon next to the respective section.

    Configure the Virtual Machine

    Option 1: Deploy Using an Existing Volume

    Deploying from a volume allows you to launch a virtual machine using an existing boot volume that already contains an operating system, installed software, and stored data.

    This option is useful when you want to:

    • Restore a previously used virtual machine.
    • Move an existing operating system to another VM.
    • Keep all current applications, configurations, and data intact.

    Steps

    • Click the Pencil icon beside the boot source.
    • Select Attach Boot Volume.
    • Choose the required boot volume from the list.
    • Click Attach.

    The selected volume will now become the boot disk for the virtual machine.

    Deploy Using an Existing Volume

    Option 2: Deploy Using an Image

    Creating a virtual machine from an image installs a fresh operating system using a predefined image, similar to installing Windows on a new computer.

    This method is recommended when creating a completely new virtual machine.

    Deploy Using an Image

    Select the Operating System Image

    Choose the operating system image you want to use from the available image library.

    If you have previously uploaded a custom image, you can select it from the Custom Images section.

    After selecting the image, click Done.

    Note

    If you want to use your own ISO image, you can upload it.

    For more information about uploading images, refer to the Image Management documentation.

    Select the Operating System Image

    Select the Virtual Machine Flavor

    Choose a flavor based on the amount of computing resources your virtual machine requires.

    The selected flavor determines:

    • Number of vCPUs
    • RAM allocation
    • Other hardware resources

    Ensure that the selected flavor satisfies the minimum hardware requirements of the operating system you selected.

    Once you’ve chosen the appropriate flavor, click Done.

    Example

    Certain Windows Server editions require additional CPU cores and memory. Always verify that your selected flavor provides enough resources for smooth operation.

    Select the Virtual Machine Flavor

    Configure the Network Interface

    Inside the Add Network Interface window, select the compute network that the virtual machine should connect to.

    By default, a primary Public IP address is assigned automatically.

    If you prefer assigning a specific Public IPv4 address manually:

    • Uncheck Assign Automatically.
    • Enter the preferred Public IPv4 address.
    • Select the desired Public IP from the dropdown list.
    • Click Add.

    Recommendation

    Assign a Public IP address during the initial deployment to simplify remote access and avoid future connectivity issues.

    Configure the Network Interface

    Add Secondary IP Addresses (Optional)

    You can also configure additional IP addresses if required.

    Unlike the primary IP address, secondary IP addresses are not configured automatically inside the Windows operating system.

    After deployment, you must configure these additional addresses manually within the guest operating system.

    Configure Private Networking (Optional)

    If your virtual machine requires a Private IP address, you must first create a Virtual Private Network (VPN).

    Once the VPN is available, you can attach the virtual machine to the private network.

    Refer to the VPN documentation for complete setup instructions.

    Security Group Configuration

    If the selected network has IP Address Management enabled:

    • Spoofing Protection is enabled automatically.
    • The Default Security Group is applied automatically.

    The default security group permits both inbound and outbound traffic to the virtual machine.

    After reviewing the settings, click Done.

    Add an SSH Public Key

    Click Add SSH Key if you want to use SSH key-based authentication.

    Select or upload the public SSH key that was generated on the computer from which you plan to access the virtual machine.

    For additional information, refer to the SSH Key Authentication guide.

    Add an SSH Public Key

    Step 4: Advanced Configuration (Optional)

    Add a Customization Script (User Data)

    You can provide User Data to perform automatic configuration tasks immediately after the virtual machine starts.

    User Data may be supplied as:

    • A cloud-init YAML configuration file
    • A shell script containing commands to execute during the first boot

    This feature is useful for installing software packages, configuring services, or applying system settings automatically.

    Add a Customization Script

    Enable CPU and RAM Hot Plug

    The CPU and RAM Hot Plug feature allows you to increase or modify CPU and memory resources while the virtual machine is running.

    Because these changes can be applied without restarting the virtual machine, you can scale resources with minimal disruption and avoid downtime.

    Step 5: Deploy the Virtual Machine

    After reviewing all configuration settings, click Deploy.

    Cloud will begin provisioning your Windows virtual machine.

    Once deployment is complete, the virtual machine is created successfully and is ready for use.

    Deploy the Virtual Machine

    Manage the Virtual Machine

    To view or manage the virtual machine:

    • Navigate to the Virtual Machines section.
    • Click the name of the newly created virtual machine.

    From the VM details page, you can monitor its status, manage resources, configure networking, and perform other administrative tasks.

  • How to create Windows Virtual Machines from Advance Panel?

    Introduction

    CMP delivers a flexible and scalable cloud infrastructure that helps you deploy virtual machines based on your workload requirements. Whether you are hosting applications, building development environments, or performing testing and data analysis, you can quickly create and manage Windows virtual machines through the CMP platform.

    If you want to create a Windows Virtual Machine using the standard CMP Dashboard, refer to the relevant documentation.

    To deploy a Windows Virtual Machine using the CMP Advanced Dashboard, follow the instructions below.

    Main Content

    Step 1: Open the Advanced Dashboard

    Log in to your CMP account.

    Navigate to the required region and click the arrow icon to open the Region Advanced Dashboard.

    From this dashboard, you can deploy, configure, and manage your virtual machines.

    Open the Advanced Dashboard

    Step 2: Start Creating a Virtual Machine

    Click the + Create Virtual Machine button.

    This opens the virtual machine deployment wizard where you can configure all required settings before launching the instance.

    Start Creating a Virtual Machine

    Step 3: Configure the Virtual Machine

    Enter the Virtual Machine Name

    Provide a unique and meaningful name for your virtual machine.

    You can customize additional settings such as:

    • Image
    • Boot Volume
    • Flavor
    • Network Interface

    To modify any of these options, click the Edit (Pencil) icon next to the respective section.

    Configure the Virtual Machine

    Option 1: Deploy Using an Existing Volume

    Deploying from a volume allows you to launch a virtual machine using an existing boot volume that already contains an operating system, installed software, and stored data.

    This option is useful when you want to:

    • Restore a previously used virtual machine.
    • Move an existing operating system to another VM.
    • Keep all current applications, configurations, and data intact.

    Steps

    1. Click the Pencil icon beside the boot source.
    2. Select Attach Boot Volume.
    3. Choose the required boot volume from the list.
    4. Click Attach.

    The selected volume will now become the boot disk for the virtual machine.

    selected volume

    Option 2: Deploy Using an Image

    Creating a virtual machine from an image installs a fresh operating system using a predefined image, similar to installing Windows on a new computer.

    This method is recommended when creating a completely new virtual machine.

    Deploy Using an Image

    Select the Operating System Image

    Choose the operating system image you want to use from the available image library.

    If you have previously uploaded a custom image, you can select it from the Custom Images section.

    After selecting the image, click Done.

    Note

    If you want to use your own ISO image, you can upload it.

    For more information about uploading images, refer to the Image Management documentation.

    Select the Operating System Image

    Select the Virtual Machine Flavor

    Choose a flavor based on the amount of computing resources your virtual machine requires.

    The selected flavor determines:

    • Number of vCPUs
    • RAM allocation
    • Other hardware resources

    Ensure that the selected flavor satisfies the minimum hardware requirements of the operating system you selected.

    Once you’ve chosen the appropriate flavor, click Done.

    Example

    Certain Windows Server editions require additional CPU cores and memory. Always verify that your selected flavor provides enough resources for smooth operation.

    Select the Virtual Machine Flavor

    Configure the Network Interface

    Inside the Add Network Interface window, select the compute network that the virtual machine should connect to.

    By default, a primary Public IP address is assigned automatically.

    If you prefer assigning a specific Public IPv4 address manually:

    • Uncheck Assign Automatically.
    • Enter the preferred Public IPv4 address.
    • Select the desired Public IP from the dropdown list.
    • Click Add.

    Recommendation

    Assign a Public IP address during the initial deployment to simplify remote access and avoid future connectivity issues.

    Configure the Network Interface

    Add Secondary IP Addresses (Optional)

    You can also configure additional IP addresses if required.

    Unlike the primary IP address, secondary IP addresses are not configured automatically inside the Windows operating system.

    After deployment, you must configure these additional addresses manually within the guest operating system.

    Configure Private Networking (Optional)

    If your virtual machine requires a Private IP address, you must first create a Virtual Private Network (VPN).

    Once the VPN is available, you can attach the virtual machine to the private network.

    Refer to the VPN documentation for complete setup instructions.

    Security Group Configuration

    If the selected network has IP Address Management enabled:

    • Spoofing Protection is enabled automatically.
    • The Default Security Group is applied automatically.

    The default security group permits both inbound and outbound traffic to the virtual machine.

    After reviewing the settings, click Done.

    Add an SSH Public Key

    Click Add SSH Key if you want to use SSH key-based authentication.

    Select or upload the public SSH key that was generated on the computer from which you plan to access the virtual machine.

    For additional information, refer to the SSH Key Authentication guide.

    Add an SSH Public Key

    Step 4: Advanced Configuration (Optional)

    Add a Customization Script (User Data)

    You can provide User Data to perform automatic configuration tasks immediately after the virtual machine starts.

    User Data may be supplied as:

    • A cloud-init YAML configuration file
    • A shell script containing commands to execute during the first boot

    This feature is useful for installing software packages, configuring services, or applying system settings automatically.

    Advanced Configuration

    Enable CPU and RAM Hot Plug

    The CPU and RAM Hot Plug feature allows you to increase or modify CPU and memory resources while the virtual machine is running.

    Because these changes can be applied without restarting the virtual machine, you can scale resources with minimal disruption and avoid downtime.

    Step 5: Deploy the Virtual Machine

    After reviewing all configuration settings, click Deploy.

    Cloud will begin provisioning your Windows virtual machine.

    Once deployment is complete, the virtual machine is created successfully and is ready for use.

    Deploy the Virtual Machine

    Manage the Virtual Machine

    To view or manage the virtual machine:

    • Navigate to the Virtual Machines section.
    • Click the name of the newly created virtual machine.

    From the VM details page, you can monitor its status, manage resources, configure networking, and perform other administrative tasks.

    Reset the Windows Administrator Password

    If you need to change or recover the Windows administrator password, you can perform a password reset using the VM Console.

    Refer to the Reset Windows VM Password documentation for detailed instructions.

    Connect to the Windows Virtual Machine Using RDP

    Windows virtual machines can be accessed remotely using Remote Desktop Protocol (RDP).

    If you are connecting from a Linux machine, you can use xFreeRDP, which is a lightweight and efficient Remote Desktop client.

    For complete connection instructions, refer to the Connect to Windows VM via RDP guide.

    Verification

    After deployment is complete:

    • Navigate to the Virtual Machines section.
    • Locate the newly created Windows virtual machine.
    • Click the VM name to open its details page.
    • Verify that the virtual machine has been created successfully.
    • Review the VM status, resources, and network configuration.

    The Windows virtual machine is now ready for use.

    Conclusion

    Creating a Windows Virtual Machine from the CMP Advanced Panel allows you to configure the operating system image, boot volume, flavor, network interface, security group, SSH key, and optional advanced settings before deployment.

    After reviewing the configuration, click Deploy to provision the Windows virtual machine. Once deployment is complete, you can manage the VM from the Virtual Machines section and connect to it using the available access methods.

    FAQ’s

    How do I create a Windows Virtual Machine from the CMP Advanced Panel?

    Log in to your CMP account, open the required region’s Advanced Dashboard, click + Create Virtual Machine, configure the required settings, and click Deploy.

    Can I create a Windows VM using an existing boot volume?

    Yes. Select the Pencil icon beside the boot source, choose Attach Boot Volume, select the required boot volume, and click Attach.

    Can I create a Windows VM using an image?

    Yes. Select the required operating system image from the available image library. You can also select a previously uploaded custom image from the Custom Images section.

    Can I assign a specific Public IP address during VM creation?

    Yes. In the Add Network Interface section, uncheck Assign Automatically, enter the preferred Public IPv4 address, select the desired Public IP, and click Add.

    Can I configure secondary IP addresses?

    Yes. Additional IP addresses can be configured during deployment. However, secondary IP addresses are not configured automatically inside the Windows operating system and must be configured manually after deployment.

    Can I configure a private IP address for the Windows VM?

    Yes. If the virtual machine requires a Private IP address, you must first create a Virtual Private Network (VPN). Once the VPN is available, the VM can be attached to the private network.

    Can I add an SSH public key while creating the Windows VM?

    Yes. Click Add SSH Key and select or upload the public SSH key that was generated on the computer from which you plan to access the virtual machine.

    What advanced configuration options are available?

    You can add User Data for automatic configuration tasks and enable CPU and RAM Hot Plug to modify CPU and memory resources while the virtual machine is running.

  • How to View Billing in Cantech Cloud

    Introduction:

    In the Cantech Cloud portal, billing details can be accessed through the Billing or Account section of the dashboard. Once logged in, navigate to the billing menu to see invoices, payment history, and current usage charges. The portal typically provides options to download invoices, track payment status, and manage billing methods. This helps users monitor expenses and keep accounts updated directly from the cloud interface.

    1. Log in to Cantech Cloud Dashboard

    Use your account credentials to access your Cantech Cloud account.

    2. Navigate to Billing History Section

    3. Select Billing Period

    • Choose a month to view billing for that specific month.
    • Or select a custom period to view charges for a specific date range.

     

    4. View Total Billing

    After selecting the desired period, the dashboard will display your total billing for that time frame.

    5. View Resource-wise Billing

    To see detailed billing for each resource:

    • Click on a resource to expand its details.
    • You will see the breakdown of charges per resource.

    Troubleshooting:

    • Login error → Check credentials or reset password.
    • Billing tab missing → Verify account role, clear browser cache.
    • Wrong period shown → Re‑select month/date range, refresh page.
    • Invoice not visible → Ensure billing cycle completed, contact support.
    • Payment not updated → Wait for processing, confirm with bank.
    • Resource billing not loading → Check resource activity, reload dashboard.

    Important Notes

    • Billing access may require Admin/Finance role permissions.
    • Always select the correct billing period or custom range for accurate results.
    • Invoices are generated after the billing cycle closes.
    • Payment updates may take time to reflect in the dashboard.
    • Resource‑wise billing shows charges only for active resources in the chosen period.

     

    Conclusion:

    By following these steps, users can easily access and review their billing information in the Cantech Cloud portal. The dashboard provides both a summary view of total charges and a detailed breakdown by resource, ensuring transparency and helping users track expenses effectively. This makes it simple to monitor usage, manage costs, and keep accounts up to date.

     

    FAQ’s:

    • Q: Where can I find my billing details? A: Log in to the Cantech Cloud dashboard and go to the Billing or Account section.
    • Q: Can I view billing for a specific month? A: Yes, you can select a billing period (monthly or custom date range) to see charges.
    • Q: How do I download invoices? A: In the billing section, use the Download Invoice option for the selected period.
    • Q: Why don’t I see the billing tab? A: You may need Admin/Finance role permissions. Contact your account administrator.
    • Q: Can I check billing per resource? A: Yes, expand the resource details to view a breakdown of charges.
    • Q: How long does it take for payments to reflect? A: Payments may take some time to update; check again after processing or confirm with your bank.

     

  • Cantech Cloud Billing Guide

      Introduction

    Cantech Cloud uses a Pay-As-You-Go (PAYG) billing model. You are billed based on the resources you actually use, such as compute, storage, and network services. so it is essential to monitor usage regularly to manage costs effectively.

    1. Billing Model

    Pay-As-You-Go

    Cantech Cloud is Postpaid and Usage for the month is billed on 1st of next month.

    • You are charged only for the resources you consume.
      • Storage: Volumes, snapshots, object storage
      • Network: Floating IPs, Direct IP, Routers, VPN, Load Balancers.
      • Compute: CPU cores, RAM, VM running hours

    Shelving a virtual machine (VM) essentially pauses the instance — it stops the VM from running but preserves its configuration. Think of it as “saving” the VM so you can resume it later.

    You don’t pay for the VM compute resources (CPU and RAM) while the VM is shelved. This helps reduce cost if you aren’t running the VM but want to keep it around, but the volume and direct OR floating IP attached to the VM will be charged.

    2. Alerts and Budgets

    Cantech Cloud currently does not support alerts or budgets:

    • Users cannot set limits on spending.
    • No automatic notifications if usage or costs increase.
    • It is recommended to manually monitor resource usage through the dashboard.

    3. Billing Frequency

    • Billing is done monthly.
    • Usage details and invoices are accessible in the billing dashboard.
    • Ensure that all unused VM’s are Shelved or deleted to avoid unnecessary charges.

    4. Cost Management Tips

    To manage your costs effectively:

    1. Regularly track your usage through the dashboard.
    2. Shelve or delete unused VMs and volumes.

    3. Plan resource deployments carefully.

       

      Troubleshooting:

    • High charges → Check if unused VMs are still running; shelving only stops compute, storage/IPs still billed.
    • Shelved VM billed → Verify VM is shelved (not just powered off); detach unused IPs/volumes.
    • Invoice mismatch → Compare dashboard usage with invoice; look for overlooked resources like snapshots/object storage.
    • No alerts → Manually monitor usage; set personal reminders to review dashboard.
    • Usage not updating → Refresh dashboard, clear browser cache, or confirm resources were actually deleted/shelved.

          Important Points:

    • Cantech Cloud uses a Pay‑As‑You‑Go (PAYG) postpaid model; invoices are generated on the 1st of each month.
    • Charges apply only for resources consumed: compute (CPU/RAM/VM hours), storage (volumes, snapshots, object storage), and network (IPs, routers, VPN, load balancers).
    • Shelving VMs stops compute billing but storage and IP costs continue.
    • No built‑in alerts or budgets — users must manually monitor usage.
    • To avoid extra charges, shelve or delete unused VMs/volumes and release unused IPs.
    • Usage details and invoices are always accessible in the billing dashboard.

      Conclusion:

      Cantech Cloud’s PAYG model offers flexibility by charging only for actual usage, but it requires proactive monitoring. Since there are no automated alerts or spending limits, users must regularly review the dashboard, manage unused resources, and plan deployments carefully to keep costs under control.

      FAQ’s:

      Q1. When am I billed for my usage?
      A: Cantech Cloud is postpaid. Usage for the month is billed on the 1st of the next month.

      Q2. What resources are charged under PAYG?
       A: Charges apply for compute (CPU, RAM, VM hours), storage (volumes, snapshots, object storage), and network services (floating/direct IPs, routers, VPN, load balancers).

      Q3. If I shelve a VM, do I still pay?
       A: Shelving stops compute charges (CPU/RAM), but storage and IPs attached to the VM are still billed.

      Q4. How can I reduce my monthly costs?
       A: Shelve or delete unused VMs, release unused IPs, and delete unnecessary volumes/snapshots. Regularly monitor usage in the dashboard

  • Managing Backups

    Introduction

    Cantech Cloud provides flexible backup options to protect your compute volumes. Users can choose between Full Backups, which copy the entire volume, and Incremental Backups, which only capture changes since the last backup. Backup plans allow you to define schedules, retention policies, and manage which volumes are included. By configuring backup plans correctly, you can ensure reliable recovery points while optimizing storage usage and costs.

    There are two types of backups:

    1- Full Backup : Copies the entire compute volume.
    2- Incremental Backup : Copies only the changes made since the last backup.

    To create a backup plan:

    1. Go to the Backup Plans screen and click Create Backup Plan.

    1. In the Create Backup Plan window:
    • Enter a name for the backup plan.
    • Optionally, add a description (avoid personal or sensitive information).

    1. Under What to back up, click Manage.
    • In the Manage Volumes window, select the volumes you want to include in the backup plan.
    • Click Save.

    1. Under Schedule, choose the backup schedule:
    • Retention: 7 Days – Creates a daily backup of the selected volumes and keeps up to 7 full backup chains. In this case, the max number of recovery point is 1.
    • Retention: 14 Days – Creates a daily backup of the selected volumes and keeps up to 14 full backup chains. In this case, the max number of recovery point is 2.
    • Custom Retention – Allows you to set a custom backup schedule. You can choose specific months, days of the week, days of the month, backup time, and the maximum number of full recovery points to keep.

    1. Click Create.

    To Add Volumes to a Backup Plan:

    1. Go to the Backup Plans screen and select the backup plan you want.
    2. On the right, open the Volumes to Back Up tab to see the current volumes.
    3. Click Manage above the list.
    4. In the Manage Volumes window, select the volumes you want to add.

    5. Click Save.

    To Remove Volumes from a Backup Plan:

    1. Go to the Backup Plans screen and select the backup plan you want.
    2. On the right, open the Volumes to Back Up tab to see the current volumes.
    3. Click Manage above the list.
    4. In the Manage Volumes window:

    • Uncheck the volumes you want to remove.

    • To filter and view only assigned volumes, check Show Only Selected Items near the search bar.

    5. Click Save.

      Troubleshooting

    • Backup not running → Verify schedule and retention settings; ensure volumes are correctly assigned.
    • Missing recovery points → Check retention policy (7‑day allows 1 point, 14‑day allows 2).
    • Incorrect volumes backed up → Re‑open Manage Volumes and confirm selections.
    • Backup plan changes not applied → Refresh dashboard and confirm “Save” was clicked after edits.

       Important Notes

    • Two backup types: Full (entire volume) and Incremental (changes since last backup).
    • Retention directly affects number of recovery points (7 days → 1, 14 days → 2).
    • Custom retention allows flexible scheduling (specific days/months/times).
    • Always name backup plans clearly and avoid sensitive info in descriptions.
    • Volumes can be added/removed anytime via Manage Volumes.

       Conclusion

    Backup plans in Cantech Cloud provide flexibility with full and incremental backups, but correct configuration is essential. By carefully setting retention, schedules, and managing volumes, users can ensure reliable recovery points while avoiding confusion or missed backups.

    FAQ’s:

    Q1. What types of backups are available?
    A: Two types — Full Backup (entire volume) and Incremental Backup (only changes since the last backup).

    Q2. How do I create a backup plan?
     A: Go to Backup Plans → Create Backup Plan, name it, select volumes, set schedule/retention, then click Create.

    Q3. What does retention mean?
    A: Retention defines how long backups are kept:

    • 7 days → 1 recovery point
    • 14 days → 2 recovery points
    • Custom → user‑defined schedule and recovery points.

    Q4. Can I add or remove volumes later?
     A: Yes. Use Manage Volumes in the backup plan to add or uncheck volumes, then save changes.

  • How to Add Your Own ISO Image to Cantech Cloud and create Virtual machine Using Custom Image

    Introduction

    Cantech Cloud allows you to upload custom ISOs or images to deploy virtual machines with your preferred operating systems or pre‑configured templates. This feature is ideal for migrating on‑premise setups, testing specialized environments, or maintaining consistency across deployments. By verifying the uploaded image and configuring VM settings properly, you can ensure smooth and secure provisioning..

    Step 1: Upload Your Custom Image

    1. Log in to your Cantech Cloud account.
    2. In the left-hand menu, navigate to Virtual Machines → Images.
    3. Select the region where you want to upload the image.

    4. Click Add Image.

    5. Choose your custom ISO/image file from your local system and click Add to begin the upload.



    Step 2: Verify the Uploaded Image

    1. Once the upload completes, go to Virtual Machines → Images.
    2. Confirm that your image appears in the list with status Available or Ready.
    3. If the status shows Processing, wait until the upload is complete before deploying.

    Step 3: Create a Virtual Machine Using the Custom Image

    1. Choose the same region where your image was uploaded.
    2. Navigate to Virtual Machines → Create VM
    3. From the image section, select the custom image you uploaded earlier.

    4. Configure other settings:

    Server Type: Choose the compute plan (CPU and RAM).
    Storage: Adjust the disk size
    Network: Select private/public network interfaces as needed.

    Name: Set a custom name for your Virtual Machine.

    Access: Add SSH keys or set a root password.

    Troubleshooting

    • Image not visible after upload → Refresh the Images tab; check region selection; ensure upload completed (status must be Available/Ready).
    • VM creation fails → Confirm you selected the same region as the uploaded image; verify compute/storage/network settings.
    • Upload stuck in Processing → Wait until status changes to Ready; large ISO files may take longer.
    • Cannot access VM → Ensure SSH keys or root password were set correctly during VM creation.

    Important Notes

    • Upload images under the correct region; VM creation must use the same region.
    • Status must be Available/Ready before using the image.
    • Configure VM settings carefully: CPU/RAM, disk size, and network interfaces.
    • Always set secure access credentials (SSH keys or strong root password).ConclusionUploading custom ISOs or images in Cantech Cloud enables flexibility for operating systems, templates, and migrations. Proper region selection, verification of image status, and careful VM configuration ensure smooth deployment and reliable access.

      FAQ

      Q1. Can I upload any ISO/image?
      A: Yes, as long as it’s a valid OS image or template supported by Cantech Cloud.

      Q2. Why don’t I see my uploaded image?
       A: Check the region and refresh the Images tab; ensure upload completed successfully.

      Q3. What does “Processing” status mean?
      A: The image is still uploading or being prepared. Wait until it shows Available/Ready.

      Q4. Do I need to select the same region when creating a VM?
       A: Yes, the VM must be created in the same region where the image was uploaded.

      Q5. How do I access my VM after creation?
      A: Use the SSH key or root password configured during VM setup.