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

mysqlnd cannot connect to MySQL 4.1+ Error

C

CalebF

Guest
Hello,

Clients are receiving this error when trying to connect to their SiteBuilder after upgrading to 10.3...

[2000] mysqlnd cannot connect to MySQL 4.1+ using the old insecure authentication. Please use an administration tool to reset your password with the command SET PASSWORD = PASSWORD(‘your_existing_password’). This will store a new, and more secure, hash value in mysql.user. If this user is used in other scripts executed by PHP 5.2 or earlier you might need to remove the old-passwords flag from your my.cnf file

We've run the repair script with no luck, any ideas?
 
could you please launch:

cd %plesk_bin%
local_mysql_helper.exe --repair-sitebuilder-database-user-password

?
 
Command

Awesome,

That worked
 
Last edited by a moderator:
Same error with older Clients Databases

Hello Pavel,

i've the same Problem with older Clients Databases after upgrading to 10.3!?
What can I do?

Why happened this?

Thanx,
Stefan
 
Hello Pavel,

sorry, but this didn't work. Same error. What can I do?

-Stefan
 
Back
Top