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

Watchdog Failed to Connect to Database

M

menthol

Guest
I have resisted posting this because the Watchdog error that I am getting is rather obvious:

db_connect: failed to connect to database: Error: Client does not support authentication protocol requested by server; consider upgrading MySQL client

With so many people having problems with 8.1 full installs or upgrades, I felt rather lucky that this is the only problem I have encountered and have left it to the updater to hopefully produce a fix.

After the last two Plesk updates this error is still being reported every night and my research has come to the conclusion that this is a password hash length problem with MySQL.

I remember having to fix my passwords manually (for other MySQL applications) when I upgraded MySQL on my own quite a few months back before Plesk supported MySQL 5 but now I do not wish to fool around with Plesk 8.1 as I fear I may create more problems.
 
Back
Top