How to Set Up AlexHost VPS Step by Step (2026 Guide)

Understanding how to set up alexhost vps infrastructure allows site owners, system administrators, and developers to deploy isolated computing resources across European and North American data centers. Founded in 2008 in Chișinău, Moldova, AlexHost operates its own ISO/IEC 27001-certified data center alongside multiple international points of presence, providing KVM-virtualized virtual private servers on high-speed 1 Gbps network uplinks. This comprehensive guide walks through the entire provisioning workflow, from selecting hardware resources and operating systems to establishing your first administrative connection and executing essential post-installation security hardening.
Affiliate disclosure: This article may contain affiliate links. If you buy through them, we may earn a commission at no extra cost to you. Details were checked on November 21, 2026 and can change.
Official website · Latest pricing & offers
Quick Answer: How to Set Up an AlexHost VPS

To configure and deploy a virtual private server on AlexHost, you complete a straightforward five-phase deployment process:
- Select Plan & Hardware: Choose between AMD Ryzen or Intel Xeon Platinum processor platforms, determine required RAM (available from 1 GB up to 8 GB+ tiers), and select storage types (SSD or NVMe).
- Choose Server Location: Pick your target physical location, such as Moldova (MD), the Netherlands (NL), Sweden (SE), Bulgaria (BG), Switzerland (CH), France (FR), England (EN), Romania (RO), or the United States (Las Vegas – US).
- Select Operating System or Template: Select Linux (such as Ubuntu 20.04, 18.04, 16.04, 14.04, Debian, CentOS, Fedora) or Windows (Windows Server 2012, 2016, 2019, Windows 10, Windows 11), along with optional hosting control panels like cPanel, Plesk, DirectAdmin, or ispmanager.
- Complete Checkout: Finalize billing terms (monthly, quarterly, semiannual, or yearly) using one of more than 20 supported payment methods.
- Initialize & Secure: Retrieve IP credentials from the AlexHost client area, establish a secure connection via SSH (Linux) or Remote Desktop Protocol (Windows), update core repositories, configure firewall rules, and disable insecure remote root logins.
Pre-Installation Decisions: Hardware, Locations, and Management Levels
Before launching into the technical mechanics of how to set up alexhost vps instances, you must evaluate the workload requirements of your planned deployment. AlexHost organizes its virtualization portfolio across different hardware platforms, networking profiles, and administrative oversight levels.
Virtualization Architecture and Platform Choices
AlexHost transitioned its infrastructure fully to KVM (Kernel-based Virtual Machine) virtualization in 2018. Unlike container-based virtualization environments, KVM provides true hardware virtualization where each VPS operates with its own kernel, dedicated RAM allocations, independent virtualized storage, and isolated network adapters. When navigating the official catalog, you will encounter two primary compute platforms:
- AMD Ryzen VPS (1 Gbps): High single-thread clock performance suited for interactive web applications, high-traffic CMS sites, and game or voice communication hosting like TeamSpeak or Discord bots.
- Intel Xeon Platinum VPS (1 Gbps): Multi-core compute platforms suited for enterprise databases, multi-tenant web hosting, automated trading terminals (such as MetaTrader 4, MetaTrader 5, cTrader, and NinjaTrader), and background processing workers.
Storage configurations generally include either solid-state drives (SSD) or ultra-fast Non-Volatile Memory Express (NVMe) storage arrays, which deliver high input/output operations per second (IOPS) for database-driven workloads. For a broader overview of how these compute tiers compare to bare-metal servers, consult our AlexHost Dedicated Server Guide.
Physical Data Center Locations
Network latency directly affects data transfer speeds and administrative responsiveness. AlexHost operates its primary owned facility in Chișinău, Moldova—built 5 meters underground in a former military factory bunker with 1.6 MW power capacity, redundant power feeds, and N+1 cooling infrastructure. Beyond Moldova, AlexHost offers virtual server deployment in several connected European and North American regions:
- Moldova (MD)
- Netherlands (NL)
- Sweden (SE)
- Bulgaria (BG)
- Switzerland (CH)
- France (FR)
- England (EN)
- Romania (RO)
- United States (Las Vegas, US)
AlexHost provides live ping checks on its homepage across these locations, enabling you to measure packet transit times before submitting an order. If your target audience is located primarily in Western Europe, deploying in the Netherlands, France, or England ensures minimal network hops; workloads targeting Eastern Europe benefit from facilities in Moldova, Romania, or Bulgaria.
Managed vs. Unmanaged VPS Tiers
A critical step when deciding how to structure your deployment is choosing between self-managed and fully managed tiers:
- Unmanaged VPS: The default, low-cost option. AlexHost guarantees hardware availability, physical network uptime backed by a 99.99% uptime SLA, and KVM hypervisor connectivity. All operating system configuration, software installations, security patches, firewall adjustments, and troubleshooting remain the sole responsibility of the customer.
- 24/7 Managed VPS: Intended for businesses that lack dedicated Linux system administrators. The AlexHost support staff assists with initial server setup, core configuration, control panel installations, routine security updates, and operational troubleshooting via their 24/7 ticketing system.
Choosing Operating Systems and Control Panels for Your AlexHost VPS
Operating system selection dictates the administrative tooling and commands you will use once your instance boots up. AlexHost offers a broad selection of standard operating system distributions and pre-configured templates.
| Operating System Family | Supported Versions / Editions | Primary Use Case | Default Remote Access Tool |
|---|---|---|---|
| Linux Ubuntu | Ubuntu 20.04, 18.04, 16.04, 14.04 | Web servers, microservices, bot hosting, open-source stacks | SSH (Port 22) |
| Linux Enterprise (RHEL/Debian) | Debian, CentOS, Fedora | Traditional web hosting, stability-oriented software, control panels | SSH (Port 22) |
| Windows Server | Windows Server 2012, 2016, 2019 | ASP.NET workloads, Active Directory, enterprise software, remote terminals | RDP (Port 3389) |
| Windows Desktop | Windows 10, Windows 11 | Forex automated trading (MT4/MT5/cTrader), remote workstation tasks | RDP (Port 3389) |
Note: While older distribution images such as Ubuntu 14.04 and 16.04 remain selectable in legacy provisioning lists, deploying long-unsupported operating systems poses severe security risks unless your deployment runs in complete network isolation. Modern deployments should prioritize current supported versions or inspect available package mirrors via the AlexHost client portal.
Optional Hosting Control Panels
If you prefer a graphic user interface (GUI) to manage virtual hosts, DNS records, FTP accounts, databases, and SSL certificates, AlexHost allows licensing and automated pre-installation of popular web hosting control panels during checkout:
- cPanel / WHM: Available in Premier Cloud and Admin Cloud editions, ideal for commercial multi-account web hosting.
- Plesk: Offered in Web Admin, Web Host, and Web Pro editions, well-suited for both Windows and Linux hosting environments.
- DirectAdmin: Available in Lite and Standard tiers, offering a lightweight, cost-effective alternative to cPanel.
- ispmanager: Selectable in Lite, 6 Pro, and 6 Host tiers, delivering efficient server administration with minimal resource overhead.
For an in-depth breakdown of licensing tiers, resource specifications, and recurring costs across different software bundles, refer to our detailed AlexHost Pricing Explained guide.
Step-by-Step Guide: How to Set Up AlexHost VPS from Order to First Boot
Deploying a virtual machine on AlexHost follows a clear sequence. Follow these precise steps to order, provision, and verify your new server.
Step 1: Navigate to the VPS Section and Select Your Plan
Access the official AlexHost website (alexhost.com) and navigate to the VPS menu in the main navigation bar. Depending on your operational needs, click on either the AMD Ryzen / 1 Gbps VPS or Platinum VPS / 1 Gbps category, or select one of the location-specific categories (such as Moldova VPS, Netherlands VPS, or Las Vegas VPS).
Review the memory (RAM), virtual CPU core count, and disk storage quotas displayed on the product cards. Click the Order Now button on the tier that matches your anticipated resource consumption.
Step 2: Configure Server Options and Geographical Location
Once you enter the configuration interface, you will be prompted to tailor the server’s core operational parameters:
- Billing Cycle: Select your billing cadence (1 month, 3 months, 6 months, or yearly). Longer cycles may lower administrative overhead by reducing invoice frequency.
- Location Selection: Choose your target data center location (such as Moldova, Netherlands, Sweden, Bulgaria, Switzerland, France, England, Romania, or United States).
- Management Level: Confirm whether the server will remain Unmanaged (self-managed) or Managed (with 24/7 technical administration included).
- Operating System: Select your preferred distribution (for example, Linux Ubuntu, Debian, CentOS, Fedora, or Windows Server editions).
- Control Panel Add-ons: If you require cPanel, Plesk, DirectAdmin, or ispmanager, check the corresponding licensing box. Otherwise, leave it set to basic OS installation for a clean shell environment.
Step 3: Review Order Summary and Register Account
Verify that your hardware parameters, location, and OS selections are accurate in the order summary. If you are a new customer, fill out the user registration form with your email address and primary contact details. Existing users can simply log in using their client credentials. Review the Terms of Service and Privacy Policy before proceeding.
Step 4: Complete Payment
AlexHost supports more than 20 payment methods, providing flexibility for international customers. Select your preferred payment gateway from the available options (such as credit/debit cards, bank wire transfers, or supported digital and online payment systems) and execute the transaction. Once payment is confirmed by the automated billing platform, your order shifts into the provisioning queue.
Step 5: Provisioning and Receiving Server Credentials
Because AlexHost uses automated KVM provisioning routines, deployment typically completes within minutes for standard Linux distributions. Once provisioning completes, check your registered email address for the welcome dispatch titled with your server details. You will also find these details directly inside the AlexHost Client Portal under your active services. The key connection parameters include:
- Primary Public IPv4 Address: (e.g.,
185.xxx.xxx.xxx) - Default Root / Administrator Username: (usually
rooton Linux,Administratoron Windows) - Initial System Password: A temporary, randomly generated root password
- Assigned Hostname & Nameserver Addresses: Network identity details assigned to your KVM container
First Login and Initial Administrative Access
Once your instance shows an “Active” status in the AlexHost dashboard, you can connect to the virtual machine. Your connection method depends on whether you installed a Linux distribution or Windows Server.
Accessing a Linux VPS via SSH
Linux servers are administered using the Secure Shell (SSH) protocol on default port 22. You can access the command line using native terminals on Linux/macOS or terminal clients like PuTTY or Windows Terminal on Windows.
To connect from a command prompt, run the following command, replacing the example IP address with your server’s assigned public IP address:
ssh root@185.xxx.xxx.xxx
When connecting for the very first time, your local terminal client will prompt you to verify the server’s SSH key fingerprint authenticity:
The authenticity of host ‘185.xxx.xxx.xxx’ can’t be established. ECDSA key fingerprint is SHA256:… Are you sure you want to continue connecting (yes/no/[fingerprint])?
Type yes and press Enter. Enter the root password provided in your provisioning confirmation email. When typing passwords in SSH, characters are not echoed back to the screen. Press Enter after typing or pasting your password. Upon successful validation, you will be greeted by the Linux distribution greeting banner and command prompt.
Accessing a Windows VPS via Remote Desktop Protocol (RDP)
If you selected Windows Server 2016, 2019, Windows 10, or Windows 11, administration is conducted via Remote Desktop:
- Open the Remote Desktop Connection client on your local Windows PC (search for
mstscin the Windows Start menu). macOS and Linux users can download Microsoft Remote Desktop from their respective app repositories. - In the Computer field, enter your assigned AlexHost public IPv4 address.
- Click Connect. When prompted for credentials, enter
Administratoras the username and the generated administrative password provided by AlexHost. - Accept the security certificate warning regarding the self-signed SSL/TLS certificate. The Windows desktop environment will launch within the remote window.
Recovering Access if Locked Out
If you misconfigure your local network settings, accidentally block port 22 in a firewall, or lock yourself out of administrative accounts, you do not need to reinstall the operating system. You can open a support ticket with AlexHost’s 24/7 technical support team through your client dashboard to request recovery assistance. Their support team can help you regain access and correct configuration mistakes even if standard network services are unreachable.
Basic Security Hardening and Post-Setup Configuration
A newly provisioned unmanaged server connected directly to a high-speed 1 Gbps uplink will begin receiving automated port scans and unauthorized connection attempts within hours. Securing your operating system is the most important phase when learning how to set up alexhost vps properly.
1. Synchronize Package Repositories and Apply Security Patches
Immediately update your distribution’s core package indexes and upgrade outdated system binaries. On Ubuntu and Debian systems, execute:
apt update && apt upgrade -y
On enterprise Linux distributions such as CentOS or Fedora, execute:
dnf upgrade -y
If the update process upgrades core components such as the Linux kernel or systemd libraries, reboot the server using reboot to ensure all running processes load the newly patched binaries.
2. Create a Non-Root User with Administrative Privileges
Operating permanently under the root account introduces significant operational and security vulnerabilities. Create a dedicated administrative account with sudo permissions:
adduser adminuser
Follow the terminal prompts to set a strong password. Next, grant this newly created user administrative access by appending it to the system’s sudo administrative group:
usermod -aG sudo adminuser
(On RHEL-derived distributions, replace sudo with wheel: usermod -aG wheel adminuser).
3. Configure SSH Key-Based Authentication
Password-based authentication remains susceptible to brute-force credential stuffing. SSH cryptographic keys provide vastly superior security. On your local workstation, generate an Ed25519 key pair if you do not already possess one:
ssh-keygen -t ed25519 -C "alexhost-vps-key"
Copy the public key to your new administrative user on the AlexHost instance:
ssh-copy-id adminuser@185.xxx.xxx.xxx
Test the connection in a separate terminal window to confirm passwordless key authentication works:
ssh adminuser@185.xxx.xxx.xxx
4. Harden the SSH Daemon Configuration
Once SSH key authentication is confirmed operational, disable remote root logins and disable password-based fallback authentication entirely. Open the SSH daemon configuration file using a text editor:
sudo nano /etc/ssh/sshd_config
Locate and adjust the following directives to match these values:
PermitRootLogin noPasswordAuthentication noPubkeyAuthentication yes
Optional: You may also change the standard Port 22 to an unassigned high port (such as Port 2222 or Port 54321) to eliminate noisy, automated port scans from filling your authentication logs. If you change this port, ensure you adjust your firewall configuration before restarting the SSH service!
Validate the syntax and restart the SSH daemon:
sudo sshd -t && sudo systemctl restart ssh
5. Implement an Active Host Firewall
A software firewall restricts inbound traffic strictly to authorized services. On Ubuntu and Debian systems, Uncomplicated Firewall (ufw) provides an effective interface:
- Ensure default rules reject unsolicited inbound traffic:
sudo ufw default deny incoming - Permit standard outbound traffic:
sudo ufw default allow outgoing - Permit your SSH port (replace 22 if you configured a custom port):
sudo ufw allow 22/tcp - Permit web traffic if you are running a public web server:
sudo ufw allow 80/tcp && sudo ufw allow 443/tcp - Enable the firewall service:
sudo ufw enable - Verify running status and rules:
sudo ufw status verbose
Understanding AlexHost DDoS Protection
AlexHost integrates built-in Distributed Denial of Service (DDoS) mitigation across its virtual server lines. While local software firewalls (like ufw or iptables) protect against unauthorized service access, layer 3 and layer 4 volumetric network floods (such as SYN floods, UDP amplification, or ICMP floods) are filtered upstream across AlexHost’s multi-10 Gbit/s and Tier-1 upstream network connections (including Cogent and RETN). This prevents malicious traffic spikes from saturating your VPS’s 1 Gbps virtual interface.
Pros and Cons of Deploying an AlexHost Virtual Private Server
Before standardizing your infrastructure on AlexHost, assess the inherent technical trade-offs associated with their platform.
Pros
- Independent Data Center Ownership: AlexHost owns and controls its primary bunker data center facility in Chișinău, Moldova, avoiding third-party resale layers.
- Wide Geographic Presence: Deploy across 9 distinct geographic regions (Moldova, Netherlands, Sweden, Bulgaria, Switzerland, France, England, Romania, and the US) from a single account.
- KVM Virtualization Standard: Every VPS features kernel-level isolation, independent storage controllers, and dedicated resources without noisy-neighbor RAM overselling.
- Flexible Payment Systems: Over 20 payment options supported, accommodating global customers with diverse payment preferences.
- High-Speed Connectivity: Standard 1 Gbps port connectivity across modern Platinum and Ryzen product lines.
- Support Access: Direct technical support available via 24/7 tickets, Telegram live chat, official Telegram channel, and phone (+373 79 600002).
Cons
- Self-Management Requirements: Unmanaged VPS instances require sound knowledge of the Linux or Windows command line; routine administration is not handled automatically.
- Control Panel Licenses are Paid Add-ons: Graphical interfaces such as cPanel, Plesk, DirectAdmin, or ispmanager require commercial license fees added to base server costs.
- Legacy Operating System Options Present: The provisioning catalog includes older OS images (such as Ubuntu 14.04 and 16.04) that are end-of-life upstream, requiring users to manually verify they select current, supported distributions.
Who Should Deploy AlexHost VPS (and Who Should Look Elsewhere)?
Different hosting platforms cater to different technical profiles. To understand whether AlexHost fits your specific technical and administrative workflow, consider the following matching criteria.
Best Suited For
- Developers and System Administrators: Users who want full KVM virtualization, complete root access, and the freedom to configure custom software stacks without hosting provider restrictions.
- Automated Forex and Financial Traders: The availability of Windows Server and desktop Windows editions (Windows 10/11) paired with ultra-fast connectivity makes AlexHost a common choice for running continuous trading platforms like MetaTrader 4, MetaTrader 5, cTrader, and NinjaTrader.
- Privacy-Conscious Organizations: Companies seeking hosting under Moldovan jurisdiction within a secure, privately owned underground bunker facility built to ISO/IEC 27001 standards.
- Multi-Region Projects: Operators requiring low-latency nodes distributed across Eastern Europe, Western Europe, and North America under a single provider.
Who Should Look Elsewhere
- Absolute Beginners Seeking Point-and-Click Web Hosting: If you do not want to manage operating system updates, SSH keys, or firewall rules, an unmanaged VPS will prove challenging. In that case, standard shared hosting or managed web hosting is a more suitable starting point. See our AlexHost Shared Hosting Guide for an overview of simpler hosting options.
- Users Requiring Proprietary Managed Cloud Ecosystems: If your deployment depends entirely on integrated cloud APIs, automated object storage buckets, managed Kubernetes clusters, or multi-zone VPC auto-scaling, traditional hyperscale cloud providers may be required instead of standard KVM VPS instances.
Common VPS Configuration Pitfalls and Troubleshooting
Even experienced administrators occasionally encounter hurdles during initial setup. Here are common configuration issues on AlexHost VPS instances and how to address them.
1. SSH Connection Refused or Connection Timed Out
If you cannot connect to your server immediately after receiving deployment confirmation:
- Check Server Power State: Log into the AlexHost client area and confirm the VPS status reads “Running” rather than “Provisioning” or “Stopped”.
- Verify Port Accessibility: If you altered the default SSH port in
/etc/ssh/sshd_config, ensure you specify the custom port in your command (ssh -p 2222 adminuser@185.xxx.xxx.xxx) and verify that your local software firewall allowed the port before restarting SSH. - Contact Support: If you are locked out by a misconfigured firewall rule, open a ticket with AlexHost technical support to request assistance with restoring access to your server.
2. Remote Desktop (RDP) Authentication Failures on Windows
When connecting to a Windows VPS via Remote Desktop, failure notices are commonly caused by user syntax errors:
- Ensure you are connecting with the username
Administrator(with a capital ‘A’) rather than your personal client dashboard email address. - Ensure your local firewall or ISP network does not actively filter outbound connections on TCP port 3389.
3. DNS Resolution and Reverse DNS (rDNS)
If your VPS will handle mail transfer agents (MTA) or send automated transactional emails, you must configure reverse DNS (rDNS / PTR record) so that your server’s IP address resolves backwards to your primary domain name. Setting PTR records prevents external receiving mail servers from rejecting your messages as unverified spam. Open a support ticket with their 24/7 support team to inquire about configuring PTR records for your server.
4. Reaching Support When Problems Persist
If you determine a connectivity failure is related to underlying hypervisor hardware, physical switch routing, or upstream packet filtering, contact AlexHost technical support:
- 24/7 Ticketing System: Open a ticket directly inside the client portal under the Technical Support queue.
- Telegram Live Chat / Channel: Connect via the official AlexHost Telegram channels listed on their website for rapid status updates.
- Email & Phone: Reach their administration team at info@alexhost.com or by telephone at +373 79 600002.
Official website · Latest pricing & offers
FAQ
How long does it take for an AlexHost VPS to activate after payment?
Standard Linux and Windows KVM VPS instances on AlexHost are provisioned automatically. Deployment typically completes within a few minutes after payment confirmation from one of their 20+ supported payment gateways. Once complete, server credentials are delivered via email and posted directly in your client dashboard.
What virtualization technology does AlexHost use for its virtual servers?
AlexHost uses KVM (Kernel-based Virtual Machine) virtualization infrastructure across its virtual private server lines. KVM guarantees dedicated RAM allocations, independent kernel control, fully isolated virtual storage devices, and comprehensive operating system customization.
Can I run Windows on an AlexHost VPS?
Yes. AlexHost supports multiple Windows editions, including Windows Server 2012, Windows Server 2016, and Windows Server 2019, as well as desktop editions like Windows 10 and Windows 11. These instances come with Remote Desktop Protocol (RDP) enabled for administrative access.
Where are AlexHost’s VPS data centers physically located?
AlexHost offers deployment across multiple locations: its primary owned bunker data center in Chișinău (Moldova), as well as server nodes in the Netherlands, Sweden, Bulgaria, Switzerland, France, England, Romania, and the United States (Las Vegas).
Does AlexHost provide DDoS protection on its VPS plans?
Yes. AlexHost includes upstream DDoS protection across its network infrastructure, utilizing multi-10 Gbit/s upstreams and Tier-1 carriers like Cogent and RETN to filter volumetric layer 3 and layer 4 network attacks before they reach your virtual server interface.
What should I do if I lock myself out of my VPS via the firewall?
If a firewall rule or SSH configuration error disconnects your remote session, open a support ticket with AlexHost’s 24/7 technical support team through your client dashboard to request assistance restoring network access.
Is an AlexHost VPS managed or unmanaged by default?
By default, standard AlexHost VPS plans are unmanaged, meaning you receive full root or administrator privileges and are responsible for software configuration and security updates. However, AlexHost also offers a 24/7 Managed VPS option for customers who require hands-on support from their technical administration staff.
Related Reading
- AlexHost VPS Review: Plans, Locations and Who It Suits
- AlexHost Dedicated Server Guide: Plans, Specs, and Support Scope
- AlexHost Pricing Explained: What Each Plan Costs (2026 Guide)
- AlexHost Shared Hosting Guide for New Websites (2026 Review)

