• 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.

Resolved Plesk panel update fails with "certificate has expired"

kassi

Basic Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.64 #1
I'm currently still on 18.0.64 and want to update to latest 18.0.67.
When I run the installer from the Plesk Panel, it starts and quits after a while with the following message:

Code:
Installation started in background
Checking whether the package dependencies are resolved.
Installing packages

**** Product prep-install started.
Create user 'psaadm' and group 'psaadm'
Group 'psaadm' already exists
Checking for the user 'psaadm'...
User 'psaadm' already exists
Create group 'swkey-data'
Group 'swkey-data' already exists
Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there
Create group 'psaserv'
Group 'psaserv' already exists
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
Create group 'psacln'
Group 'psacln' already exists
Trying to got legacy variables... done
config updated
===> Updated /etc/psa/psa.conf
Trying to save legacy variables... done
Checking that /opt/psa/bin/chrootsh registered as login shell...

===> Performing safe prep-install database actions


===> Upgrading database

Trying to start service mariadb... active
done
Trying to establish test connection... ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
ERROR 2026 (HY000): TLS/SSL error: certificate has expired
failed

ERROR while trying to establish test connection

Check the error reason (see log file: /var/log/plesk/install/plesk_18.0.67_installation.log), fix and try again
***** problem report *****
ERROR while trying to establish test connection
Launching component and product checkers...
Downloading file report-update: 0%
Downloading file report-update: 100% was finished.
Downloading file pool/PSA_18.0.67_16409/examiners/py_launcher.sh: 0%
Downloading file pool/PSA_18.0.67_16409/examiners/py_launcher.sh: 100% was finished.
Error: An error occurred during performing of installation PREP actions (see log for details). Installation was rolled back.
Warning! Not all packages were installed.
Please check if your system services are operable.
Please resolve this issue and try to install the packages again.
Visit https://support.plesk.com/ to search for a solution.

The downloaded log contains the same error and doesn't reveal anything else.

Since I don't know which certificate is meant, I tried
`plesk bin certificate -u` for each certificate in the -admin space, but I get the same errors.
 
You can remove the line, yes. As on whether that will happen in the future, it is best for the server configuration to be further checked in order to determine what exactly caused the issue.
 
Back
Top