Short answer: Plesk supports AlmaLinux 10 from Plesk Obsidian 18.0.72, and Plesk’s system requirements now list AlmaLinux 10.x as a recommended OS. It comes with limits: no Watchdog, no Plesk Premium Antivirus, no Webalizer, Mailman, Qmail or SOGo webmail, and no support for Intel Xeon V2 or older CPUs. There is no in-place upgrade from AlmaLinux 9, so the path is a new server plus Plesk Migrator.
Applies to Plesk Obsidian 18.0.72+ on AlmaLinux 10; migration from AlmaLinux 9
Facts checked against Plesk’s support article, system requirements and change log (linked below) on 6 October 2026. The CPU check command was run on our AlmaLinux 9.8 lab server; we have not installed Plesk on AlmaLinux 10 in our lab.
Table of Contents
Which Plesk version supports AlmaLinux 10
Plesk’s support article Does Plesk support AlmaLinux 10? says support starts with Plesk Obsidian 18.0.72. The current Plesk system requirements page lists the supported AlmaLinux releases as AlmaLinux 10.x (recommended), 9.x and 8.x, with a note that AlmaLinux 10 comes “with a number of limitations” that link back to the same article.
When we checked the Plesk change log on 6 October 2026 the newest release listed was Plesk Obsidian 18.0.81 (15 September 2026). Recent entries include AlmaLinux 10 fixes, for example ClamAV installation through the Email Security extension (May 2026) and SSH public key logins for subscription users when SELinux is enforcing (September 2026). If you build a new AlmaLinux 10 Plesk server today, you get a current release by default, so 18.0.72 is only a floor.
The installer is the usual one-click command from the Plesk deployment guide, run as root on a clean AlmaLinux 10 install:
sh <(curl https://autoinstall.plesk.com/one-click-installer || wget -O - https://autoinstall.plesk.com/one-click-installer)Plesk says the one-click install takes around 15 minutes and installs the latest stable release with the default component set.
What is missing on AlmaLinux 10
The Plesk article lists these components as unavailable or unsupported on AlmaLinux 10, with the reason Plesk gives:
| Component | Status on AlmaLinux 10 | Reason given by Plesk |
|---|---|---|
| Watchdog extension | Not available | monit dependency missing from EPEL |
| Plesk Premium Antivirus | Not supported | 32-bit glibc not available |
| Webalizer | Not available | – |
| Mailman | Not supported | – |
| Qmail | Not supported | xinetd dependency problems |
| SOGo Webmail extension | Not compatible | Waiting on vendor support |
| Intel Xeon V2 and older CPUs | Not supported | OS baseline |
The Watchdog reason is Plesk’s wording. When we checked EPEL 10 metadata on 6 October 2026 it did contain a monit 6.0.0 package, and the Plesk change log mentions a Watchdog fix for Monit 6.x on AlmaLinux 9. Do not assume Watchdog works on AlmaLinux 10 until the Plesk article says so; plan external monitoring instead.
If you rely on any item in that table, stay on AlmaLinux 9 for now. AlmaLinux 9 is still supported by Plesk and has a long support window left.
The CPU limit: x86-64-v3
AlmaLinux 10 follows Red Hat in building its default x86_64 packages for the x86-64-v3 microarchitecture level, which older CPUs lack. AlmaLinux also ships a separate x86-64-v2 variant for older hardware, but its release notes say that variant only suits workloads that need nothing beyond the default OS packages. Plesk’s article simply says Intel Xeon V2 and older CPUs are unsupported on this OS.
Check a server (or a VPS plan) before you order or reinstall. On any EL9 system, the dynamic loader tells you which levels the CPU supports. This is the output from our AlmaLinux 9.8 lab VM:
/lib64/ld-linux-x86-64.so.2 --help | grep x86-64-v
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)If x86-64-v3 is not marked supported, do not put Plesk on AlmaLinux 10 on that machine. On a VPS, the hypervisor’s CPU model setting matters as much as the physical CPU: a generic “kvm64” model can hide v3 features even on new hardware.
What behaves differently from AlmaLinux 9
Plesk lists several technical changes that matter if you have scripts or habits from AlmaLinux 9 servers:
- AWStats now comes from Plesk’s own package.
- Postfix lookup tables use the
lmdbformat instead ofhash. Custom scripts that runpostmap hash:...need updating. - IP addresses are managed through NetworkManager with nmstate rather than the old network scripts.
- Fail2Ban uses nftables.
- Firewall extension depends on the
iptables-nftpackage.
If you manage firewall rules by hand, check them with nft list ruleset rather than assuming the iptables view tells the whole story.
Moving a Plesk server from AlmaLinux 9 to 10
Plesk’s article says there is no in-place upgrade tool from AlmaLinux 9 to 10 and no ETA for one; the team’s focus is the AlmaLinux 8 to 9 upgrade. The supported route is a side-by-side move:
- Build a new AlmaLinux 10 server on a CPU that supports x86-64-v3, and install Plesk with the one-click installer.
- Check the missing-components table against what you use (Watchdog, SOGo, Premium Antivirus, Mailman).
- On the new server, open Extensions > Plesk Migrator > Start a New Migration and choose Plesk as the source. Plesk Migrator supports Plesk 8.6 and later as a source.
- Migrate one test subscription, check it through a hosts-file entry, then migrate the rest.
- Switch DNS, then run Plesk Migrator’s re-sync for content and a mail-only sync for mail that arrived after the switch.
- Keep the AlmaLinux 9 server running for a week before you cancel it.
The same Plesk Migrator workflow is covered for cross-panel moves in our Plesk to cPanel migration guide.
Should you choose AlmaLinux 10 for a new Plesk server?
| Choose AlmaLinux 10 if | Stay on AlmaLinux 9 if |
|---|---|
| The CPU supports x86-64-v3 | The host only offers older Xeon (V2 or earlier) or a CPU model without v3 |
| You use Postfix, AWStats and Roundcube | You need SOGo, Mailman, Qmail or Webalizer |
| You monitor services externally | You rely on the Watchdog extension |
| You want the longest OS support window | You want the most-tested combination today |
Whichever you pick, test the extensions you depend on (Imunify, backup extensions, WP Toolkit) on a trial server first; third-party extensions follow their own OS support schedules.
Check that it worked
- Run
plesk versionand confirm the release is 18.0.72 or later. - Open Tools & Settings > Updates and check that no component you need shows as unavailable.
- Send a test mail through Postfix and confirm any custom transport maps were rebuilt in lmdb format.
- Check Fail2Ban jails with
fail2ban-client statusand the nftables rules withnft list ruleset.
Official documentation: Plesk: Does Plesk support AlmaLinux 10? · Plesk Obsidian system requirements · Plesk Obsidian change log · AlmaLinux 10.0 release notes
Related: Install cPanel AlmaLinux 10: 2026 Checklist · Install DirectAdmin on AlmaLinux 9/10 and Debian 13: 2026 Guide · CSF AlmaLinux 10: nftables and ipset Problems Fixed · Best VPS for cPanel and DirectAdmin in 2026: What to Check · MailBaby Plesk Webuzo Relay: Outbound Setup
See also: Migrate DirectAdmin to DirectAdmin: Move All Users to a New Server · Migrate Plesk to cPanel (and cPanel to Plesk): Tools and Limits
See also: Plesk “Unable to connect to database”: PleskDBException Fix · cPanel vs Plesk (2026): Which Control Panel for Hosting? · DirectAdmin vs Plesk (2026): Cost, Features, Migration
Frequently asked questions
Does Plesk support AlmaLinux 10?
Yes, from Plesk Obsidian 18.0.72, with limitations: no Watchdog, Premium Antivirus, Webalizer, Mailman, Qmail or SOGo, and no Xeon V2 or older CPUs.
Can I upgrade a Plesk server from AlmaLinux 9 to 10 in place?
No. Plesk says there is no in-place upgrade tool for AlmaLinux 9 to 10. Build a new server and move subscriptions with Plesk Migrator.
Why does AlmaLinux 10 not run on my old Xeon?
AlmaLinux 10 builds its default packages for x86-64-v3, which older CPUs lack. AlmaLinux offers a v2 variant, but Plesk lists Xeon V2 and older as unsupported.
Is AlmaLinux 9 still a good choice for Plesk?
Yes. It is fully supported and has none of the AlmaLinux 10 component gaps, which makes it the safer pick if you need SOGo, Watchdog or Premium Antivirus.
Which webmail works on Plesk with AlmaLinux 10?
Roundcube is the usual choice. The SOGo extension is listed as incompatible until the vendor adds support.
Maintenance record
This guide changes servers, data or security settings, so we re-check it against current versions on a fixed schedule. Take a backup or snapshot before you start.
- Maintained by
- srvScripts editorial team
- Supported versions
- Plesk Obsidian 18.0.72+ on AlmaLinux 10; migration from AlmaLinux 9
- Last full review
- Next review