VPS Tutorials
Choose a VPS Linux distribution: Ubuntu, Debian, Rocky or AlmaLinux
Choose a supported VPS image by application requirements, architecture and maintenance coverage. Compare Ubuntu, Debian and RHEL-family systems, then plan a verified CentOS migration.

Choose a VPS operating system by the software you need to run, the provider's image quality and the support you can maintain. Ubuntu, Debian, Rocky Linux and AlmaLinux can all host useful workloads; a familiar, supported image is usually more valuable than a distribution ranking.
This guide reviews the original September 2026 advice against official information available in November 2026. It covers release support, package tools, security controls, network configuration and migration from CentOS Linux. An old image in a provider's menu is a reason to investigate that image, not proof that every image the provider offers is neglected.
| Need | Starting point |
|---|---|
| Follow a current Ubuntu tutorial | Ubuntu 26.04 LTS if every dependency supports it |
| Match existing infrastructure or mature third-party packages | Ubuntu 24.04 LTS |
| Minimal installation or a 512-MB–1-GB VPS | A supported minimal Debian 13 image, after budgeting the workload |
| cPanel, Plesk or another commercial panel | The exact OS/release/architecture supported by that panel version |
| RHEL-compatible enterprise tooling | Supported Rocky Linux or AlmaLinux, subject to application certification |
| Existing CentOS Linux 7/8 | Plan a supported migration; do not build a new service on the old image |
Panel support is not interchangeable. Plesk's matrix includes Ubuntu and Debian as well as other systems; it is not RHEL-only. The verified cPanel AlmaLinux requirements list AlmaLinux 10 with cPanel 132 or later. Check the cPanel requirements and Plesk matrix before ordering.
| Release family | Relevant lifecycle |
|---|---|
| Ubuntu 26.04 LTS, Resolute Raccoon | Released April 2026; standard maintenance through May 2031 |
| Ubuntu 24.04 LTS, Noble Numbat | Released April 2024; standard maintenance through May 2029 |
| Debian 13, Trixie | Released August 2025; regular support to August 2028, LTS to June 2030 |
| Debian 12, Bookworm | Released June 2023; in the LTS phase, scheduled through June 2028 |
| Rocky Linux 10 | Use the maintained point release and the project's published lifecycle |
| AlmaLinux 10 | Active support through May 31, 2030; security support through May 31, 2035; keep point releases current |
| CentOS Stream 10 | Tracks upcoming RHEL changes; use its own lifecycle and application support |
| CentOS Linux 7 / 8 | Upstream EOL June 30, 2024 / December 31, 2021 |
| Debian 11, Bullseye | Community LTS ended August 31, 2026; plan migration unless separately covered |
The verified Debian page lists 13.7, released September 12, 2026. Always check the current point release instead of freezing an image-menu example. Debian's dates extending to June 2035 for 13 are third-party paid ELTS, with its own package/architecture coverage, not community LTS through 2035. Ubuntu Pro and other extended services likewise have separate coverage and terms. See Ubuntu's lifecycle and Debian releases.
- Bullseye's community LTS deadline has passed; a running service is not evidence that it still receives covered updates.
- AlmaLinux's release notes explain that an older minor release reaches EOL when its replacement is released. The major-version deadline does not justify freezing an obsolete minor release.
- Ubuntu interim releases normally receive nine months of support. Ubuntu 25.10 reached EOL in July 2026. Repository changes can break
apt update, but a successful package refresh also does not prove ongoing security coverage.
Both use apt, and much administration is similar. Compare the actual cloud images and repository support.
| Consideration | Ubuntu LTS | Debian stable |
|---|---|---|
| Minimal image size | Depends on provider and installed services | Often a small starting installation |
| Kernel and package versions | Depend on LTS, HWE and repository selection | Depend on the current stable release and backports |
| Third-party repositories | Frequently supported, but verify the release | Support varies by vendor |
| Guides and tooling | Many Ubuntu-specific instructions | Extensive Debian documentation |
| sudo and default accounts | Provider-dependent | Provider-dependent, especially minimal images |
The original 50–150-MB idle-memory difference is an estimate for particular images, not a distribution guarantee. Measure identical installed services, especially on 512 MB or 1 GB. The application's resource needs are much larger than many idle-system differences.
Ubuntu 26.04 uses the codename resolute. Verify that database, monitoring and panel repositories publish packages for it before adding them. If apt update reports unsupported suites or missing metadata, do not substitute another release's repository blindly. Ubuntu 24.04 remains a valid choice when it matches your dependencies and maintenance plan.
Rocky Linux was initiated by Gregory Kurtzer and its community; AlmaLinux began with CloudLinux support and is governed by its foundation. Select according to application support, project policies and any commercial support contract, rather than assuming only one can receive paid assistance.
AlmaLinux changed its objective in 2023 to RHEL ABI compatibility; describing both projects simply as identical 1:1 rebuilds is misleading. Consult the AlmaLinux FAQ. Compatibility also does not automatically provide Red Hat certification or a vendor's application support.
RHEL-family systems make sense when:
- Your organization's operations or certification requirements specify them.
- An application supports a particular RPM-based release.
- A chosen panel explicitly lists that release.
Ordinary websites, Docker projects and personal services do not inherently require a RHEL-family OS. CentOS Stream sits upstream of RHEL's minor releases; it is not the discontinued CentOS Linux rebuild. Its release model requires compatibility and update planning, but a blanket claim that it can never serve production is inaccurate.
Ubuntu 24.04 x64
Debian 12 minimal
AlmaLinux 9 + cPanel
CentOS 7 x64 (Legacy)
Custom ISO
- Distribution and release identify package and support expectations; prefer a maintained release compatible with your software.
x64/amd64commonly mean 64-bit Intel/AMD;arm64/aarch64indicate ARM. Match both hardware and application images. Some newer releases also require particular CPU instruction levels.minimalandnetinstallindicate different installation/minimal-image offerings; check what the provider means. Tools such assudoandcurlmay be absent.+ cPanelor+ Pleskmeans a preinstalled panel. Select it only when you want its supported stack and license.Legacy/EOLwarn about old support status; do not assume an archived image is suitable for a new public service.Custom ISOrequires a compatible uploaded ISO and console access. See reinstallation choices.
Menu position is not a reliable freshness indicator. Check release, image build date, update repositories, architecture and provider documentation.
# 发行版和版本号
cat /etc/os-release
# 内核版本
uname -r
# 架构(x86_64 还是 aarch64)
uname -m
Read /etc/os-release: PRETTY_NAME is a display name and VERSION_CODENAME identifies a codename such as noble or trixie. Kernel version and architecture answer different questions from distribution support.
Compare the installed release with its lifecycle and any active extended-support entitlement. Upstream EOL ends normal coverage; third-party paid support, when present, has specific scope and is not a reason to assume every package is covered.
| Operation | Debian / Ubuntu | RHEL / Rocky / AlmaLinux |
|---|---|---|
| Refresh/check available updates | apt update | dnf check-update |
| Upgrade installed packages | apt upgrade | dnf upgrade |
| Install | apt install nginx | dnf install nginx |
| Remove | apt remove nginx | dnf remove nginx |
| Search | apt search nginx | dnf search nginx |
| List installed packages | dpkg -l | rpm -qa |
Run privileged package changes with the appropriate administrative identity. dnf check-update can return 100 when updates are available; automation must not mistake that for a broken repository. Removing a package may leave configuration or application data: inspect before deleting.
File permissions are only one access-control layer. RHEL-family images commonly enable SELinux enforcing; Ubuntu commonly uses AppArmor. Modern Debian installations can also enable AppArmor, so the original claim that Debian has neither enabled by default is unreliable for a cloud image.
- SELinux labels and policy can affect web content under
/home, outbound connections and nonstandard ports. - AppArmor confinement depends on loaded profiles; it is not inherently a promise of weaker or stronger protection for every service.
- Provider images and commercial applications can change defaults. Inspect the actual installation.
# RHEL 系
getenforce
sudo ausearch -m avc -ts recent
# Ubuntu
sudo aa-status
These are alternative diagnostics for the relevant system; install required tools if missing. Investigate denials and correct labels/profiles or approved policy. Do not disable the entire security layer just to make a website load. See 403 and SELinux troubleshooting.
Ubuntu often offers ufw, and RHEL-family images often use firewalld. Neither its presence nor its default state is guaranteed by the distribution name. Debian can have nftables or provider-managed filtering even without a convenience frontend. Check guest rules, cloud firewalls and listening addresses when a service is unreachable.
| System | Common network management |
|---|---|
| Ubuntu | Netplan, often /etc/netplan/*.yaml |
| Debian | /etc/network/interfaces, systemd-networkd or NetworkManager, depending on the image |
| RHEL family | NetworkManager using nmcli; /etc/sysconfig/network-scripts/ is a legacy path, not a reliable modern configuration location |
Confirm interface names, DHCP/static addressing, gateways and cloud-init before editing. netplan try offers rollback behavior compared with netplan apply, but still keep console access and understand the actual network renderer. Common mainstream server images use systemd and systemctl; specialized containers may not.
- Archived images: CentOS 7, Debian 9 or an old Ubuntu image require a support review. Ubuntu 18.04 may have separate extended coverage, but is a poor default for a new service without a specific plan. Check the image itself; use reinstallation if appropriate.
- Architecture: an x86 image will not simply boot as native ARM. Verify the provider's CPU and ARM application compatibility.
- Repositories after migration: use the release's official repositories. Check
/etc/apt/sources.listand sources.list.d, including modern deb822 .sources files. Do not repairapt updateby mixing distribution suites. - cloud-init: it can manage network, hostname and SSH keys. Identify which configuration is generated before editing or disabling anything; its behavior varies by image.
- Missing sudo: log in through an authorized root/console path and install it if required:
apt update && apt install -y sudo
Then add the intended account with usermod -aG sudo youruser, start a fresh login and verify administrative access. Do not remove working access until the new account succeeds.
Its upstream support ended June 30, 2024. yum update may fail as repositories move to archives, but switching to an archive restores old packages rather than security maintenance.
| Route | What to plan | Trade-off |
|---|---|---|
| Reinstall after verified backups | Rebuild packages, configuration and data | Straightforward for a simple environment; disk contents can be destroyed |
| Supported in-place conversion/upgrade path | Exact source/target versions, prerequisites and staged testing | Can preserve configuration but carries package and rollback complexity |
| Migrate to a new supported VPS | Parallel deployment, data synchronization and cutover | Easier rollback; needs extra capacity and a controlled write window |
The original half-hour-to-several-hours reinstall and 1–2-hour conversion figures are estimates, not outage commitments. A parallel migration can reduce downtime, but does not guarantee zero downtime. Tools such as ELevate support defined transitions; do not assume they jump directly from CentOS 7 to the newest major release.
Before any change, collect data and configuration:
# 网站和配置
tar czf /tmp/backup-$(date +%F).tar.gz \
/etc/nginx /etc/httpd /etc/letsencrypt /var/www /home /root/.ssh
# 数据库
mysqldump --all-databases --single-transaction > /tmp/all-db.sql
# 或
sudo -u postgres pg_dumpall > /tmp/all-db.sql
# 装了哪些包(重建环境时用得上)
rpm -qa > /tmp/packages.txt
Adapt the sketch to existing paths. Missing tar inputs can fail the archive; do not accept a partial copy. Use unique protected filenames and the dump tool for your actual database, not both commands writing the same file. InnoDB transactional dumps do not freeze website files, non-transactional tables or concurrent DDL. Include required secrets, service units, certificates, scheduled jobs and dependency versions, then transfer encrypted copies off the system disk. Verify extraction and an isolated database restore.
Choose reinstallation for a rebuild, or controlled business migration for staged cutover. A clean target is often simpler to reason about, but evaluate the documented conversion path rather than assuming all conversion tools leave unusable systems.
| Workload | Useful selection rule |
|---|---|
| BT/aaPanel, 1Panel or another panel | Follow its current OS and architecture matrix |
| Mostly Docker | Debian 13 or a supported Ubuntu LTS; verify engine and application image support |
| 512 MB–1 GB | Minimal supported image plus a measured workload budget |
| cPanel / Plesk | Check panel version, OS, CPU architecture and license requirements separately |
| Enterprise applications | Follow certification and support contracts |
| SteamCMD/game servers | Verify game binaries, libraries and supported architecture; Ubuntu guides may help |
| RPM-only applications | Use the explicitly supported RPM distribution/release |
There is no guarantee of identical throughput across distributions: kernels, libraries, defaults and packaging differ. In many small sites, application configuration, caching, resources and connectivity dominate. See hardware sizing and low-memory tuning.
Can I change the system later? Usually by reinstalling or migrating. The system disk may be erased; provider timing and treatment of extra disks vary. Verify offsite backups first.
Will the distribution change website speed? It can change runtime and defaults, but do not expect a universal ranking. Compare the actual stack under representative load.
32-bit or 64-bit? Choose a supported 64-bit image matching the hardware: x86_64/amd64 for Intel/AMD or arm64/aarch64 for ARM. Do not treat 64-bit as synonymous with x86.
Can a VPS run Windows? Only with compatible virtualization, provider terms, licensing and an appropriate image. The original 1/2/4-GB examples are rough usability estimates, not current Windows minimum requirements. Verify the selected version, storage and workload; a GUI and updates require substantial headroom.
Ubuntu 26.04 or 24.04? Use 26.04 when all dependencies support it and its lifecycle fits. Use 24.04 when you need a supported repository or consistency with existing hosts; keep it patched.
Is the provider image the same as an ISO installation? Usually it is a prepared cloud image with cloud-init and selected packages. Check accounts, keys, network configuration and security updates instead of assuming identical defaults.
- Reinstall a VPS when its image is unsuitable.
- Size the workload alongside the OS.
- Check panel requirements.
- Install and operate Docker using distribution-specific instructions.
- Harden the new server before exposing applications.