# Welcome to Neon Cloud Neon Cloud is a powerful cloud infrastructure platform designed for developers and businesses who need reliable, scalable computing resources without the complexity. ## What is Neon Cloud? Neon Cloud provides: * **Virtual Machines** - Deploy Linux and Windows servers in seconds * **Block Storage** - High-performance NVMe SSD storage for your data * **Networking** - Build secure, isolated networks with load balancing * **1-Click Apps** - Deploy popular applications instantly * **Data Protection** - Automated backups and snapshots ## Why Choose Neon Cloud? ### Developer-Friendly * Simple, intuitive interface * Powerful API for automation * Quick deployment times ### Reliable Infrastructure * 99.95% uptime SLA * Enterprise-grade hardware * Multiple data center locations ### Transparent Pricing * Pay only for what you use * No hidden fees * Prepaid credit system ## Getting Help * **Documentation** - You're here! Browse our guides * **Support Tickets** - Get help from our team * **API Docs** - Available at [api.neoncloud.com/api/docs](https://api.neoncloud.com/api/docs/alto#/) # About Neon Cloud Docs Welcome to Neon Cloud Docs-your guide to deploying and operating VMs, Kubernetes, networking, and storage on Neon Cloud. ## How to use this KB * **Search:** Use the search bar to jump to features, errors, or guides. * **Sections:** Get Started, Products, Platform (billing, account), Tutorials, APIs. * **Copy blocks:** Commands and tables are copyable as-is. ## Give feedback * Click **“Was this helpful?”** at the bottom of any page (if enabled) * Or email **** with page URL + suggestion ## Conventions * **Projects** are isolation boundaries for resources and access * **RBAC** uses roles per project (least-privilege) * **Snapshots** for quick rollback; **Backups** for durable retention # What’s New / Release Notes Stay up to date with improvements, bug fixes, and new features. ## Summary (recent) | Date (YYYY-MM-DD) | Area | Change | | ----------------- | ---------- | ---------------------------------- | | 2025-08-10 | Kubernetes | Added cluster autoscaling controls | | 2025-07-28 | Billing | CSV export for transactions | | 2025-07-12 | Networking | IPv6 support GA in select regions | ## Versioned notes ### 2025-08-10 * **Kubernetes:** Node pool autoscaling controls, drain-safe rollouts * **Compute:** Faster snapshot creation for NVMe Pro volumes * **Fixes:** Improved SSH key validation in Create VM ### 2025-07-28 * **Billing:** Transactions CSV export; invoice filters by project * **Support:** File attachment size raised to 25 MB > Note: Features may roll out region-wise. See the **Status Page** for maintenance updates. # Quick Links Handy shortcuts for day-to-day operations. * **Portal:** * **Status Page:** * **API Docs:** [https://api.neoncloud.com](https://api.neoncloud.com/api/docs/alto#/) * **Support:** # Platform Overview Neon Cloud provides the building blocks for modern apps—**Compute**, **Kubernetes**, **Networking**, and **Storage**—managed through a clean console and APIs.

## What you can provision | Area | What it includes | | ----------------- | ------------------------------------------------------------- | | **VMs (Compute)** | Linux/Windows instances, console, resize/rebuild, snapshots | | **Kubernetes** | Managed clusters, node pools, upgrades, kubeconfig | | **Networking** | VPCs, firewalls, public IPs, load balancers, VPN | | **Storage** | NVMe block volumes (Standard/Premium/Pro), snapshots, backups | ## Safety & governance 🛡️ * **RBAC** roles per project, **2FA** for accounts * **Quotas** and **budgets** to avoid surprises * **Audit logs** for key actions # Create Your Account This article explains how to set up your Neon Cloud account, complete KYC verification, and access your dashboard to start using cloud services. Sign up and secure your account in minutes.

## Steps ▶️ 1. **Sign up** on the portal by visiting and enter your **full name**, **phone number** and **work email** 2. **Set a** **strong password** *(Recommended: 15+ Characters with numbers, alphabets, symbols, and at least 1 uppercase alphabet)* 3. **Verify** your email via link sent to your inbox 4. Choose your account type - Individual or Organization and enter all necessary details.

5. Add **billing details** that will be used in invoices 6. Make the account activation fee of ₹1 payment. This amount will be added to your Neon Cloud Wallet when you login. 7. Complete the **KYC** steps (you can complete this later after exploring the platform) Start by clicking on "Start DIGIO KYC".

You will be redirected to DigiLocker verification page. Now click on "Proceed".

Enter your 12 digits Aadhaar number and click on "Next".

Now, enter the OTP received on your phone number that is linked to your Aadhaar and click on "Submit".

Enter your 6 digit DigiLocker PIN and click "Done".

Please cross check all your information and check the boxes for "Aadhaar Card" or "PAN Verification Record" and click on "Allow".

This might take a few seconds to verify your KYC details through DigiLocker.

If all details are verified correctly then a success message will display.

Congratulations! Your KYC is successfully verified and you may click "Done" to proceed to the next step. If the KYC status is not updated automatically, please click on "Check Status" and it should be updated within a few seconds.

Accept the Terms & Conditions and click on "Done" or "Go to dashboard". You will be now logged into the platform successfully.

8. After logging in, enable **Two-Factor Authentication (2FA)** under Profile → Authentication (Recommended to secure your account)

## KYC Verification 🪪 * **Individuals:** Verify identity using **DigiLocker KYC** (instant on success) * **Organizations:** Provide **GST/PAN** for manual verification (**24–48 hours**) * You can also complete the KYC later by navigating to **Profile → KYC** ***Please note: You will not be able to deploy any cloud services without completing your KYC verification.*** ## Troubleshooting 🛠️ * Didn’t get the email? Check spam/promotions * Use **Resend verification** if the link expired * Contact **** for help # Projects & RBAC Organize resources with **projects** and control access with **roles**.

Click on "Create New Project" and enter **project name, project description, and project purpose.** Then click on "Create Project" and the new project will be created.

This is your default project homepage where you can see all active services within that project, view/add/remove users in the project, and see the resource quota assigned to the project.

## Projects vs. Account * **Account:** Your identity, billing, and security context * **Project:** Isolation boundary for resources, quotas, and RBAC ## Users Navigate to **Profile** → **Users** and you can create/modify/delete users here and assign them to projects.

## Roles & Permissions (RBAC) Navigate to **Profile** → **Roles** and you can create new roles, modify/delete existing ones, and assign these roles and permissions to users.

When adding a new role, you can choose specific services, features, and permissions you want to assign to users in this role.

These are typical roles and permissions you can assign to you team members. *Please note these are suggestions and may vary based on industry, team size, use case, etc.* | Role | Scope | Permissions | | ------------------ | --------------- | ----------------------------------- | | Owner | Project | Full control, manage roles/quotas | | Contributor | Project | Create/update/delete most resources | | Viewer | Project | Read-only access | | Billing (optional) | Account/Project | Invoices, transactions | ## Best practices ✅ * Least-privilege roles; **Viewer** by default * Separate **billing** from **ops** access * Review **members** quarterly and rotate credentials # Virtual Infrastructure Setup and VM Deployment The following article will guide you tto create a Virtual Network, Subnet, Virtual Router etc. so that we can proceed with VM deployment in our private nework. {% stepper %} {% step %} ### **Create a Virtual Network** **Purpose & Summary:** Create a private virtual network exclusive to your project that acts like a secure switch within the cloud, enabling VMs to communicate internally without exposure. \ **Details:** This network is the foundation for VM communication and network isolation. The network should be “Up” and assigned to your project. \ **Steps:** \ Go to Networking → Networks.

Click on Virtual Networks

Click Create Network.\\ Select your project (e.g., web-project) and then Name the network (e.g., private-net).\ ![](https://1802641068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAChv0b03d6kwjavnnWlJ%2Fuploads%2FRhOzzFNGXn1cesPKhme9%2Fimage.png?alt=media\&token=3aeade36-b43f-453c-b23a-ee01ceca08ac) After filling the details click on Create.
{% endstep %} {% step %} ### **Add a Subnet** Under the network we just created, we now need to create a subnet.

**Purpose & Summary:** \ Define a subnet within your virtual network that specifies the IP address range your VMs will use, e.g., 192.168.50.0/24. \ Configure DHCP to automatically assign IP addresses and specify DNS servers for name resolution. \ **Details:** \ The subnet determines the IP range and gateway for the network. You should avoid IP \ conflicts with your existing networks.\ **Steps:** \ When creating your network, proceed to add a subnet. \ Provide: \ Subnet Name (e.g., private-subnet) \ Network Address (CIDR), e.g., 192.168.50.0/24 \ Gateway IP (usually 192.168.50.1) \ Enable or disable DHCP as per your setup (default enabled) \ Add DNS Nameservers (8.8.8.8, 1.1.1.1)

{% endstep %} {% step %} ### **Create a Virtual Router** **Purpose & Summary:** \ Set up a virtual router to enable routing between your private network and external networks (such as the internet), acting as a Layer 3 device managing traffic flow. \ **Details:** \ The router must be active (Admin State: Up) and assigned to your project. \ **Steps:** \ Navigate to Networking → Routers.

Click Create New, Select the Project, name the server (e.g., internet-router) and then click on Review and Create.

{% endstep %} {% step %} ### **Attach Subnet to Router** **Purpose & Summary:** \ Connect the subnet to the router by adding the subnet interface to allow VMs on that subnet to route traffic outside the private network. \ **Details:** \ This links your private subnet with external networks via the router. **Steps:** \ Open your newly created router (internet-router). \ Go to the Interfaces tab. \ Click Add Interface. \ Select your subnet (e.g., private-subnet). \ Confirm the interface addition

{% endstep %} {% step %} ### **Create a Security Group (Restrict by IP)** **Purpose & Summary:** \ Configure a security group to control inbound and outbound traAic to your VM, acting like a virtual firewall. \ Restrict SSH access to your specific public IP for security. \ **Details:** \ Default security usually denies inbound access; explicitly allow needed ports and IP ranges. \ **Steps:** \ Go to Network → Security Groups.

Create a new group called (e.g., ssh-only).

Upon Submission, click on the name of the particular Security Group and add an ingress rule: \ Protocol: TCP \ Optionally add a description \ Port Range: 22 (SSH) \ Remote IP Prefix: Your public IP with /32 mask (e.g., 203.0.113.25/32) \ Optionally, add rules for HTTP (80) and HTTPS (443) if hosting web apps. \ **Tip:** \ Find your public IP at whatismyipaddress.com.

{% endstep %} {% step %} ### **Launch a Virtual Machine (Instance)** **Purpose & Summary:** \ Deploy a virtual machine in your environment with the OS, compute resources, network, and security settings defined. \ **Details:** \ Select an image (Linux/Windows), an VM plan for CPU/RAM sizing, and upload/select an SSH key or set a password for access. Attach the VM to the private network and security group. \ **Steps:** \ Navigate to Virtual Machines → Instances (VMs).\\ Click Create Instance.

Provide: \ Compute Offering (e.g., GP1.micro)\ OS Image (e.g., Ubuntu 22.04)

Disk Offering (e.g., Standard NVMe 10 GB)\ Network: Attach to your private network (private-net).\ Security Group: Select the group you created (e.g., ssh-only).\ Key Pair: Upload or select your SSH public key (ssh-rsa \ AAAAB3NzaC1...your-key...) or define a strong password. \ Startup Script: If you have start script while provisioning VM.\ Monitoring: Enable/Disable

Server Name & Server Hostname (e.g., web-server)\ Review & Deploy the VM.

{% endstep %} {% step %} ### **Allocate and Assign a Floating IP** **Purpose & Summary:** \ Assign a floating (public) IP to your VM to enable internet access, mapping a public IP to the VM’s private address. \ **Details:** \ Floating IPs provide NAT (network address translation) so your VM can be accessed externally without exposing its internal IP. \ **Steps:** \ Go to Networking → Floating IPs.

If you don't have any existing public IPs, Buy one.

Allocate a new floating IP. \ Associate it with your VM instance (e.g., web-server). {% endstep %} {% step %} ### **Final Notes** After deploying, test connectivity by SSHing to the floating IP. \ Verify security group rules to ensure only intended ports/IPs are open. {% endstep %} {% endstepper %} # Connecting to the VM Once you have deployed the VM, you can go through this article as it describes ## Connect ▶️ 1. **Open ports:** Allow SSH (22) or RDP (3389) in firewall rules 2. **Connect:** One way to access the VM/Instance is directly through the Neon Cloud Portal. In the portal, navigate to the Instances tab, then click the three dots on the far right of the desired instance, and select Console Access.

Another way to access the console is by clicking on the name of the desired instance and then selecting the Console Access tab.

### SSH (Linux/macOS) ```bash ssh -i ~/.ssh/id_rsa ubuntu@ ``` ### PowerShell (Windows → SSH) ```powershell ssh -i C:\Keys\id_rsa ubuntu@ ``` ### RDP (Windows Server) * Launch **Remote Desktop Connection** * Connect to `` as **Administrator** * Change the default password after first login # Production Checklist A quick pre-flight list for going live. * [ ] **RBAC & 2FA**: least-privilege roles, all admins on 2FA * [ ] **Network**: security groups tight; expose only needed ports * [ ] **Backups**: policies configured and tested restores * [ ] **Snapshots**: before major updates * [ ] **Monitoring**: CPU/mem/disk/net alerts enabled * [ ] **Quotas/Budgets**: review limits and forecasts * [ ] **Runbook**: document incidents, contacts, and SLAs # Resetting your VM Password This article explains how to reset the password of a VM in Neon Cloud. {% stepper %} {% step %} ### Access Reset Option Navigate to **Instances**, select the desired instance, and go to **VM Settings → Reset Password**.

{% endstep %} {% step %} ### Set New Password Enter the new password and click on **Save** to apply the changes. **Note:** Ensure you use a strong password and update any saved credentials or scripts that rely on the previous password. {% endstep %} {% endstepper %} # Increasing Your Account Limits and Resource Quotas If you need more resources than your default quotas allow, you can request an account limit increase. This guide explains how to submit your request and track its approval. Click on your Profile and then select "Account Limits":

After that you will be guided to a new "Quota" page from where you can select the specific service for which you wish to increase the quota for and hence raise a request for the same by clicking on "Request to Increase".

Once the request is submitted, our backend team will be notified and will take the necessary action. # Taking VM Snapshots This article explains how to take VM snapshots, which capture the current state of your machine for easy restoration if needed. To take a snapshot of your VM from the **Instances** tab - select the specific VM, go to **Options > VM Snapshots > Create Snapshot**

Name the snapshot as you want to and then Confirm.

Once the snapshot creation is complete, you can find it listed under the “Snapshots” section on the left-hand panel.

# Scheduling Backups This article outlines the steps to schedule automated backups for your instances or volumes in Neon Cloud. {% stepper %} {% step %} ### Navigate to **Backups** from the dashboard and then click on **Create New**

{% endstep %} {% step %} ### Configure Backup Details Select the **Project**, choose the **Instance or Volume** for which you want to schedule the backup.

Set the **Backup Interval** (e.g., daily or weekly), and specify the **preferred time** for the backup and then click on **Create** to finalize.

{% endstep %} {% endstepper %} # Transitioning Your Instances from Hourly to Monthly Billing Cycle This article explains how to transition your instances from an hourly to a monthly billing cycle in Neon Cloud while ensuring data safety and continuity. **Important Note:** Neon Cloud does not support direct conversion of an existing instance from hourly to monthly billing. To avoid data loss, you must first create a snapshot of your current VM. {% stepper %} {% step %} ### Take a Snapshot of the Existing VM As described in the [*Taking a VM Snapshot*](https://docs.neoncloud.com/common-issues/taking-vm-snapshots) article, create a snapshot of your instance to preserve its current state. {% endstep %} {% step %} ### Verify Snapshot Completion Ensure the snapshot is successfully created and available under the **Snapshots** section.

{% endstep %} {% step %} ### Deploy a New Instance from Snapshot Use the created snapshot to launch a new VM.

While deploying the instance, you will find the **Snapshot** option under the **Choose Image** section.

{% endstep %} {% step %} ### Select Monthly Billing While deploying the new instance, choose the **monthly billing cycle** as per your requirement, review and then deploy the VM.

{% endstep %} {% endstepper %} # Expanding Instance Block Storage This article explains how to increase the block storage of an instance in Neon Cloud. {% stepper %} {% step %} ### Resize Block Storage: Navigate to **Instances**, select the desired instance, go to **VM Settings → Block Storage**, click on the **Resize Block Storage** icon

{% endstep %} {% step %} ### Configure Storage Choose the plan as **Custom**, enter the required storage size, select the billing cycle, and click on **Submit**.

{% endstep %} {% step %} ### Reboot the Instance Once the block storage expansion is successful, reboot the instance to ensure the changes take effect.

{% endstep %} {% endstepper %} # Attaching Additional Block Storage to your Instance This article explains how to attach additional block storage to an instance in Neon Cloud. {% stepper %} {% step %} ### Initiate Creation Navigate to the **Block Storage** tab on the console and click on **Create New**

{% endstep %} {% step %} ### Select Resources Choose the **Project** and the specific **Instance** to which you want to attach the block storage.

{% endstep %} {% step %} ### Configure Storage Select the **Source Type** (choose *No Image* for new block storage), define the required storage size based on your needs and IOPS, and assign a name.

{% endstep %} {% step %} ### Tiers & performance | Tier | Baseline IOPS/GB | Good for | | ------------- | ---------------- | ---------------------------------------- | | **Standard** | 10 | General-purpose apps, web servers | | **Premium** | 20 | Databases and higher I/O workloads | | **Pro** | 30 | Latency-sensitive or sustained heavy I/O | | {% endstep %} | | | {% step %} ### Finalize Setup Select the billing cycle and click on **Create** to attach the block storage.

{% endstep %} {% step %} #### Reboot the Instance Once the block storage is successfully attached, reboot the instance to ensure the changes take effect.

{% endstep %} {% endstepper %} # Upgrading your VM Configuration This article explains how to upgrade your VM to a higher configuration in Neon Cloud. #### **Important Note:** Instances can only be **upgraded to higher configurations**. Downgrading to a lower configuration is currently not supported. Steps are as follows: {% stepper %} {% step %} ### Access Plan Change Option Navigate to **Instances**, select the desired instance, and go to **VM Settings → Change Plan**.

{% endstep %} {% step %} ### Configure Upgrade Select the required VM configuration, confirm the billing cycle, review the changes, and click on **Change Plan** to proceed.

{% endstep %} {% step %} #### Reboot the Instance Once the instance is successfully upgraded, reboot the instance to ensure the changes take effect.

{% endstep %} {% endstepper %} # AI Tools This guide explains how to set up your AI tool on a pre-configured Neon Cloud Server. All dependencies are pre-installed, you only need to add your AI provider API key to get started.

OpenClaw for Windows 2022 Server

OpenClaw is a personal AI assistant that runs on your own server and connects to messaging platforms like WhatsApp, Telegram, Slack, Discord, and more. It enables you to interact with AI models through your preferred communication channels. As a prerequisite for OpenClaw, we would suggest you have an API key from an AI provider such as Anthropic, OpenAI, OpenRouter, or Google. #### Initial OpenClaw Configuration Once connected to your VM, you'll configure OpenClaw with your API key. Open PowerShell as Administrator 1. Right-click the Start button 2. Select 'Windows PowerShell (Admin)' or 'Terminal (Admin)' 3. Click 'Yes' when prompted by User Account Control #### Configure OpenClaw In the PowerShell window, run the OpenClaw configuration wizard: ``` openclaw configure ``` The wizard will guide you through the setup process. Follow these steps: 1. Select AI Provider: Choose your AI provider 2. Enter API Key: Paste your API key when prompted 3. Select Model: Choose your preferred model 4. Confirm Settings: Review and confirm your configuration Alternative: Manual Configuration (If you prefer to manually edit the configuration file): 1. Navigate to: C:\Users\Administrator.openclaw 2. Open openclaw\.json in Notepad or your preferred text editor 3. Add your API key to the configuration: ``` { "models": { "providers": { "anthropic": { "apiKey": "sk-ant-YOUR-API-KEY-HERE" } }, "defaults": { "provider": "anthropic", "model": "claude-sonnet-4-20250514" } } } ``` 4. Save the file and close the editor #### Starting OpenClaw Services After configuration, start the OpenClaw gateway service: ``` openclaw gateway start ``` You should see output indicating the gateway is starting. Look for messages like: \ ⦁ "Gateway starting on port 18789" \ ⦁ "Successfully connected to Anthropic API" \ ⦁ "OpenClaw is ready" **Verify Service Status** \ To check if OpenClaw is running correctly: ``` openclaw gateway status ``` The output should show "Status: Running"

# Business Analytics

OpenCart on Ubuntu 22.04

**Getting Started After Deploying OpenCart:** After your first SSH login to the VM or launching the VM console (via the 1-Click OpenCart deployment), access the OpenCart web installer by visiting: ``` http:///opencart/upload ``` Click "**Continue**" to begin the installation process. 1. **Enter Database Connection Details**\ When prompted, fill in the following:\ ⦁ DB Driver: MySQLi\ ⦁ Hostname: localhost\ ⦁ Database Username: opencartuser\ ⦁ Database Password: password!\ ⦁ Database Name: opencart (assumed; create if not exists)\ ⦁ Database Prefix: oc\_\ ⦁ Port: 3306 2. **Set Up Admin Credentials**\ Create an administrator username and password that you’ll use to manage your OpenCart store.\ Click "Continue" to finalize the setup. 3. **Access the OpenCart Admin Panel**\ Once installation is complete, log in to your OpenCart dashboard: ``` http:///opencart/admin ``` 4. **Use the admin credentials you just created to log in.**

# Web Hosting Control Panels

Webmin on Ubuntu 22.04

**Accessing the Webmin Interface**\ To log in to Webmin, open your browser and visit: ``` https://:10000 ``` Use the following credentials:\ Username: root or any sudo-enabled user\ Password: Your system user’s password **Note**: You may receive a security warning due to a self-signed SSL certificate. You can safely proceed to the page.

WordPress on Ubuntu 22.04

**Getting Started After Deploying WordPress:** After your first SSH login to the VM or launching the VM console (via the 1-Click WordPress deployment), open your browser and navigate to: ``` http:/// ``` Follow the WordPress setup wizard and enter the following database details when prompted:\\ **Database Name:** wordpress\ **Database Username:** wpuser\ **Database Password:** password!\ **Database Host:** localhost Next, set your WordPress admin username and password, complete the installation, and then log in at: ``` http:///wp-admin/ ```

Plesk on Ubuntu 22.04

**Getting Started After Deploying Plesk**\\ \ When you first log in to your Plesk VM via SSH or the VM console (after using the 1-Click deployment), you'll see a Message of the Day (MOTD). This message includes important details such as the default admin password. **Plesk IP Configuration & Admin Password** Refresh IP List\ To refresh the IP list in Plesk, run: ``` sudo plesk bin ipmanage --reread ``` **Remove a Specific IP**\ To remove an IP address (e.g., 10.1.1.65) from Plesk, run: ``` sudo plesk bin ipmanage --remove 10.1.1.65 ``` **Set a New Admin Password** To set a new admin password, use the following command: ``` sudo plesk bin admin --set-password -passwd YourNewPassword ``` Replace YourNewPassword with a secure password of your choice. **Accessing the Plesk Login Panel** Once the admin password is set, you can log in to your Plesk panel by visiting: ``` https://your-server-ip:8443 ``` Be sure to replace your-server-ip with the actual IP address of your VM.

Plesk on Windows-server-2022.SE

**Step 1: Initial Setup** Command Line Access & Web Interface\ To access the Plesk web interface, open your browser and navigate to: ``` https://:8443 ``` 1. Log in with your **Windows Administrator credentials**. 2. Accept the license agreement. 3. Create your **Plesk admin account**. 4. Enter your **Plesk license key** (or request a trial license from Plesk). **Step 2: Post-Installation** * Update system components (Tools & Settings → Updates). * Install extensions as needed (e.g., WordPress Toolkit, Docker, Security Advisor). * Add your first domain and hosting plan. **Access Plesk Panel trough the folllowing URL:** ``` https://:8443 ``` **Username**: admin (or your custom one)\ **Password**: The one you set during installation

PhpMyAdmin on Centos-9/Ubuntu 22.04/24.04

**Getting Started After Deploying PhpMyAdmin.**\\ \ **PhpMyAdmin MOTD**\ On your first SSH login to the VM or launch of the VM console of your PhpMyAdmin VM 1-Click; you will be greeted by a message of the day which includes the admin password for your PhpMyAdmin instance:\\ \ **PhpMyAdmin passwords location**\ If for any reason, you are unable to access the message of the day, you can get the admin password by simply\ Reading the /root/.neoncloud\_password file in your VM:\\ \ **PhpMyAdmin login screen**\ With an admin password, you can now access your PhpMyAdmin instance, by visiting: ``` http:///phpmyadmin Username: my_admin Password: password ```

# Monitoring and Visualization Here is the list of monitoring and visualization tools currently available on Neon Cloud. You can also find the supported OS for each tool, along with a post-installation guide to assistance

App	Description	Min Requirements	Supported OS
Grafana	Grafana is an open-source analytics and visualization platform used to monitor and explore metrics, logs, and other time-series data.	1 CPU, 2GB RAM	Ubuntu 22.04
Prometheus	Prometheus is an open-source monitoring system and time-series database used to collect, store, and query metrics from systems, applications, and services.	2 CPU, 4GB RAM	Ubuntu 22.04
Uptime Kuma	Uptime Kuma is a self-hosted monitoring tool that checks the availability of websites, servers, APIs, or any networked service and alerts you when something goes down.	1–2 vCPUs, 200–300 MB,	Ubuntu 24.04

Grafana

With the admin password set, you can now access your Grafana instance by visiting: **Admin URL: http\://\:3000** Use the default credentials to sign in: · Username: admin · Password: admin After logging in for the first time, you will be prompted to set a new password for security purposes.

Prometheus

**Command Line Access & Web Interface** To access the Prometheus web interface, open your browser and navigate to: http\://\:9090 This will bring up the Prometheus dashboard where you can run queries, monitor metrics, and manage your monitoring setup.

Uptime Kuma

To access Uptime Kuma, open your browser and navigate to: **http\://\:3001**\ On your first visit, you’ll be prompted to set an admin username and password to complete the setup.

Zabbix

Zabbix is an open-source enterprise monitoring solution for networks, servers, VMs, cloud services, and applications, offering real-time monitoring, alerting, visualization, and reporting. #### Accessing the Zabbix Web Interface Make sure you have the public IP address of your Zabbix VM instance Open the Zabbix Interface 1. Open your web browser 2. Navigate to the following URL (replace with your actual IP): ``` http://your_server_ip/zabbix ``` Example: If your VM IP is 203.0.113.45, you would access: and you should see the Zabbix login page with the welcome message In order to login on the Zabbix login page, you'll see fields for Username and Password. 1. Enter the username: Zabbix 2. Enter the password: 3. Click the 'Sign in' button #### Database Access (SQL) If you need to access the MySQL/MariaDB database directly for advanced configuration or troubleshooting, use these credentials: Database Name: MySQL \ Username: root \ Password: **Verify Installation** After logging in, check the server status in the bottom-right corner: "Zabbix server is running"

# Development and Automation Tools

Node.js on Ubuntu 22.04

To Install dependencies: ``` sudo apt install -y curl software-properties-common ``` Then add Node.js Repository ``` curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash – ``` Install Node.js & npm ``` sudo apt install -y nodejs ``` Verify installation ``` node -v npm –v ``` On your first SSH login to the VM or via the VM console (using the Node.js 1-Click deployment), Node.js will be pre-installed and ready for development or production use.

VS Code on Ubuntu 22.04

On your first SSH login to the VM or launch of the VM console via the VS Code 1-Click deployment: Install x11-apps on the VM and use MobaXterm (on Windows) to enable GUI access over SSH. Once set up, you can launch VS Code from the command line using:\ code This opens the VS Code GUI in your local X11 session over SSH.

Coolify on Ubuntu 22.04

**Command Line Access & Web Interface**\ To access the Coolify web interface, open your browser and navigate to: ``` http://:8000 ```

Docker on Ubuntu 22.04

Run Docker Without Sudo (Optional): ``` sudo usermod -aG docker $USER ``` Upon your first SSH login to the VM or when launching the VM console via the Docker 1-Click deployment, your environment is ready to begin running Docker containers.

GitLab on Ubuntu 24.04

On your first SSH login to the GitLab VM (or via the VM console, if using a 1-Click deployment), you can reset the root password using the command line. **Reset GitLab Root Password**\ **Launch the GitLab Rails console:** ``` sudo gitlab-rails console ``` **Run the following commands:** ``` user = User.find_by_username('root') user.password = 'NewStrongPassword123!' user.password_confirmation = 'NewStrongPassword123!' user.save! ``` **Exit the console:** ``` exit ``` Then on your browser (on your local machine), go to: ``` http:// ```

Dokploy on Ubuntu 24.04

To access Dokploy open your browser and navigate to: ``` http://your-ip-from-your-vps:3000 ``` You will see the **Setup the Server** screen (as shown below). This step is required to create the **first administrator account** for your Dokploy instance. **Steps to Register:** 1. **Name** → Enter your full name or identifier. 2. **Email** → Provide a valid email address (this will be your login username). 3. **Password** → Set a strong password. 4. **Confirm Password** → Re-enter the password to confirm. 5. Click **Register**. Once registered, you’ll be redirected to the **Dokploy Dashboard** where you can start: * Managing projects * Deploying applications * Configuring environments * Monitoring logs

Jenkins on Ubuntu24.04

**Getting Started After Deploying Jenkins** Unlocking Jenkins After Installation\ Once Jenkins is installed and running, open your browser and go to: ``` http://:8080 ``` You’ll see the **Unlock Jenkins** screen. To ensure Jenkins is securely set up, it requires an **initial administrator password**. **Steps to Unlock Jenkins:** Locate the password file on your server: ``` sudo cat /var/lib/jenkins/secrets/initialAdminPassword ``` Copy the long alphanumeric password displayed in the terminal. Paste it into the **Administrator password** field on the Jenkins web page. Click **Continue**. **Next Steps:** You’ll be asked to install **recommended plugins** or choose specific ones. Then, create your **first Jenkins admin user**. Once complete, Jenkins will be ready for you to configure jobs, pipelines, and integrations.

# Databases This guide provides step-by-step instructions to help users set up databases and manage access directly on virtual machines using console access or SSH tools like PuTTY. Below is a list of all supported databases along with their compatible operating systems. You can click on each tab to view more details.

MYSQL [Ubuntu 24.04/22.04]

**Create User & Database, Then Run Security Script** **Step 1: Run the Security Script** ``` sudo mysql_secure_installation ``` You’ll be prompted to: * Set a root password (if not already set) * Remove anonymous users * Disallow remote root login * Remove the test database * Reload privilege tables > **Tip**: Press `Y` to accept the recommended security settings. **Step 2: Log In to MySQL** With the admin password set, you can now access your MySQL instance by running the following command: ``` sudo mysql -u root -p ``` * **Username**: `root` * **Password**: *(enter the password you set in Step 1)*

MYSQL [Alma Linux 9.5/ 8.5]

**Create User & Database, Then Run Security Script** **Run the MySQL Security Script:** ``` sudo mysql_secure_installation ``` You’ll be prompted to: * Change the root password * Remove anonymous users * Disallow remote root login * Remove the test database * Reload privilege tables **Tip**: Press `Y` to accept the recommended security settings. **Log In to MySQL** ``` mysql -u root -p ``` Enter the root password you set during the security script. **Configure MySQL for Remote Access** ``` sudo nano /etc/my.cnf ``` Find the line with `bind-address` and change it to: ``` bind-address = 0.0.0.0 ``` Save and exit the file. **Restart MySQL Service** ``` sudo systemctl restart mysqld ``` **Open MySQL Port in Firewall** ``` sudo firewall-cmd --permanent --add-service=mysql sudo firewall-cmd --reload ``` **Verify MySQL Access** ``` sudo mysql -u root -p ``` Username: root\ Password: (your admin password)

PostgreSQL [Ubuntu 24.04]

**Create User & Database** ``` sudo -i -u postgres createuser --interactive createdb mydatabase ``` **Or via SQL:** ``` psql CREATE USER myuser WITH PASSWORD 'mypassword'; CREATE DATABASE mydb OWNER myuser; \q ``` **Optional: Enable Remote Access** ``` sudo nano /etc/postgresql/16/main/postgresql.conf Set: listen_addresses = '*' sudo nano /etc/postgresql/16/main/pg_hba.conf Add: host all all 0.0.0.0/0 md5 sudo systemctl restart postgresql ```

MariaDB [Ubuntu24.04/22.04]

**Create User & Database, Then Run Security Script** **Run the Security Script** ``` sudo mysql_secure_installation ``` You’ll be prompted to: * Set a root password (if not already set) * Remove anonymous users * Disallow remote root login * Remove the test database * Reload privilege tables **Tip**: Press `Y` to accept the recommended security settings. **Log In to MariaDB** ``` sudo mariadb -u root -p ``` Username: root\ Password: (enter the password you set above) **Enable Remote Access (Optional)** ``` sudo nano /etc/my.cnf ``` Locate the `bind-address` line and update it to: ``` bind-address = 0.0.0.0 ``` Save and exit the file. **Restart MariaDB Service** ``` sudo systemctl restart mysqld ``` **Open MariaDB Port in Firewall** ``` sudo firewall-cmd --permanent --add-service=mysql sudo firewall-cmd --reload ```

MongoDB [Ubuntu 24.04/22.04]

**In order to start and enable service:** ``` sudo systemctl enable mongod sudo systemctl start mongod sudo systemctl status mongod ``` With an admin without password you can now access your MongoDB instance, run command. **Launch the MongoDB Shell** ``` mongosh ``` **View Available Databases** Once inside the shell, run: ``` show databases; ``` **Expected Output:** ``` admin 40.00 KiB config 12.00 KiB local 72.00 KiB ``` **Exit the MongoDB Shell** Press `Ctrl + Z` to exit the shell and return to the command prompt. **For secure access to Mongo DB (Optional)** **Step 1: Start MongoDB Shell** ``` mongosh ``` **Step 2: Switch to `admin` Database** ``` use admin ``` **Step 3: Create an Admin User with Password** Replace `YourStrongPassword123!` with your own strong password. ``` db.createUser({ user: "admin", pwd: "YourStrongPassword123!", roles: [ { role: "root", db: "admin" } ] }) ``` **Step 4: Enable Authentication** Edit the MongoDB config file: ``` sudo nano /etc/mongod.conf ``` Find the section: ``` #security: ``` Uncomment and enable: ``` security:authorization: enabled ``` Save and exit (`CTRL+O`, `CTRL+X`). **Step 5: Restart MongoDB** ``` sudo systemctl restart mongod ``` **Step 6: Log in with Password** Now you must use your username and password: ``` mongosh -u admin -p YourStrongPassword123! --authenticationDatabase admin ```

MongoDB [Alma Linux 9.5/8.10]

**In order to start and enable service:** ``` sudo systemctl enable mongod sudo systemctl start mongod sudo systemctl status mongod ``` **Open Firewall (Optional for remote access):** ``` sudo firewall-cmd --zone=public --add-port=27017/tcp --permanent sudo firewall-cmd –reload ``` With an admin without password you can now access your MongoDB instance, run command. **Launch the MongoDB Shell** ``` mongosh ``` **View Available Databases** Once inside the shell, run: ``` show databases; ``` **Expected Output:** ``` admin 40.00 KiB config 12.00 KiB local 72.00 KiB ``` **Exit the MongoDB Shell** Press `Ctrl + Z` to exit the shell and return to the command prompt. **For secure access to Mongo DB (Optional)** **Step 1: Start MongoDB Shell** ``` mongosh ``` **Step 2: Switch to `admin` Database** ``` use admin ``` **Step 3: Create an Admin User with Password** Replace `YourStrongPassword123!` with your own strong password. ``` db.createUser({ user: "admin", pwd: "YourStrongPassword123!", roles: [ { role: "root", db: "admin" } ] }) ``` **Step 4: Enable Authentication** Edit the MongoDB config file: ``` sudo nano /etc/mongod.conf ``` Find the section: ``` #security: ``` Uncomment and enable: ``` security:authorization: enabled ``` Save and exit (`CTRL+O`, `CTRL+X`). **Step 5: Restart MongoDB** ``` sudo systemctl restart mongod ``` **Step 6: Log in with Password** Now you must use your username and password: ``` mongosh -u admin -p YourStrongPassword123! --authenticationDatabase admin ```

Redis Server [Ubuntu24.04/22.04] / AlmaLinux 9.5/8.10

You can access your Redis instance using the default admin user without a password. To verify connectivity and run basic commands, please follow the steps below: **Launch the Redis CLI:** ``` redis-cli ``` **At the prompt, test the connection by running:** ``` ping ``` You should see the response: ``` PONG ``` To exit the Redis CLI, simply type: exit

LAMP [Ubuntu24.04/22.04]

**Getting Started After Deploying LAMP** **LAMP MOTD** On your first SSH login to the VM or launch of the VM console of your PhpMyAdmin VM 1-Click; you will be greeted by a message of the day which includes the admin password for your PhpMyAdmin instance: **LAMP passwords location** If for any reason, you are unable to access the message of the day, you can get the admin password by simply reading the /root/.neoncloud\_password file in your VM: **PhpMyAdmin login screen** With an admin password, you can now access your PhpMyAdmin instance, by visiting: ``` http:///phpmyadmin ``` Username → admin\ Password → StrongPass123!

# Security Tools

NethServer on Rocky Linux 9.5

Once the installation is complete, you can access the web UI at: visiting Admin URL i.e. https\://\/cluster-admin/ Use the default credentials: **Username**: admin **Password**: Nethesis,1234 You'll be prompted to create a cluster or join an existing one. Change your default admin password immediately

# Storage and Sharing # Kubernetes # Concepts & Limits (Neon Kubernetes Engine) Neon Kubernetes Engine (NKE) provides **managed Kubernetes** with versioned control planes and node pools. > Insert screenshot of **Kubernetes → Clusters** here ## Key concepts 💡 * **Cluster:** Managed control plane with one or more **node pools** * **Node pool:** Set of worker nodes sharing the same size/image * **Versioning:** Supported K8s releases with scheduled deprecation * **Networking:** VPC-attached; supports LoadBalancers and Ingress * **Storage:** CSI-backed persistent volumes from block storage tiers ## Typical limits (example) | Item | Default | Notes | | -------------------- | ------------ | --------------------------- | | Clusters per project | 5 | Per region | | Nodes per cluster | 50 | Across all pools | | Node pool count | 10 | Per cluster | | PV size | Up to 10 TiB | Depends on tier | | K8s versions | N, N-1 | Oldest retired periodically | > Actual limits may vary by region/plan; see **Quotas**. # Create a Cluster Provision an NKE cluster with the right networking and node pool sizing. ## Steps ▶️ 1. **Project & region**: select placement 2. **Version**: choose a supported Kubernetes release 3. **Networking**: pick **VPC/subnet**; enable public LB if required 4. **Node pool**: size (vCPU/RAM), count (min/max if autoscale), OS image 5. **Storage**: enable CSI; default **StorageClass** → NVMe tier 6. **Create** and download **kubeconfig** ## Sizing tips 📏 * Start **3 nodes** for HA control-plane integrations and disruptions * Separate pools for **system** vs **workloads** * Use larger nodes for CPU-bound apps; memory-optimized for caches # Access Your Cluster (kubeconfig) Connect using a generated **kubeconfig**. > Insert screenshot of **Cluster → Access / Download kubeconfig** here ## Use kubeconfig ```bash # Save file as ~/.kube/config or use --kubeconfig export KUBECONFIG=~/Downloads/neon-kubeconfig kubectl cluster-info kubectl get nodes -o wide kubectl get pods -A ``` > Rotate kubeconfig on team changes. Prefer **short-lived tokens** where available. # Add/Resize Node Pools, Upgrades & Maintenance Scale capacity, roll upgrades safely, and keep clusters healthy. > Insert screenshot of **Cluster → Node Pools** here ## Node pools * **Add** a pool for new workload types * **Resize** by changing **node size** (create new pool → migrate pods) * **Scale** count or enable **autoscaling** (if available) ## Upgrades * **Control plane** upgrade from cluster settings * **Rolling node upgrades**: cordon/drain, recreate nodes ```bash kubectl cordon && kubectl drain --ignore-daemonsets --delete-emptydir-data ``` ## Maintenance * Recycle nodes periodically to pick up kernel/runtime patches * Keep versions within **N / N-1** # Ingress & Load Balancing Expose services using **type=LoadBalancer** or an **Ingress** controller. > Insert screenshot of **Service → type=LoadBalancer** and **Ingress** here ## Service (LoadBalancer) ```yaml apiVersion: v1 kind: Service metadata: name: web spec: type: LoadBalancer ports: - port: 80 targetPort: 8080 selector: app: web ``` * Allocates an **external IP** on the LB * Health checks map to backend pod endpoints ## Ingress (HTTP/S) * Use a controller (e.g., Nginx/HA proxy class) * TLS via secrets or cert manager * Supports **host/path** routing, canaries via annotations # Persistent Storage for K8s (CSI) Bind PersistentVolumeClaims (PVCs) to Neon block storage via **CSI** with mapped tiers. > Insert screenshot of **StorageClasses** here ## Storage classes * `neon-standard` (10 IOPS/GB), `neon-premium` (20 IOPS/GB), `neon-pro` (30 IOPS/GB) ## PVC example ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: data-pvc spec: accessModes: [ "ReadWriteOnce" ] storageClassName: neon-premium resources: requests: storage: 100Gi ``` > Resize PVCs where supported; extend filesystem in the pod after expansion. # Cluster Monitoring & Logs Track health for clusters, nodes, and workloads; inspect logs for troubleshooting. > Insert screenshot of **Cluster → Monitoring** here ## Metrics * **Cluster overview**: API health, etcd, scheduler * **Node**: CPU, memory pressure, disk/inode usage * **Workloads**: pod restarts, resource requests vs usage ## Logs ```bash # View logs kubectl -n logs deploy/ --tail=200 # Recent events kubectl get events -A --sort-by=.lastTimestamp ``` * Export charts/CSV where available for reports # Best Practices (HA, security, cost) Practical guidance for reliable and efficient clusters. ## High availability 🛡️ * Use **multiple node pools** across zones (if supported) * Run **≥3 nodes** for production workloads * Prefer **stateless** services; use readiness/liveness probes ## Security 🔐 * Enforce **RBAC** and least-privilege * Apply **NetworkPolicies**; restrict egress where possible * Keep clusters at **N / N-1**; patch base images regularly * Store secrets in a secure provider; rotate tokens/certs ## Cost 💰 * Right-size requests/limits; use **HPA/VPA** * Autoscale node pools; scale to zero for dev jobs if supported * Choose storage **tiers** to match I/O needs # Raising a Support Ticket If you happen to face any difficulty or need help, you can visit this page for guidance on how to raise a Support Ticket from your portal. Our Support team will respond to you as soon as possible. {% stepper %} {% step %} #### **Click on the Support tab in the dashboard**

{% endstep %} {% step %} #### Choose the required fields accordingly from the drop down menu Select the type of ticket and the specific service associated with your request.\ Then, choose the severity level (**High**, **Medium**, or **Low**) according to the nature and urgency of your request.

{% endstep %} {% step %} #### Enter the Subject and briefly explain the issue in the ticket content Scroll down in the "Raise Ticket" section and fill the required details:\ ![](https://1802641068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAChv0b03d6kwjavnnWlJ%2Fuploads%2F1DpJjlN0apA5zUQ4vpGE%2Fimage.png?alt=media\&token=735d0407-93c5-4689-ae0c-e1ea741b1842) {% endstep %} {% step %} #### Attach the relevant files and Submit You can attach screenshots of the error or issue you are experiencing for reference, and then click on the Submit tab. **NOTE:** When creating your support ticket, please include the following details: A clear summary of the issue and its impact\ The affected project, region, or resources\ Timestamps, error messages, and request IDs (if available)\ Attachments such as logs, screenshots, or configuration files (please ensure any sensitive information is redacted)\ ![](https://1802641068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAChv0b03d6kwjavnnWlJ%2Fuploads%2FI6rNDzD1osjJKaBlBsMj%2Fimage.png?alt=media\&token=6f1fd1d3-f112-42da-8791-35e741dd7163) {% endstep %} {% step %} #### Upon Submission: As soon as you Submit the Ticket with all the details, a ticket number is generated and our support team is notified about the same.\ ![](https://1802641068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAChv0b03d6kwjavnnWlJ%2Fuploads%2FyQLbrXyG8U6yN0NdU1zo%2Fimage.png?alt=media\&token=ba4e6726-0d9e-496a-8256-2a855c0ee501) You will receive a prompt response once our Support team identifies a relevant solution for your query. Additionally, you can reply on the same ticket if you wish to provide any further details or updates. {% endstep %} {% endstepper %}