• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue MySQL Issues after Plesk Obsidian Upgrade

hostking

Regular Pleskian
Seems after plesk Obsidian Upgrade it gives problems with mysql passwords.

I get this error running plesk repair all -y

Password validation failed. The password does
not meet Windows policy requirements because it is not complex
enough.

Seems to happen with mssql aswell I think:

- mssqlmng failed: Password validation failed. The password does
not meet Windows policy requirements because it is not complex
enough.

Will disable password complexity via Local security policy and see if that helps but strange this is an issue due to upgrade of Plesk.
 
The user meetingr_edmund on the subscription meetingr.ghvgh is
absent from the database server ................................... [ERROR]
Recreating the user meetingr_edmund on the subscription
meetingr.ghvgh ............................................... [FAILED]
- mssqlmng failed: Password validation failed. The password does
not meet Windows policy requirements because it is not complex
enough.
at (VADOConnection::execute line 78)
at execute console command --add-login(vconsoleapp::start
line 93)
at execute "C:\Program Files (x86)\Plesk\admin\bin\mssqlmng"
--add-login "--server=sqlservername"
"--login=plesksql" "--password=*"
"--new-user-login=meetingr_edmund" --new-user-password
"--database=rgeshake_meetingr_shakeIt"(vconsoleapp::run line
110)
(Error code 1)
 
Back
Top