• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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