• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved After upgrading from ubuntu 18.04 to Ubuntu 20.04 MySQL 8.0 and plesk stop working at 100%

EmilioO

Basic Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
18.0.64 #1
I used the script to upgrade ubuntu 18.04 to 20.04, upgrade fails and I have to manually recovery packages and database dumps from backup.
After many fixes I got plesk running again but certain tasks (backups, plesk repair installation) fails which the error "Plugin caching_sha2_password could not be loaded: /usr/lib/mariadb/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory"

I'm using ubuntu 20.4 and Plesk obsidian 18.0.64 Update 1

I've checked another server with Ubuntu 20.04, Plesk and MariaDB 10 and this file "/usr/lib/mariadb/plugin/caching_sha2_password.s" doesn't exists.
 
The issue is most likely caused because the 'caching_sha2_password' authentication plugin used for the 'apsc' database user. What you can do is try to configure the user to use 'mysql_native_password' authentication instead.

  1. Back up Plesk databases:
    plesk db dump > psadump.sql
  2. Log in to the 'mysql' database:
    plesk db
    ...
    mysql> use mysql;
  3. Change authentication plugin:
    mysql> ALTER USER 'apsc'@'localhost' IDENTIFIED WITH 'mysql_native_password' BY '<password>';
    Query OK, 0 rows affected (0.03 sec)

    mysql> quit
  4. Update credentials stored in the 'psa' database using 'plesk repair db' utility:
    plesk repair db
 
Back
Top