• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Cannot update from Plesk Obsidian 18.0.69

Aspire

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian 18.0.69 #4
We installed a Plesk system from AWS marketplace about a year ago, but cannot update it.
The EMI was: Plesk Obsidian 'Bring Your Own License' (Ubuntu 22.04 aarch64) 20250430.0715-7917ca0b-ac94-416a-9357-1d45f6bf9b65

Update attempt returns:
There are no products for your operating system
( 'Ubuntu' 'Linux' '24.04' 'aarch64' ) available
from the selected source.

Because the reason for the update was to patch PHP 8.3.26 , I installed PHP 8.3.36 and switched Plesk over to it,

We have around 20 sites on that EC2 and all are running again, but it's a wee bit unstable. With the occassional MariaDB lockup and probably related timeouts.

It was rock-solid before, but before I go retuning it, I'd like to get Plesk updated.

What can I do form here?
 
Hi,

Look at the error again: it says ‘Ubuntu’ ‘Linux’ ‘24.04’ ‘aarch64’, not 22.04. Plesk doesn’t have packages for that combo. Ubuntu 24.04 is only supported on x86-64, and Plesk has said in the forum that there are no plans for 24.04/26 on ARM. ARM support is supposed to end together with Ubuntu 22.04 in April 2027.

So first, check what your server really is:
Code:
cat /etc/os-release
uname -m
plesk version
grep -rhE “^(deb |URIs:|Suites:)” /etc/apt/sources.list /etc/apt/sources.list.d/

If it says 24.04: at some point the OS got upgraded (do-release-upgrade or apt), and Plesk is now on an unsupported platform. That could also explain the flakiness, since you’d have a mix of packages from both releases. Your options:
  1. Roll back to an EBS snapshot/AMI from before the OS upgrade, if you have one. Downgrading Ubuntu isn’t really a thing.
  2. Spin up a fresh Ubuntu 22.04 aarch64 instance and move everything over with the Plesk Migrator. That works, but only until April 2027.
  3. Spin up an x86-64 instance with Ubuntu 24.04 and migrate with the Plesk Migrator. That’s the only long-term supported route.
If it says 22.04: then the installer is picking up 24.04 from somewhere else (leftover repo config maybe). Post the output of the commands above and we can dig further.

About the MariaDB lockups: I wouldn’t tune anything yet. Check the logs first:
Code:
journalctl -u mariadb --since “7 days ago” | tail -n 100
dmesg -T | grep -i -E “out of memory|oom”
free -h

If the OOM killer shows up there, that’s a good lead. It’s just a guess though, so look at the logs before changing anything.

One more question: where did you get PHP 8.3.36 from? Plesk’s own packages or a third-party repo? If it’s a third-party repo, it might be part of the problem.

Sources:
Regards
Tessa
 
Back
Top